[Bug 1961010] Re: firefox doesn't let its user control how or when it upgrades
Thank you. Yes, about:buildconfig shows the --disable-updater flag. And software-properties-gtk --open-tab=2 showed that the setting for security updates was to download and install them immediately. I have changed that setting to only download security updates rather than to install them immediately. This should allow me to schedule updates to Firefox when its ongoing continuity is not critical. (Somehow when I run update-manager, it regularly finds "Security updates" that have not been immediately applied, even though the setting was formerly "Download and install immediately". Are "Security updates" in update-manager different from the "security pocket" that Firefox updates occur in? Thank you for the diagnosis. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961010 Title: firefox doesn't let its user control how or when it upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1961010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961010] Re: firefox doesn't let its user control how or when it upgrades
Added screenshot that happens when this bug is triggered. Firefox refuses to operate normally after this point, just displaying "Sorry. We just need to do one small thing to keep going. Firefox has just been updated in the background. Click Restart Firefox to complete the update. We will restore all your pages, windows and tabs afterwards, so you can be on your way quickly." over and over. ** Attachment added: "Screenshot from 2022-02-15 20-06-57.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1961010/+attachment/5561208/+files/Screenshot%20from%202022-02-15%2020-06-57.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961010 Title: firefox doesn't let its user control how or when it upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1961010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961010] [NEW] firefox doesn't let its user control how or when it upgrades
Public bug reported:
The Firefox package does not act like ordinary packages. When it is
running, it forcibly downloads upgraded binary versions of itself and
then forces the user to restart Firefox and run the new version. There
used to be a Firefox setting by which the user could control this, but
it has been deliberately removed.
This is problematic in many ways. The first way is that it undermines
the user's control over their own environment. The essential element of
free software is that users control it, it does not control them. If
there is behavior that is undesirable, they can fix it, not just be
subjected to the arbitrary decisions of a distant corporation. For
example, some users require that they have a copy of the source code
that matches each binary package they are running. Firefox's covert
upgrades undermine this local user policy, installing binaries that have
no local matching source code. Other users may be using plugins or
other applications that do not work with later versions of Firefox. It
is not Firefox's decision when to upgrade -- it is the user's or system
operator's.
The second problem is that restarting one's browser has many side effects. For
example, if one window or tab is in a video conference, forcing a restart of
Firefox ejects the user from their video conference. If a video or audio file
is merely playing in another window or tab, it is
interrupted and not necessarily resumed after restart in the right place.
Cookies and permissions (e.g. for NoScript) are not carried forward after a
restart, when they are set to persist only for one session.
If the Mozilla Corporation has firmly and permanently decided that it
doesn't believe in the freedom of the end-users of its software, then
Ubuntu should ship a patched version that DOES give its end-users
freedom, by restoring the setting to disable automated updates. Firefox
would continue to be able to be updated by the usual update-manager GUI
(which IS under the control of the user), apt-get, or by the user
explicitly installing new versions via dpkg or by building from source
code.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 97.0+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: gnu2520 F pulseaudio
/dev/snd/controlC1: gnu2520 F pulseaudio
/dev/snd/controlC0: gnu2520 F pulseaudio
BuildID: 20220202182137
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 15 22:55:07 2022
ForcedLayersAccel: False
IncompatibleExtensions:
Global Menu Bar integration - globalm...@ubuntu.com
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-05-04 (652 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 209.16.159.254 dev enp6s0 proto static metric 100
75.101.100.0/24 dev enp6s0 proto kernel scope link src 75.101.100.46 metric
100
169.254.0.0/16 dev enp6s0 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
209.16.159.0/24 dev enp6s0 proto kernel scope link src 209.16.159.252 metric
100
MostRecentCrashID: bp-f3d4806a-b277-49a1-b452-902072161127
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:365
PrefSources: prefs.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=97.0/20220202182137 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs:
bp-f3d4806a-b277-49a1-b452-902072161127
bp-4da20c64-dde1-4304-9118-238562160914
bp-16b8bc44-ebd0-46e0-a272-95feb2160908
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F25
dmi.board.asset.tag: Default string
dmi.board.name: AX370-Gaming 5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: AX370-Gaming 5
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co.,
[Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
I am running a laptop with an internal nvme that is partitioned to contain an encrypted LUKS partition that contains an LVM2 PV. That PV contains part of an LV (lvubuntu) which also includes a partition residing on an external USB drive. The theory is that I'll make part of the external PV into a RAID-1 image of the internal partition, which will automatically back up the internal nvme whenever I plug in that drive, making it a USB-bootable bit-for-bit copy. (That part doesn't work yet because of a blocksize mismatch between the 4k hard drive and the 512b nvme partition; I'll need to dump, reformat, and restore the nvme LV into 4k blocks before LVM will succeed in making it part of a RAID set.) I have been able to boot this laptop (without the external drive attached) even prior to this bug fix. I can't tell you exactly how it worked, but it worked, possibly because the RAID1 isn't set up yet; instead the LV just includes both PV's. I upgraded to the released fix for this bug in 20.04, as part of installing all current security patches. Now when I boot the system, it detects the encrypted partition, asks for the password, gets it, and succeeds in fsck-ing the root partition. But then it loops and fsck's it again. And again. And again. (I noticed this by the long delay with the circling icon on the splash screen. I switched to ctrl-alt-F1 to see console messages and there I see it doing the fsck over and over.) Eventually THIS behavior times out too, and the system does boot. But I suspect that this is not exactly what you wanted this patch to do. It used to boot very quickly, now after the patch for this bugfix, it doesn't. I'm running 20.04.1 on an amd64 (Lenovo Ideapad Flex 5 14", AMD Ryzen 5 4500U) laptop. # pvdisplay WARNING: Couldn't find device with uuid u2T6W5-rI3L-40C8-rZc3-uS6H-rMsV-U58ic5. WARNING: VG vgubuntu is missing PV u2T6W5-rI3L-40C8-rZc3-uS6H-rMsV-U58ic5 (last written to /dev/mapper/luks-d43f3ec2-2633-46d0-bd1b-1c9f46e13c4d). --- Physical volume --- PV Name /dev/mapper/nvme0n1p3_crypt VG Name vgubuntu PV Size 237.24 GiB / not usable 0 Allocatable yes PE Size 4.00 MiB Total PE 60734 Free PE 253 Allocated PE 60481 PV UUID SQ4XNm-dKJQ-ild3-dx2k-lrGL-fqay-5rY8nY --- Physical volume --- PV Name [unknown] VG Name vgubuntu PV Size <3.64 TiB / not usable 4.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 953610 Free PE 817930 Allocated PE 135680 PV UUID u2T6W5-rI3L-40C8-rZc3-uS6H-rMsV-U58ic5 # lvdisplay WARNING: Couldn't find device with uuid u2T6W5-rI3L-40C8-rZc3-uS6H-rMsV-U58ic5. WARNING: VG vgubuntu is missing PV u2T6W5-rI3L-40C8-rZc3-uS6H-rMsV-U58ic5 (last written to /dev/mapper/luks-d43f3ec2-2633-46d0-bd1b-1c9f46e13c4d). --- Logical volume --- LV Path/dev/vgubuntu/root LV Nameroot VG Namevgubuntu LV UUIDDy2wIe-nhEd-BZN5-i3bg-AU3P-uenQ-fuPkSR LV Write Accessread/write LV Creation host, time ubuntu, 2020-07-16 16:55:07 -0700 LV Status available # open 1 LV Size236.25 GiB Current LE 60481 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 --- Logical volume --- LV Path/dev/vgubuntu/root4tb LV Nameroot4tb VG Namevgubuntu LV UUIDKFe7kE-bPOs-md1j-iVqT-kBQy-mj1U-XTpfM9 LV Write Accessread/write LV Creation host, time pad.toad.com, 2020-09-03 01:11:24 -0700 LV Status NOT available LV Size230.00 GiB Current LE 58880 Segments 1 Allocation inherit Read ahead sectors auto --- Logical volume --- LV Path/dev/vgubuntu/misc LV Namemisc VG Namevgubuntu LV UUIDQKd7pK-CfdG-VxFb-VThb-QzWy-oKVO-NQdchx LV Write Accessread/write LV Creation host, time pad.toad.com, 2020-09-03 01:40:22 -0700 LV Status NOT available LV Size300.00 GiB Current LE 76800 Segments 1 Allocation inherit Read ahead sectors auto # -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879980 Title: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1888088] Re: [amdgpu] [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling
I found a way to enable the amdgpu support for this hardware in the standard LTS kernel! Based on this comment on a YouTube video reviewing this laptop: https://www.youtube.com/watch?v=FjegdWtHuOE=UgzbtkQw4vuk6ls- 6vF4AaABAg Add "amdgpu.exp_hw_support=1" to the kernel command line in /etc/default/grub, run update-grub, and reboot. This FIXES ALL THE ISSUES that I encountered in this bug. I am running linux-image-5.4.0-42-generic:amd64 (5.4.0-42.46) which is the current LTS kernel. The same poster also recommended turning on this Firefox about:config setting, to avoid screen tearing while playing YouTube videos: layers.acceleration.force-enabled. I have seen reports (comments below that same YouTube video, and elsewhere) that there are small kernel patches in the 5.7 kernels that also fix the screen brightness settings on this hardware. Perhaps a future Ubuntu kernel update can cherry-pick those fixes, and automatically enable the experimental hardware support for this integrated AMD Ryzen 5 4500U CPU/GPU? Would be good for these fixes to get into the Ubuntu 20.04.1 point release, too; these laptops are very fast and cost $600 so they are selling very well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888088 Title: [amdgpu] [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1888088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling
** Description changed: Opening Settings -> Display and selecting an orientation other than Landscape doesn't work. Similarly, selecting Fractional Scaling and then picking a scale factor has no effect. This is a recently installed Ubuntu 20.04, fully updated, on a recently released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU. It is possible that the GPU is not being detected by Ubuntu and that is the root cause of the problem. I couldn't find an easy explanation online about how to tell whether a GPU was detected or is in use. I did try running "tlp-stat -g" to get graphics status, but it returns without printing anything except its version number (1.3.1). When I choose an orientation, such as Portrait Right, the setting changes and an "Apply" button appears in the top of the Settings window. When I press it, up pops up a dialog asking whether I want to "Keep these display settings?" with two options, keep or revert. The rest of the screen goes grey behind the dialog box, but I can already see that the "Orientation" setting back in the Settings->Display window has been reverted to "Landscape" without me doing anything. Whether I choose keep or revert, or merely let it time out after 20 seconds, the result remains the same -- the display stays in Landscape mode and the setting that I had made is reverted. Regarding scaling, I can set the display scale to 100% (default) or 200%, successfully. When I turn on the "Fractional Scaling" slider, the graphics around the edge of the screen increase in size (the icons in the left-hand dock, the text in the top bar), but the Scale settings do not change (they remain "100%" and "200%"). However, if I switch to a different setting (for example, "Mouse & Touchpad") and then back to "Displays", the Scale settings have changed. I have included three screenshots (original screen, Fractional Scaling on, and after switching to and from Displays. When I attempt to set a fractional scale such as 125%, the "Apply" button appears in the upper right corner. When I press that, the display does not scale, a pop-up asks if I want to keep or revert the setting, but looking back at the Displays settings, the Scale has already reverted to 100% (as above with the Orientation). - The display has been rock-solid before this, but now it started showing artifacts, such as + The display has been rock-solid before this, but now it started showing artifacts, such as previous copies of the Displays window. I've enclosed a screen shot. Merely taking a screen shot also wiped out parts of the display to white; I took another shot to show that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: - + CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jul 18 14:00:38 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Renoir [17aa:3f1a] + Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Renoir [17aa:3f1a] InstallationDate: Installed on 2020-07-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81X2 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EECN20WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05: dmi.product.family: IdeaPad Flex 5 14ARE05 dmi.product.name: 81X2 dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05 dmi.product.version: IdeaPad Flex 5 14ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling
** Attachment added: "This is my screen after I chose "125%" as a fractional scale, then pressed Apply. The pop-up has dimmed the underlying windows, but you can see that the Scale setting in the underlying Displays window has reverted to "100%", and nothing on the screen has changed its scale to 125%." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393948/+files/Screenshot%20from%202020-07-18%2014-27-40%20-%20attempted%20125%25%20with%20popup.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888088 Title: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling
** Attachment added: "This is my screen before I slide the "Fractional Scaling" slider." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393945/+files/Screenshot%20from%202020-07-18%2014-21-25%20-%20before%20fractional%20scaling.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888088 Title: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling
** Attachment added: "This is my screen just after I slide the Fractional Scaling slider. The icons in the left margin, and the text at the top of the screen, have changed size (despite me not picking any new scale) and nothing else has scaled." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393947/+files/Screenshot%20from%202020-07-18%2014-21-41%20-%20fractional%20scaling%20with%20large%20dock%20and%20top%20bar%20but%20nothing%20else%20scaled.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888088 Title: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888088] [NEW] [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling
Public bug reported: Opening Settings -> Display and selecting an orientation other than Landscape doesn't work. Similarly, selecting Fractional Scaling and then picking a scale factor has no effect. This is a recently installed Ubuntu 20.04, fully updated, on a recently released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU. It is possible that the GPU is not being detected by Ubuntu and that is the root cause of the problem. I couldn't find an easy explanation online about how to tell whether a GPU was detected or is in use. I did try running "tlp-stat -g" to get graphics status, but it returns without printing anything except its version number (1.3.1). When I choose an orientation, such as Portrait Right, the setting changes and an "Apply" button appears in the top of the Settings window. When I press it, up pops up a dialog asking whether I want to "Keep these display settings?" with two options, keep or revert. The rest of the screen goes grey behind the dialog box, but I can already see that the "Orientation" setting back in the Settings->Display window has been reverted to "Landscape" without me doing anything. Whether I choose keep or revert, or merely let it time out after 20 seconds, the result remains the same -- the display stays in Landscape mode and the setting that I had made is reverted. Regarding scaling, I can set the display scale to 100% (default) or 200%, successfully. When I turn on the "Fractional Scaling" slider, the graphics around the edge of the screen increase in size (the icons in the left-hand dock, the text in the top bar), but the Scale settings do not change (they remain "100%" and "200%"). However, if I switch to a different setting (for example, "Mouse & Touchpad") and then back to "Displays", the Scale settings have changed. I have included three screenshots (original screen, Fractional Scaling on, and after switching to and from Displays. When I attempt to set a fractional scale such as 125%, the "Apply" button appears in the upper right corner. When I press that, the display does not scale, a pop-up asks if I want to keep or revert the setting, but looking back at the Displays settings, the Scale has already reverted to 100% (as above with the Orientation). The display has been rock-solid before this, but now it started showing artifacts, such as previous copies of the Displays window. I've enclosed a screen shot. Merely taking a screen shot also wiped out parts of the display to white; I took another shot to show that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jul 18 14:00:38 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3f1a] InstallationDate: Installed on 2020-07-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81X2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EECN20WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05: dmi.product.family: IdeaPad Flex 5 14ARE05 dmi.product.name: 81X2 dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05 dmi.product.version: IdeaPad Flex 5 14ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you
[Bug 1873641] [NEW] pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Public bug reported: Apr 19 03:12:37 shh pulseaudio[2107]: ALSA woke us up to write new data to the device, but there was actually nothing to write. Apr 19 03:12:37 shh pulseaudio[2107]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. Apr 19 03:12:37 shh pulseaudio[2107]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. I'm running Ubuntu 20.04 beta, and have just gotten past several crash or abort issues in pulseaudio on this Gigabyte AX370-Gaming5 motherboard. With tonight's update to: Package: pulseaudio Architecture: amd64 Version: 1:13.99.1-1ubuntu3 and the running kernel: Linux shh.toad.com 5.4.0-24-generic #28-Ubuntu SMP Thu Apr 9 22:16:42 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I got a somg;e report like this in syslog (so far). Since the developers asked me to report it, here's the bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 03:24:07 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: enp6s0no wireless extensions. enp5s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=35b84e12-683c-43ea-9b3f-64fae90e1984 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873641 Title: pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873641] Re: pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Um, that should say I got a "single" report like this in syslog so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873641 Title: pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873630] Re: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting.
I ran the software updater and noticed that it installed a new pulseaudio: pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 After rebooting the system, I'm running this version. You will be happy to learn that pulseaudio doesn't crash with this version, and it shows sound devices in Settings -> Sound, and the speaker test actually plays (once I picked Line Out rather than the default which was Speaker -- my chassis doesn't have a speaker). I am even able to play mp3 and flac music in Totem. I think it's fixed! Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873630 Title: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa- ucm.c:2158, function device_add_hw_mute_jack(). Aborting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
I ran the software updater and noticed that it installed a new pulseaudio: pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 After rebooting the system, I'm running this version. You will be happy to learn that pulseaudio doesn't crash with this version, and it shows sound devices in Settings -> Sound, and the speaker test actually plays (once I picked Line Out rather than the default which was Speaker -- my chassis doesn't have a speaker). I am even able to play mp3 and flac music in Totem. I think it's fixed! Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
OK, that's bug #1873630. We don't actually know that this current crasher bug is correctly solved by the above patch, since pulseaudio is not yet working. Perhaps the new bug was there all along, but perhaps it was introduced by this patch being an incomplete fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873630] [NEW] [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting.
Public bug reported: I have a Gigabyte motherboard that gives pulseaudio fits in Ubuntu 20.04 beta. (It worked fine in 18.04.4 LTS.) It produced pulseaudio crashes with bug #1870833 until a proposed fix was brought in from upstream: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu2 However, that did not actually make pulseaudio work; now it throws this error and aborts: Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. It was suggested in the previous bug that I should open a new bug for this. Here you are! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 00:25:26 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873630 Title: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa- ucm.c:2158, function device_add_hw_mute_jack(). Aborting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
** Attachment added: "Here's the alsa-info output for this system, in case it helps." https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870833/+attachment/5356402/+files/alsa-info.txt.QsoAGgtfAU -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
With the -1ubuntu2 package, I no longer get a crash dump, but the audio is still not working. pulseaudio is aborting. Here is what is in syslog from bootup: Apr 18 01:13:09 shh dbus-daemon[1218]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.31' (uid=122 pid=1443 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") ... Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic1, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic2, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line2, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Headphones, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line1, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Speaker, assuming stereo duplex. Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. ... Apr 18 01:13:10 shh systemd[1432]: pulseaudio.service: Main process exited, code=dumped, status=6/ABRT Apr 18 01:13:10 shh systemd[1432]: pulseaudio.service: Failed with result 'core-dump'. Apr 18 01:13:10 shh systemd[1432]: Failed to start Sound Service. Apr 18 01:13:10 shh systemd[1432]: Dependency failed for GNOME Sound sample caching handling. Apr 18 01:13:10 shh systemd[1432]: gsd-sound.target: Job gsd-sound.target/start failed with result 'dependency'. ... Apr 18 01:13:10 shh systemd[1432]: pulseaudio.service: Scheduled restart job, restart counter is at 1. ... Apr 18 01:13:10 shh systemd[1432]: Stopped Sound Service. Apr 18 01:13:10 shh systemd[1432]: Starting Sound Service... ... Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] pid.c: Stale PID file, overwriting. ... Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic1, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic2, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line2, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Headphones, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Line1, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Speaker, assuming stereo duplex. Apr 18 01:13:11 shh pulseaudio[1790]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. Apr 18 01:13:12 shh systemd[1432]: pulseaudio.service: Main process exited, code=dumped, status=6/ABRT Apr 18 01:13:12 shh systemd[1432]: pulseaudio.service: Failed with result 'core-dump'. Apr 18 01:13:12 shh systemd[1432]: Failed to start Sound Service. Apr 18 01:13:12 shh systemd[1432]: Startup finished in 2.727s. Apr 18 01:13:12 shh systemd[1432]: pulseaudio.service: Scheduled restart job, restart counter is at 2. Apr 18 01:13:12 shh systemd[1432]: Stopped Sound Service. Apr 18 01:13:12 shh systemd[1432]: Starting Sound Service... Apr 18 01:13:12 shh rtkit-daemon[1539]: Successfully made thread 1864 of process 1864 owned by '122' high priority at nice level -11. Apr 18 01:13:12 shh rtkit-daemon[1539]: Supervising 1 threads of 1 processes of 1 users. Apr 18 01:13:12 shh pulseaudio[1864]: W: [pulseaudio] pid.c: Stale PID file, overwriting. ... Apr 18 01:13:13 shh pulseaudio[1864]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic1, assuming stereo duplex. Apr 18 01:13:13 shh pulseaudio[1864]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or 'CaptureChannels'for device Mic2, assuming stereo duplex. Apr 18 01:13:13 shh pulseaudio[1864]: W: [pulseaudio] alsa-ucm.c: UCM file does not specify 'PlaybackChannels' or
[Bug 1873439] [NEW] Logitech BRIO webcam fails with "xhci_hcd 0000:02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13"
Public bug reported: [ 450.844431] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 450.844439] xhci_hcd :02:00.0: Looking for event-dma fd473230 trb-start fd473210 trb-end fd473210 seg-start fd473000 seg-end fd473ff0 The above occurs while trying to use Cheese to access the Logitech BRIO webcam (USB device 046d:085e). Ultimately the webcam doesn't work with Cheese. When it produces any image at all, it is full of vertical bars and is in greyscale. Meanwhile dmesg shows hundreds of the above kernel messages. After getting out of Cheese, I unplugged and replugged the webcam. This produced: Apr 17 03:58:30 shh kernel: [ 1218.202407] usb 2-8: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd Apr 17 03:58:35 shh kernel: [ 1223.341073] usb 2-8: device descriptor read/8, error -110 then a new series when plugged in: Apr 17 03:59:13 shh kernel: [ 1261.369494] usb 2-8: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd Apr 17 03:59:18 shh kernel: [ 1266.604852] usb 2-8: device descriptor read/8, error -110 which repeated a few times, interspersed with: Apr 17 03:59:34 shh kernel: [ 1282.848732] usb usb2-port8: attempt power cycle Apr 17 03:59:35 shh kernel: [ 1283.361363] usb 2-8: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd Apr 17 03:59:40 shh kernel: [ 1288.621098] usb 2-8: device descriptor read/8, error -110 Apr 17 03:59:40 shh kernel: [ 1288.728918] usb 2-8: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd Apr 17 03:59:46 shh kernel: [ 1293.996668] usb 2-8: device descriptor read/8, error -110 and ultimately: Apr 17 03:59:56 shh kernel: [ 1304.864636] usb usb2-port8: unable to enumerate USB device This dustup with the webcam also seems to screw up the USB interface to a nearby disk drive on a completely different USB port on the motherboard. The problem persists until the kernel is rebooted. Power cycling the webcam (it has no battery, so pulling the USB cord, waiting ten seconds, and replugging it suffices) does not fix the "error -110" issue, so the webcam can never be accessed again until the kernel is rebooted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 03:54:10 2020 InstallationDate: Installed on 2020-04-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: enp5s0no wireless extensions. enp6s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=35b84e12-683c-43ea-9b3f-64fae90e1984 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "dmesg output since kernel boot, plugging in webcam, failing with it, unplugging and replugging it"
[Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
** Attachment added: "syslog from Ubuntu 18.04.4 from the same system, with working sound and working pulseaudio, in case it helps." https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870833/+attachment/5355971/+files/syslog-18.04.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
I forgot to note (and the attachments don't apparently say) that I am also running this on a Gigabyte Aorus GA-AX370-Gaming 5" motherboard. I have an AMD Ryzen 7 2700 Eight-Core Processor, and 16GB of DRAM. I'll enclose dmesg output so you can see what audio chips the kernel found when booting with this 20.04 beta kernel (Linux version 5.4.0-21-generic). Also will include syslog version of dmesg output from an Ubuntu 18.04.4 boot in which the sound works fine. ** Attachment added: "dmesg output from booting this system on 20.04 beta, for audio chip and BIOS audio configuration reports" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870833/+attachment/5355970/+files/dmesg-20.04-beta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873407] [NEW] totem warns every time: "Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale)
Public bug reported: I am running Ubuntu 20.04 beta amd64 Desktop from the liveCD ISO. Whenever I run totem from a shell window to play a video, I get on stderr: "(totem:13002): Gtk-WARNING **: 07:50:52.916: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale)" This has also been happening in totem in Ubuntu 18.04.4 LTS for years. I was shocked when I first ran it on 20.04 that apparently nobody else noticed this error. It happens every single time I run totem, as soon as it actually opens a video and starts playing it. For example, I made a screencast for a few seconds (with Ctl-Alt- Shift-R) and then played it from "totem ~/Videos/Screencast*.webm", and this error came out on stderr. If I just run "totem &" the error doesn't come out -- until I select a video from totem's interface. Once I pick one and play it, then the error comes out on the terminal screen where I typed the totem command. Is there supposed to be a slider for scaling the video? That would be a nice feature, but no slider appears, possibly due to this bug... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 07:46:58 2020 ExecutablePath: /usr/bin/totem LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873407 Title: totem warns every time: "Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1873407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873398] [NEW] gnome-disks won't do SMART on NVME drive
Public bug reported: I'm running 20.04 beta amd64 Desktop from a USB stick of the live ISO. I opened Disks (gnome-disks) and it sees all my drives, but it won't show SMART stats on my NVME drive (Samsung SSD 970 EVO Plus 500GB). The SMART menu item is greyed out. It works fine on other drives. The NVME has SMART support; it works fine with smartctl -a /dev/nvme0n1 for example. (Though smartctl is not in this live ISO, I have apt-get installed it at another time and tried it; and it works fine in the Ubuntu 18.04 that is installed on this machine.) I've attached a screencast showing the failure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 07:32:43 2020 ExecutablePath: /usr/bin/gnome-disks LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screencast of Disks failing to show SMART data on NVME drive" https://bugs.launchpad.net/bugs/1873398/+attachment/5355919/+files/Screencast%20from%2004-17-20%2007%3A38%3A22.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873398 Title: gnome-disks won't do SMART on NVME drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1873398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873396] [NEW] Software & Updates hangs and won't close if IPv6 but no IPv4 connectivity
Public bug reported: I was running Ubuntu 20.04 beta x86_64 desktop without installing it. Went into Settings, to About, clicked "Software Updates", and up popped this window. My LAN has public IPv6 connectivity but this machine's ethernet address was configured with an IPv4 address that doesn't have global connectivity, just local ethernet. The window hung and would not close when I clicked the [X] in the upper right corner. (Eventually I got the "Force Quit?" pop-up from the window manager and was able to successfully force it to quit.) But -- its UI should always be responsive, no matter what is happening on the network. The bug-filing page here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+filebug/1a28ffd4-807c-11ea-a586-0025b3df357a? told me: We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 3) What you expected to happen 4) What happened instead But lsb-release isn't on this (uninstalled live iso) system: ubuntu@ubuntu:~$ lsb-release -rd Command 'lsb-release' not found, did you mean: command 'lsb_release' from deb lsb-release (11.1.0ubuntu2) Try: sudo apt install ubuntu@ubuntu:~$ I dno't know what "System -> About Ubuntu" means. There isn't a "System" menu visible. I did go to Settings -> About and it says "Ubuntu Focal Fossa (development branch)" -- but it won't let me select and copy that string! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 07:21:25 2020 ExecutablePath: /usr/bin/software-properties-gtk InterpreterPath: /usr/bin/python3.8 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873396 Title: Software & Updates hangs and won't close if IPv6 but no IPv4 connectivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1873396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
Just for fun I tried to start it manually. $ pulseaudio --start --log-level=debug --verbose D: [pulseaudio] conf-parser.c: Parsing configuration file '/etc/pulse/client.conf' D: [pulseaudio] conf-parser.c: Failed to open configuration file '/etc/pulse/client.conf.d/01-enable-autospawn.conf': No such file or directory E: [pulseaudio] main.c: Daemon startup failed. And whoopsie pops up with the same old crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
Besides this Whoopsie catch of pulseaudio crashing, the result is that audio doesn't work at all on the system. Settings -> Sound shows no options for the output or input devices, the "Test" button says to click on a speaker to test it but then shows zero speakers, just the icon of a person, etc. I am happy to try daily builds or patched versions on this motherboard if someone wants to try to debug it. (Also, comment #7 says "tracking in (url)" but I as an ordinary user don't seem to have access to that URL. It just shows me a graph of all error reports for all releases. So I can't see if y'all have a workaround that I could try, or want people who get this error to run some diagnostic or anything...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835660] Re: initramfs unpacking failed
This happened for me yesterday, when booting the main Ubuntu 20.04 beta x86_64 iso on real hardware (not a virtual machine). It has a graphical splash screen but in the upper left corner I get this "console" message. Then eventually in a few seconds, after it has fully booted, that splash screen is replaced and the system has booted up fine. But it's a worry- producing message that should really not be there. If the kernel is actually able to handle the stock ISO's initramfs, then please change the kernel boot process to not produce an error message when there is no error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1274678] Re: Unable to unmount nfsv3 when server is inaccessible
This error occurs on an NFS client machine when one of its NFS servers stops responding (e.g. is powered-off). The umount command provides a -l (lazy) option that is supposed to disconnect the mount point from the system so that no future commands that access the file system will hang due to the unresponsive NFS server. This is supposed to work even when the NFS server is not responding. The problem is that a sub-library used by the umount command is doing a readlink() on the filesystem, which causes a hang before umount can actually unmount the filesystem. The umount program uses a helper program called /sbin/umount.nfs (which is a symlink to /sbin/mount.nfs, and both are part of the nfs-common package), and that's where the bug lies. When you do: umount -l /images and /images is an NFS mount, umount invokes: /sbin/umount.nfs /images -l and /sbin/umount.nfs does the readlink, which can easily be verified by running the umount command under strace -f. Here is a GDB backtrace of /sbin/umount.nfs when it hangs: (gdb) run /images -l Starting program: /sbin/umount.nfs /images -l [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. Breakpoint 1, readlink () at ../sysdeps/unix/syscall-template.S:81 81 ../sysdeps/unix/syscall-template.S: No such file or directory. (gdb) bt #0 readlink () at ../sysdeps/unix/syscall-template.S:81 #1 0xb7768a0a in ?? () from /lib/i386-linux-gnu/libmount.so.1 #2 0xb7756073 in mnt_resolve_path () from /lib/i386-linux-gnu/libmount.so.1 #3 0xb7762887 in ?? () from /lib/i386-linux-gnu/libmount.so.1 #4 0xb77666f0 in mnt_context_prepare_umount () from /lib/i386-linux-gnu/libmount.so.1 #5 0x0804afc1 in ?? () #6 0xb75b9a83 in __libc_start_main (main=0x804ad10, argc=3, argv=0xbfcc2e34, init=0x8057b40, fini=0x8057bb0, rtld_fini=0xb77cc180 _dl_fini, stack_end=0xbfcc2e2c) at libc-start.c:287 #7 0x0804b4fc in ?? () The actual readlink() call seems to occur in libmount, from a function under mnt_resolve_path. If, under GDB, I cause the readlink function to artificially return -1 rather than do the system call, the rest of the program succeeds in lazily unmounting the hung filesystem. I don't know if the proper fix is for /sbin/umount.nfs to avoid calling mnt_resolve_path, or to pass it a parameter that says, Don't touch that filesystem while trying to resolve the path!!!. I will leave that to the maintainers. All I know is that it hangs forever if you let the readlink system call occur, but it does the job it's supposed to do if you breakpoint at the readlink and do return (int)-1 and continue in the debugger. ** Summary changed: - Unable to unmount nfsv3 when server is inaccessible + Unable to lazy unmount nfsv3 when server is inaccessible -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274678 Title: Unable to lazy unmount nfsv3 when server is inaccessible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1274678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1274678] Re: Unable to lazy unmount nfsv3 when server is inaccessible
The version of nfs-common that I found the bug in is: nfs- common-1:1.2.8-6ubuntu1.1 which is from the trusty-updates repository. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274678 Title: Unable to lazy unmount nfsv3 when server is inaccessible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1274678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1274678] Re: Unable to lazy unmount nfsv3 when server is inaccessible
I found this bug today in ubuntu-14.04.2 LTS. I don't see in the Launchpad interface how to easily specify which release(s) the bug appears in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274678 Title: Unable to lazy unmount nfsv3 when server is inaccessible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1274678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 412351] Re: nfs server stand-by cause client hang
When mounting with the intr option, you have to interrupt a stalled program (using Control-C in a terminal, for example) in order to get it to stop trying to access the server. If you instead mount with the soft option, NFS accesses will eventually time out without needing to be interrupted (but you may lose data if you were writing to the NFS filesystem -- the written data will not get saved anywhere because the server isn't responding.) When the server is hung, you should be able to unmount the server's filesystem using the -l (lazy) option (umount -l /opt/user1) to avoid future hangs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/412351 Title: nfs server stand-by cause client hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/412351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466217] Re: unmounting NFS filesystem hangs on readlink even with lazy unmount
*** This bug is a duplicate of bug 1274678 *** https://bugs.launchpad.net/bugs/1274678 ** This bug has been marked a duplicate of bug 1274678 Unable to unmount nfsv3 when server is inaccessible -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466217 Title: unmounting NFS filesystem hangs on readlink even with lazy unmount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466217] [NEW] unmounting NFS filesystem hangs on readlink even with lazy unmount
Public bug reported: This error occurs on an NFS client machine when one of its NFS servers stops responding (e.g. is powered-off). The umount command provides a -l (lazy) option that is supposed to disconnect the mount point from the system so that no future commands that access the file system will hang due to the unresponsive NFS server. This is supposed to work even when the NFS server is not responding. The problem is that a sub-library used by the umount command is doing a readlink() on the filesystem, which of course causes a hang before umount can actually unmount the filesystem. The umount program uses a helper program called /sbin/umount.nfs (which is a symlink to /sbin/mount.nfs), and that's where the bug lies. When you do: umount -l /images and /images is an NFS mount, umount invokes: /sbin/umount.nfs /images -l and /sbin/umount.nfs (which is part of the nfs-common package) does the readlink, which can easily be verified by running it under strace -f. Here is a GDB backtrace of /sbin/umount.nfs when it hangs: (gdb) run /images -l Starting program: /sbin/umount.nfs /images -l [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. Breakpoint 1, readlink () at ../sysdeps/unix/syscall-template.S:81 81 ../sysdeps/unix/syscall-template.S: No such file or directory. (gdb) bt #0 readlink () at ../sysdeps/unix/syscall-template.S:81 #1 0xb7768a0a in ?? () from /lib/i386-linux-gnu/libmount.so.1 #2 0xb7756073 in mnt_resolve_path () from /lib/i386-linux-gnu/libmount.so.1 #3 0xb7762887 in ?? () from /lib/i386-linux-gnu/libmount.so.1 #4 0xb77666f0 in mnt_context_prepare_umount () from /lib/i386-linux-gnu/libmount.so.1 #5 0x0804afc1 in ?? () #6 0xb75b9a83 in __libc_start_main (main=0x804ad10, argc=3, argv=0xbfcc2e34, init=0x8057b40, fini=0x8057bb0, rtld_fini=0xb77cc180 _dl_fini, stack_end=0xbfcc2e2c) at libc-start.c:287 #7 0x0804b4fc in ?? () The actual readlink() call seems to occur in libmount, from a function under mnt_resolve_path. If, under GDB, I cause the readlink function to artificially return -1 rather than do the system call, the rest of the program succeeds in lazily unmounting the hung filesystem. I don't know if the proper fix is for /sbin/umount.nfs to avoid calling mnt_resolve_path, or to pass it a parameter that says, Don't touch that filesystem while trying to resolve the path!!!. I will leave that to the maintainers. All I know is that it hangs forever if you let the readlink system call occur, but it does the job it's supposed to do if you breakpoint at the readlink and do return (int)-1 and continue in the debugger. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466217 Title: unmounting NFS filesystem hangs on readlink even with lazy unmount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066342] Re: Reinstalling over a previous installation with encrypted swap displays a Continue without swap warning dialog
This is not fixed in Ubuntu-Gnome 14.04.2 LTS. I recently installed Ubuntu-Gnome 14.04.2 LTS on a few machines and invented a workaround. The script that sets up encrypted swap (/usr/bin /ecryptfs-setup-swap) should first do a mkswap on the partition (if it isn't already set up), then use the offset= parameter in crypttab to avoid clobbering the first bytes of the swap partition. I set it to 2048 (512-byte blocks, totaling 1MB) because megabyte alignment of partitions is now the default for avoiding performance issues in disk drives with various physical block sizes, yet losing only 1 megabyte from a swap partition is a tiny fraction of a modern swap partition, and thus easily tolerable. My crypttab currently reads: cryptswap1 UUID=b742ddee-4f75-4826-9c43-2a08778560d4 /dev/urandom swap,cipher=aes-xts-plain64:sha256,size=512,offset=2048 The relevant change is offset=2048 on the end. This does not allow the installer to automatically detect swap from a PREVIOUSLY encrypted swap partition that starts at offset=0. But if the installer starts doing this now, FUTURE installers will be able to see the swap partition as a swap partition, and can use it either encrypted or not. Also, this allows the swap partition to be detected via its UUID. When encrypted with the offset defaulting to zero, it encrypts the UUID, puts the UUID into crypttab, and then subsequent reboots cannot find the swap partition. One additional change is in this crypttab for your consideration: I changed from the default cipher to aes-xts-plain64 (and the key size from 256 to 512) because the dm-crypt documentation says it's a better choice than the default. I also recommend that the installer provide a checkbox to allow users to encrypt their swap partition even if they don't encrypt their file systems or drives. This is because active keys and other valuable data needing protection often exist in process address spaces that get written to the swap partition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066342 Title: Reinstalling over a previous installation with encrypted swap displays a Continue without swap warning dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1066342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340970] Re: When apport complains package is outdated, it doesn't let you update
The issue is worse than as reported above. apport in Ubuntu 14.10 beta1 won't even let you report a bug in an application when ANY package in the system is not the absolute latest! I got a core-dump crash in Rhythmbox and this was the eventual result from apport (when I came across it on my screen hours later): The problem cannot be reported: You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs: acl, apt, apt-utils, bsdutils, cgmanager, coreutils, dbus, dbus-x11, dictionaries-common, enchant, firefox, geoip-database, gettext, gettext- base, gir1.2-gdkpixbuf-2.0, gir1.2-gst-plugins-base-1.0, gir1.2-gstreamer-1.0, gir1.2-gtk-3.0, gir1.2-javascriptcoregtk-3.0, gir1.2-peas-1.0, gir1.2-soup-2.4, gir1.2-webkit-3.0, glib-networking, glib-networking-common, glib-networking-services, groff-base, gstreamer1.0-plugins-base, gstreamer1.0-plugins-good, gstreamer1.0-pulseaudio, gstreamer1.0-x, gvfs, gvfs-backends, gvfs- common, gvfs-daemons, gvfs-libs, iproute2, isc-dhcp-client, isc-dhcp- common, libacl1, libapparmor1, libapt-inst1.5, libapt-pkg-perl, libapt- pkg4.12, libarchive13, libasprintf-dev, libasprintf0c2, libattr1, libblkid1, libbsd0, libburn4, libcap-ng0, libcgmanager0, libclone-perl, libcups2, libcurl3-gnutls, libdbus-1-3, libdmapsharing-3.0-2, libelf1, libenchant1c2a, libexif12, libfile-fcntllock-perl, libfreetype6, libgdk- pixbuf2.0-0, libgdk-pixbuf2.0-common, libgettextpo-dev, libgettextpo0, libglib2.0-0, libglib2.0-data, libgpg-error0, libgstreamer-plugins- base1.0-0, libgstreamer-plugins-good1.0-0, libgstreamer1.0-0, libgtk-3-0, libgtk-3-bin, libgtk-3-common, libgudev-1.0-0, libhunspell-1.3-0, libimobiledevice4, libio-pty-perl, libisofs6, libjavascriptcoregtk-3.0-0, libldap-2.4-2, liblist-moreutils-perl, liblocale-gettext-perl, libmirclient8, libmirclientplatform-mesa, libmircommon1, libmount1, libmpdec2, libnet-dns-perl, libnet-libidn- perl, libnet-ssleay-perl, liborc-0.4-0, libpam-systemd, libparted2, libpeas-1.0-0, libpeas-common, libperlio-gzip-perl, libpopt0, libpulse0, libpython2.7, libpython2.7-minimal, libpython2.7-stdlib, libpython3.4, libpython3.4-minimal, libpython3.4-stdlib, librsvg2-2, librsvg2-common, libsepol1, libsmartcols1, libsmbclient, libsocket6-perl, libsoup- gnome2.4-1, libsoup2.4-1, libsqlite3-0, libstartup-notification0, libsub-identify-perl, libsub-name-perl, libsystemd-daemon0, libsystemd- journal0, libsystemd-login0, libtelepathy-glib0, libtext-charwidth-perl, libtext-iconv-perl, libtext-soundex-perl, libudev1, libuuid1, libwbclient0, libwebkitgtk-3.0-0, libwebkitgtk-3.0-common, libxcb-util0, lintian, mount, multiarch-support, parted, perl, perl-base, perl- modules, python-apt-common, python-gi, python-gobject, python2.7, python2.7-minimal, python3-apt, python3-gi, python3.4, python3.4-minimal, samba-libs, systemd, systemd-shim, t1utils, tzdata, udev, usbmuxd, util-linux, uuid-runtime, x11-common So, on how many levels is this wrong? First, this problem may not be easy to reproduce. So throwing away the bug report until every package is updated will mean the bug just doesn't get reported, which means it will never be fixed. Second, the bug is almost certainly not fixed by installing any of those updates. Third, the package containing the bug isn't even in the list of things-that-need-updates!!! It won't report a core dump in rhythmbox because I haven't updated Firefox? Come on! Fourth, I just installed this system a few days ago, from the very latest release media available (Ubu Gnome 14.10 beta1). Refusing to even report the bugs IN THE RELEASE MEDIA is foolish. Not everybody lives on a gigabit connection and perhaps a few people actually want to run software that they have the source code for -- not just the latest binary that somebody threw on a server somewhere. Fifth, most people are NEVER going to have the absolute latest everything installed. Poof, no bug reports! All this is explainable if you consider that the apport maintainers might prefer if FEWER bugs were filed. It's so much simpler to maintain packages when the system won't let bugs be reported against them -- not even crashes that produce core dumps. You could simplify both the user interaction and eliminate many of the other bugs reported against apport if you just insert exit(0) as the first line of the main routine of apport. This is a much more straightforward way to prevent end users from filing bugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/340970 Title: When apport complains package is outdated, it doesn't let you update To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/340970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 454358] Re: karmic ubiquity installer hangs in partitioner after dismounting 2nd drive
It's only end of life because the bug-handling team sat on it without action for four years. This bug is not MY problem, it's yours. No, I am neither able nor willing to reproduce this with a later Ubuntu release. I've switched to Fedora. If you actually care about addressing the bug that I wasted a few hours chasing down and reporting to you, the bug report contains all the information that YOU need to reproduce it (on Karmic or any later release). I did my part. You could've tried to reproduce it, then reported I can't reproduce it, neither in Karmic nor the latest release, showing good faith on your part, and then it would be worth my time to help chase it down. But since your response is just a lazy attempt to chivvy the bug into a closed due to EOL status without actually doing any work to solve the underlying problem, why should I waste any more time here? If I did reproduce it in 12.04 or 13.10, I have every reason to expect another multi-year delay and then another demand that if I don't work on it some more, you'll just close it unfixed. I suggest making a new category for bugs closed because we aren't interested in addressing them and closing it into that category. It'll be a very popular category. Merely closing the bug would leave the incorrect implication that it had been fixed -- or even investigated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/454358 Title: karmic ubiquity installer hangs in partitioner after dismounting 2nd drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/454358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172002] Re: Install doesn't mount encrypted swap for reinstall
*** This bug is a duplicate of bug 1066342 *** https://bugs.launchpad.net/bugs/1066342 ** This bug has been marked a duplicate of bug 1066342 Reinstalling over a previous installation with encrypted swap displays a Continue without swap warning dialog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172002 Title: Install doesn't mount encrypted swap for reinstall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1172002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 882147] Re: overlayfs does not implement inotify interfaces correctly
Inotify is not defined to return a subset of changes. It's defined to return all changes. That's why this is a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882147 Title: overlayfs does not implement inotify interfaces correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/882147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977847] [NEW] won't install in livecd, fails to configure
Public bug reported: I wanted to mount an NFS disk in the LiveCD, so I tried a mount command; that didn't work. Turned out that the NFS support isn't even in the livecd, so I had to apt-get install nfs-common. This failed, even immediately after apt-get update: # apt-get install nfs-common Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libgssglue1 libnfsidmap2 libtirpc1 rpcbind The following NEW packages will be installed: libgssglue1 libnfsidmap2 libtirpc1 nfs-common rpcbind 0 upgraded, 5 newly installed, 0 to remove and 516 not upgraded. Need to get 232 kB/410 kB of archives. After this operation, 1,296 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://archive.ubuntu.com/ubuntu/ precise/main nfs-common i386 1:1.2.5-3ubuntu3 [232 kB] Fetched 232 kB in 1s (119 kB/s) Selecting previously unselected package libgssglue1. (Reading database ... 136122 files and directories currently installed.) Unpacking libgssglue1 (from .../libgssglue1_0.3-4_i386.deb) ... Selecting previously unselected package libtirpc1. Unpacking libtirpc1 (from .../libtirpc1_0.2.2-5_i386.deb) ... Selecting previously unselected package rpcbind. Unpacking rpcbind (from .../rpcbind_0.2.0-7ubuntu1_i386.deb) ... Selecting previously unselected package libnfsidmap2. Unpacking libnfsidmap2 (from .../libnfsidmap2_0.25-1ubuntu1_i386.deb) ... Selecting previously unselected package nfs-common. Unpacking nfs-common (from .../nfs-common_1%3a1.2.5-3ubuntu3_i386.deb) ... Processing triggers for man-db ... Processing triggers for ureadahead ... Setting up libgssglue1 (0.3-4) ... Setting up libtirpc1 (0.2.2-5) ... Setting up rpcbind (0.2.0-7ubuntu1) ... Removing any system startup links for /etc/init.d/rpcbind ... start: Unknown job: portmap invoke-rc.d: initscript portmap, action start failed. dpkg: error processing rpcbind (--configure): subprocess installed post-installation script returned error exit status 1 Setting up libnfsidmap2 (0.25-1ubuntu1) ... dpkg: dependency problems prevent configuration of nfs-common: nfs-common depends on rpcbind (= 0.2.0-6ubuntu1); however: Package rpcbind is not configured yet. dpkg: error processing nfs-common (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin ... ldconfig deferred processing now taking place No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: rpcbind nfs-common E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rpcbind 0.2.0-7ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 CasperVersion: 1.312 Date: Tue Apr 10 08:28:12 2012 LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rpcbind UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rpcbind (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977847 Title: won't install in livecd, fails to configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/977847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977847] Re: won't install in livecd, fails to configure
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977847 Title: won't install in livecd, fails to configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/977847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 882147] Re: overlayfs does not implement inotify interfaces correctly
Mike, if inotify will not actually report all changes on an overlayfs then inotify needs to report an error when someone tries to monitor changes in an overlayfs. Pretty simple, eh? I mean, you could actually fix it so that inotify DOES report all the changes, but that would be harder than merely erroring out and forcing the userspace program to fall back to polling. (I don't know how many userspace programs, besides tail, know how to fall back to polling. But what's the point of having inotify at all, if userspace programs can't depend on it to either produce correct results, or give an error when it can't?) (I reported bug#977847 in which apt-get install nfs-common fails on the latest Ubuntu Beta2 LTS livecd because a critical system facility made the stupid mistake of depending on inotify. Either we have to tell every programmer to pretend inotify doesn't exist as a kernel facility, or we have to fix it. This is not an academic concern; end-users are noticing daily.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882147 Title: overlayfs does not implement inotify interfaces correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/882147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977847] Re: won't install in livecd, fails to configure
*** This bug is a duplicate of bug 882147 *** https://bugs.launchpad.net/bugs/882147 For those who run into this bug, which is caused by #882147, here is how to circumvent it while the boffins argue about what the right fix is. Run sudo initctl reload-configuration, and then rerun the failing apt- get install command again. You may have to do this several times (each time it will enable one more system service, until you finally get the last one done). The problem is that the system startup scripts depend on the kernel call inotify to tell them when a new startup script is added. However, inotify doesn't actually work when using an overlayfs, which is how a LiveCD allows a temporary RAM filesystem to record temporary changes that are made to the booted read-only CD/DVD image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977847 Title: won't install in livecd, fails to configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/977847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876107] [NEW] relnotes in 11.10 say to install gnome-panel but it doesn't install
Public bug reported: I hate Unity and am only interested in running new Ubuntu's if I can install gnome. The release notes here: https://wiki.ubuntu.com/OneiricOcelot/ReleaseNotes?action=showredirect=OneiricOcelot%2FTechnicalOverview say: GNOME 3.2 is included and is a major upgrade from GNOME 2.32 included in Ubuntu 11.04. GNOME Classic is no longer installed by default, but can be enabled after installation completes by installing gnome-panel THIS IS FALSE. It's easy to reproduce. While running the Live image (desktop-i386) from USB stick, I got this result: apt-get install gnome-panel Reading package lists... Done Building dependency tree Reading state information... Done Package gnome-panel is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'gnome-panel' has no installation candidate The same result occurs whether or not I have run apt-get update. To Fix: (1) Make gnome-panel installable from the repos. AND/OR (2) Change the release notes so that they don't tell people to do things that fail. Best of all would be: (3) Quit with the Not-Invented-Here attitude, don't force the Unity crud on everyone; make a simple way to delete Unity and install Gnome by default (or merely INSTALL it by default, next to Unity, and let people pick it in the login screen). ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876107 Title: relnotes in 11.10 say to install gnome-panel but it doesn't install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/876107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455068] Re: Merely starting Firefox gives user a permanent Google cookie
Just reconfirmed that this bug still exists in 11.10 (Ocelot). I started Firefox in the desktop-i386 LiveCD, went right to Preferences, clicked Privacy, changed from remember everything to custom settings, clicked View cookies, and poof, the Google PREF cookie is there, with a many-hex-digit ID field inside it. Thanks, Ubuntu, for selling out your customers' privacy! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/455068 Title: Merely starting Firefox gives user a permanent Google cookie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/455068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 862928] [NEW] NFS filesystems are not exported after booting
Public bug reported: I have an 11.04 Natty system that was upgraded from earlier releases. It exports several filesystems via NFSv3 for use by other machines on the local network. When I boot the machine, those filesystems are not exported by default. Immediately after logging in after a reboot, I can get a terminal and run showmount -e, which shows no filesystems exported. If I then run sudo exportfs -rv, it exports them without trouble. The problem is that it doesn't do this by default. E.g. after a powerfail, it won't restart by providing the filesystems; I have to export them manually! What good is a server that doesn't serve? In investigating other bugs relating to network service startup, I thought the problem might be that it tries to export to these hosts before DNS is available. So I installed bind9 and made it a secondary server for the relevant domains. Thus, it should be able to resolve domain names even before the network comes up. That didn't help. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/862928 Title: NFS filesystems are not exported after booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/862928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 862928] Re: NFS filesystems are not exported after booting
I have found a way to reconfigure the system to resolve the problem. However, there is still a bug in the default configuration of Ubuntu. The problem DOES appear to be name resolution. Even with bind9 installed, the local system is never configured to set /etc/resolv.conf to USE the local nameserver! When I configured that manually, by editing /etc/resolv.conf, then rebooted, it properly exported the filesystems -- for a single boot. But then NetworkManager overwrote /etc/resolv.conf with its own crazy idea of how to resolve domain names, and on the second reboot, it failed to export the filesystems. But this at least showed what the problem was. And enough talented sysadmins had already seen THIS problem that they came up with a big kludge script (apt-get install resolvconf) and patched all of the applications that love to clobber /etc/resolv.conf to call it. So after I installed the resolvconf package, and made sure that /etc/default/bind9 was set to RESOLVCONF=yes so that it would automatically inject localhost into resolvconf, everything started working. This problem CLEARLY should be fixed in the default configuration. Forcing resolvconf and bind9 won't work, because the system can't know how to configure bind9 so it'll locally store a cache of the domain names that /etc/exports needs to resolve. I don't know how to fix this -- the complexities of upchuck are beyond me. I think you'll have to actually let upchuck know that, yes, /etc/exports MIGHT INDEED contain domain names and MIGHT INDEED have to look them up, so if domain service isn't yet working, then oops, DON'T RUN exportfs yet. Or, as an old programmer warrior often told me, I can make your program run arbitrarily fast if you don't mind it producing the wrong answer. Upchuck has to produce the right answer -- THEN make things as fast as possible within that constraint. ** Also affects: upstart Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/862928 Title: NFS filesystems are not exported after booting To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/862928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806284] [NEW] nfs-kernel-server fails: hostname has non-inet addr on boot, before eth0 comes up
Public bug reported: I upgraded my server to Natty and now the two directories that this server exports to various other machines on the network, do not get exported during an ordinary bootup. However, after startup, if I run exportfs -av on them, they export just fine. /var/log/syslog shows: Jul 5 16:17:54 om exportfs[1585]: name1.frob.com has non-inet addr Jul 5 16:17:54 om exportfs[1585]: last message repeated 3 times Jul 5 16:17:54 om exportfs[1585]: name2.frob.com has non-inet addr Jul 5 16:17:54 om exportfs[1585]: name2.frob.com has non-inet addr (I've replaced the actual names with name1.frob.com and name2.frob.com). The problem appears to occur because NetworkManager is still in the process of bringing up the network interface (according to other interleaved syslog reports). These hostnames need DNS from another server to resolve them. The root cause of the problem appears to be that Natty doesn't make the nfs-kernel-server service wait until the first Ethernet comes up. Thus, nfs-kernel-service can't resolve domain names in the /etc/exports file, and it produces this very confusing message and doesn't actually export the filesystems. Ubuntu release: 11.04 (natty) Version of nfs-utils: Installed: 1:1.2.2-4ubuntu5 Related programs: upstart, NetworkManager ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Tags: upstart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806284 Title: nfs-kernel-server fails: hostname has non-inet addr on boot, before eth0 comes up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/806284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 458453] Re: beam.smp uses lots of CPU on desktopcouch contacts lookup
It was apparently started by gwibber (perhaps because I briefly opened the menu in the upper right corner of the Ubuntu Natty screen, which seems to be a gwibber thing; I do not use social networking). One possible problem is that the Erlang runtime is started with the -heart option, so it burns time whether or not any demands are placed on it. Is there a reason that the desktop couchdb instance needs a heartbeat? The heart process wakes up every 5 seconds, forever. And it demands that the main process wake up as frequently, too. This means that the CPU can never stop running for more than 5 seconds, even when the machine is completely idle. The main process seems to wake up every 10 minutes and write a few lines to the logfiles. There is no apparent reason for this activity. I have attached my logfile. ** Attachment added: $HOME/.cache/desktop-couch/desktop-couchdb.log.1 https://bugs.launchpad.net/ubuntu/+source/erlang/+bug/458453/+attachment/2177239/+files/desktop-couchdb.log.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/458453 Title: beam.smp uses lots of CPU on desktopcouch contacts lookup To manage notifications about this bug go to: https://bugs.launchpad.net/desktopcouch/+bug/458453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 458453] Re: beam.smp uses lots of CPU on desktopcouch contacts lookup
I upgraded my Ubuntu 10.04 system to 11.04 recently. I do not use Evolution, Ubuntu One, or Gwibber or Weather. Yet I still find this beam.smp process has burned 979 minutes of CPU since the last reboot 18 days ago -- apparently for no reason at all. First, why is it getting started at all? ps ax --forest shows it's run from /usr/bin/couchdb but there's no indication about why Apache CouchDB is running at all. dpkg -S shows it's from the couchdb-bin package. When I try to remove that package with apt-get remove, it also wants to remove desktopcouch and evolution-couchdb. I don't use any of those things. Aha, a clue: apt-cache show evolution-couchdb reports that This package provides support for the Evolution mail and calendar program to access CouchDB databases (http://couchdb.apache.org), a replication and synchronization database of JSON documents, used by online services like UbuntuOne at http://ubuntuone.com;. Great, so in Canonical's haste to use its Ubuntu distribution funnel to drive revenues to its unrelated server cluster business, they stuck everyone with this package that burns up CPU even when nobody uses it. Clever. Even more clever is that after I removed those three packages (couchdb- bin, desktopcouch, evolution-couchdb), the damn beam.smp process IS STILL RUNNING, burning up CPU! That's a packaging problem for sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/458453 Title: beam.smp uses lots of CPU on desktopcouch contacts lookup To manage notifications about this bug go to: https://bugs.launchpad.net/desktopcouch/+bug/458453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510212] Re: update-manager: no branding. Is it legit?
The problem (as reported) seems to be that it pops up without warning, but doesn't identify itself as a part of the Ubuntu system. To anyone who's used to annoying or harmful Windows or Web pop-ups, it looks like another one of those, trying to scam the user into something. Upgrade the system for important security updates -- right! How can the program clearly indicate that it isn't malware? (In a way that real malware would find hard to replicate.) Perhaps it shouldn't do unprovoked pop-ups at all? Merely putting something in the panel (and in a notification that shows up periodically?) that shows how many packages can be upgraded (and the maximum severity of the issues that provoked the updates) might be a good fix. If the user clicks on the panel item, THEN they would get a window popping up -- when they expect to see one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510212 Title: update-manager: no branding. Is it legit? -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 694283] Re: Encrypt my home folder should be disabled when Log in automatically is selected
The problem with disabling the Encrypt my home directory option when Login automatically is selected is that people who want to encrypt their home directory have no way to figure out why it's greyed out. (Now, if Gnome supported hitting a greyed-out item and getting a message about why it's greyed out, that would not be an issue -- but that's a major user interface bug that nobody in the UI community seems interested in fixing. It's been that way since the Mac stole the UI from the Xerox Star. If an item is disabled, you just have to GUESS at why, unlike in a command-line UI, where you can order the program to do something, and it has to tell you something when it can't. Ideally it tells you something useful to the user about why it can't, like what you'd have to do to make the command or option start functioning.) So, it would be better to merely UNCHECK encrypt my home directory when you check Login automatically, and vice verse, leaving both of them selectable at all times. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/694283 Title: Encrypt my home folder should be disabled when Log in automatically is selected -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661364] [NEW] Python warning at UpdateManager.py:398: ...gsignal.c:2392: instance '0x9ab4278' has no handler with id '341'
Public bug reported: Binary package hint: update-manager After running update-manager from a terminal, I got this message on the terminal: /usr/lib/python2.6/dist-packages/UpdateManager/UpdateManager.py:398: Warning: /build/buildd/glib2.0-2.26.0/gobject/gsignal.c:2392: instance `0x9ab4278' has no handler with id `341' button.disconnect(id); I didn't notice any other odd behavior. This was the very first time I ran update-manager after putting UNR 10.10 on an SD card and booting my laptop (Acer Aspire One D250) from it. I did not install it on the hard drive. The SD card was made from the latest 10.04 startup disk creator and I had it discard changes between reboots rather than allocate space on the SD card for changed files. update-manager 1:0.142.20 is now installed -- but it might have updated itself. I see that 1:0.142.19 is also in the repository. So the error could have come from .19 rather than .20. What I expected to happen: No extraneous warning messages. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- Python warning at UpdateManager.py:398: ...gsignal.c:2392: instance '0x9ab4278' has no handler with id '341' https://bugs.launchpad.net/bugs/661364 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661382] [NEW] Maverick Source DVD is missing many packages
Public bug reported: I downloaded the Maverick source DVD from: http://mirror.anl.gov/pub/ubuntu-iso/DVDs/ubuntu/10.10/release/source/ I got the ubuntu-10.10-src-1.jigdo and ubuntu-10.10-src-1.template files, and ran jigdo-lite on a Lucid machine to produce the .iso, which passed all the checksums. However, the .iso is only 1.4GB: -r--r--r-- 1 gnu uucp 1515292672 2010-10-12 20:49 /d1/linux- releases/ubuntu/ubuntu-10.10-src-1.iso It is missing many packages. For example, just in the z's: $ /mnt/ubu10.10src/pool/main/z$ ls zip zlib zope.interface zsh But in my installed Maverick UNR laptop, dpkg -l shows zeitgeist and zenity packages that are installed but which are not on this source DVD. For another example, compiz is not in the source release: $ find /mnt/ubu10.10src -name \*compiz\* -print produces nothing. These packages were in the daily source release builds that preceded the final Maverick release, e.g.: $ find /mnt/mav -name \*compiz\* -print produces a dozen lines of output, when run against maverick- daily-20101005-src-1.iso What I expected to happen: I expected the source code of every package in the released Ubuntu CDs and DVDs to appear in the Source DVD. I also expected the source code of GPL and LGPL licensed packages, such as compiz, to be available alongside the binaries. ** Affects: ubuntu Importance: Undecided Status: New -- Maverick Source DVD is missing many packages https://bugs.launchpad.net/bugs/661382 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 646421] Re: oem-config process that zero's swap broken on armel preinstalled images
Also note that this dd should specify a blocksize, rather than defaulting to 512 byte writes. This will vastly speed up the process of clearing encrypted swapspace. See bug #432422. -- oem-config process that zero's swap broken on armel preinstalled images https://bugs.launchpad.net/bugs/646421 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655402] [NEW] doesn't let me buy software without a Launchpad account (which it won't help me create)
Public bug reported: Binary package hint: software-center There should be a clear, obvious way to register for a new Launchpad account while making a software purchase. We were asked to test the software-purchase capabilities of the software-center, so I tried to buy the $1 wallpaper test package. I ran the LiveCD (from SD card) of 10.10-RC UNR, ran the Software Center, navigated to For Purchase, clicked the Wallpapers, clicked Buy. It popped up a window to get me to login to Launchpad. This window would not allow a new user (who's not already a Launchpad user) to register -- only existing users to login. I tried entering a working email address that Launchpad has never seen, plus a new password, and it reports Password didn't match. When I enter that email address and no password at all, it reports Required field. When I try clicking Forgot your password (because it gives me no other choices), it ran me through a captcha, claimed to have sent me an email (which didn't arrive within 10 min - possibly my mail server was rejecting mail) and wanted a confirmation code. If I try hitting Cancel (the only other option) it says OpenID failed and then there's nothing left to do but close that pop-up, which puts me back at the screen where I tried to buy the software. I came in from IP addr 209.237.225.227; perhaps you can trace this in the logs. But it seems simple enough to reproduce -- just try entering a new email address (that Launchpad has never seen) at the prompt. ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: purchase -- doesn't let me buy software without a Launchpad account (which it won't help me create) https://bugs.launchpad.net/bugs/655402 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655406] [NEW] pop-up for buying software is too small for underlying text
Public bug reported: Binary package hint: software-center UNR 10.10-RC on 10.1 Acer Aspire One D250 netbook, running from SD card as LiveCD. I tried to buy the Wallpaper test item. It popped up a window to authenticate me to Launchpad. Unfortunately, the text in that window is too large for the pop-up, requiring users to scroll around just to see the Continue button. The top half of the popup consists of nothing but an orange bar and a big white bar -- it's completely wasted space. The popup ends up with both horizontal and vertical scrollbars. Oh my god! I tried scrolling both of those scrollbars, and found the cure for just-reported bug #655402 - a New User button that's so far off the right-hand side of the window that I didn't even suspect its existence. ** Affects: software-center (Ubuntu) Importance: Undecided Status: New -- pop-up for buying software is too small for underlying text https://bugs.launchpad.net/bugs/655406 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655406] Re: pop-up for buying software is too small for underlying text
** Attachment added: Screen shot of too-small popup window https://bugs.launchpad.net/bugs/655406/+attachment/1674164/+files/Screenshot.png -- pop-up for buying software is too small for underlying text https://bugs.launchpad.net/bugs/655406 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655402] Re: doesn't let me buy software without a Launchpad account (which it won't help me create)
Bug #655406 is the cause of this -- the New Account button is so far off the right-hand side of the window that I never suspected its existence. -- doesn't let me buy software without a Launchpad account (which it won't help me create) https://bugs.launchpad.net/bugs/655402 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649553] Re: system hangs, bounces, oom-killer invoked on UNR live SD card
This is not a fucking question, it's a fucking bug report. But feel free to ship your precious Maverick release with this bug, because you ignored the bug report. -- system hangs, bounces, oom-killer invoked on UNR live SD card https://bugs.launchpad.net/bugs/649553 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649553] Re: system hangs, bounces, oom-killer invoked on UNR live SD card
Mr. Marconi apparently forged my name to an Ubuntu Questions posting here: https://answers.launchpad.net/ubuntu/+question/127826 while simultaneously trying to close out this bug report with Status: Invalid. His recommendation -- that I should run memtest on the laptop that showed these failures -- was ludicrous, but I have done it anyway and indeed memtest shows no failures. This is still a bug, and as far as I can see, nobody with any sense has looked at it yet. -- system hangs, bounces, oom-killer invoked on UNR live SD card https://bugs.launchpad.net/bugs/649553 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649553] Re: system hangs, bounces, oom-killer invoked on UNR live SD card
This is a bug report, not a fucking question. Perhaps making bug reports into questions is just another of the Ubuntu QA team's tactics to make their statistics look good. Unfortunately, good QA stats don't do anything for the quality of the actual software release. -- system hangs, bounces, oom-killer invoked on UNR live SD card https://bugs.launchpad.net/bugs/649553 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649553] Re: system hangs, bounces, oom-killer invoked on UNR live SD card
Part of the problem seems to be that the netbook normally runs Lucid with encrypted home directory and 5GB of encrypted swapspace. Thus the LiveCD boot of Maverick beta doesn't see the swap partition, because even though it has the linux-swap partition type, it doesn't have the swapspace signature in the first block (it's encrypted with a key pulled from /dev/random due to the setting in /etc/crypttab. Therefore Maverick runs totally from RAM, which seems to tickle some kernel problems even in a 1GB machine. -- system hangs, bounces, oom-killer invoked on UNR live SD card https://bugs.launchpad.net/bugs/649553 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 636206] Re: Unity crashes on opening Firefox Browser
This might well be the oom-killer - just running the 10.10 beta UNR LiveCD without swap space invokes it for all sorts of things, even on a 1GB machine. -- Unity crashes on opening Firefox Browser https://bugs.launchpad.net/bugs/636206 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610055] Re: computer stuttering, freezing, hanging, and otherwise being uncooperative
All the hangs I noticed so far in 10.10 BETA UNR on Acer Aspire One D250 (running direct from SD card with LiveCD) might have been the oom- killer, but in dmesg, I did notice some odd entries relating to the ATA ports (which I'm not using, since I'm running from the LiveCD without mounting or swapspace). Look at 7.913, 9.03, 43, 49, and 110846 seconds: [7.595226] ata1: SATA max UDMA/133 abar m1...@0x58344000 port 0x58344100 irq 44 [7.595236] ata2: DUMMY [7.595244] ata3: SATA max UDMA/133 abar m1...@0x58344000 port 0x58344200 irq 44 [7.595251] ata4: DUMMY [7.912155] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [7.913589] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [7.914055] ata1.00: ATA-8: Hitachi HTS543216L9A300, FB2OC40C, max UDMA/133 [7.914071] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [9.036998] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) [9.037660] ata1.00: configured for UDMA/133 [9.376152] ata3: SATA link down (SStatus 0 SControl 300) ... [ 38.344887] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 39.742775] Skipping EDID probe due to cached edid [ 39.872241] Skipping EDID probe due to cached edid [ 39.962468] lp: driver loaded but no devices found [ 40.054468] ppdev: user-space parallel port driver [ 43.472533] ata1.00: configured for UDMA/133 [ 43.472551] ata1: EH complete [ 47.784690] Skipping EDID probe due to cached edid [ 47.821174] Skipping EDID probe due to cached edid [ 47.857432] Skipping EDID probe due to cached edid [ 49.527846] ata1.00: configured for UDMA/133 [ 49.527863] ata1: EH complete [ 64.996154] Skipping EDID probe due to cached edid [ 342.716156] Skipping EDID probe due to cached edid [110846.899560] ata1.00: configured for UDMA/133 [110846.899579] ata1: EH complete [110846.900326] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [111088.132457] mutter invoked oom-killer: gfp_mask=0xa01d2, order=0, oom_adj=0 [111088.132469] mutter cpuset=/ mems_allowed=0 [111088.132478] Pid: 2802, comm: mutter Not tainted 2.6.35-19-generic #28-Ubuntu -- computer stuttering, freezing, hanging, and otherwise being uncooperative https://bugs.launchpad.net/bugs/610055 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649553] [NEW] system hangs, bounces, oom-killer invoked on UNR live SD card
Public bug reported: I put Maverick Beta UNR on an SD card, ran it in my Aspire One D250 laptop without installing. Was just trying it out, running mahjongg, running rhythmbox (with no music), trying to find the control panel (hiding in greyed-out stuff that scrolled off the left margin), etc, but it kept hanging for seconds and then bouncing the few windows around. I was not connected to Internet; not running a web browser. Nothing huge should be running. I started a terminal and dmesg showed that I had been hit by the oom-killer three times! Mutter killed rhythmbox, then killed ssh-agent, then killed gnome-session. Clearly the system should boot up and do simple stuff from the LiveCD without crashing for lack of memory on a 1GB laptop! I tried to submit this from the laptop itself using ubuntu-bug -p linux (as suggested in the page where I'm typing this), and it let me type everything in, and then when I submitted the bug, it said Timeout error: Sorry, something just went wrong in Launchpad. and threw away everything I'd typed. So this is all the bug report you're gonna get. Dmesg really did show three oom-kills, I promise you, and I submitted it, but your recommended procedure for submitting did not work. ** Affects: ubuntu Importance: Undecided Status: New -- system hangs, bounces, oom-killer invoked on UNR live SD card https://bugs.launchpad.net/bugs/649553 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649560] [NEW] Too hard to find control panel / settings / System in 10.10 UNR Beta
Public bug reported: Binary package hint: unity It's too hard to find out how to do something simple like change a setting. The settings are apparently buried under a grey square that rolls off the bottom of the screen during normal operation. To get to it, you seem to have to hover at the bottom left of the screen until the left margin scrolls up, then eventually a grey square comes along that doesn't look at all like settings (it's for Applications), then you have to go into the far right corner of the screen and hit System, then you can see your system control panel settings. Way too cumbersome and counterintuitive! ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: gui loses -- Too hard to find control panel / settings / System in 10.10 UNR Beta https://bugs.launchpad.net/bugs/649560 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649562] [NEW] Help icon produces garbage-unicode name popup in 10.10 beta UNR
Public bug reported: Binary package hint: unity When moving the mouse down the left margin in 10.10 beta UNR (running from LiveCD on SD card), when I come to the blue circle containing a question mark, it pops up a tooltip that says: [four Unicode characters in boxes that indicate we don't have the right font installed]. Looks like 010403, 010403, 010404, 010430 or something like that - it's pretty tiny. I had just booted up the UNR SD card, haven't changed any settings, it's all in English so far, except for this. It doesn't even know my timezone yet. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- Help icon produces garbage-unicode name popup in 10.10 beta UNR https://bugs.launchpad.net/bugs/649562 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649562] Re: Help icon produces garbage-unicode name popup in 10.10 beta UNR
Here's a screenshot of the errant tooltip. ** Attachment added: Screenshot with tooltip visible https://bugs.launchpad.net/ubuntu/+source/unity/+bug/649562/+attachment/1647265/+files/Screenshot.png -- Help icon produces garbage-unicode name popup in 10.10 beta UNR https://bugs.launchpad.net/bugs/649562 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 432422] Re: add installer status message for Wiping Swap Space
OK, so now we have a message, that's progress, but it still hangs for minutes after printing the message. How about fixing the underlying bug, which is that a shell script is doing *512-byte* writes from /dev/zero to the swap partition using dd! See comment #13 above. Making it run 1000x as fast, with full security, is *trivial* - just add a bs=16m parameter - but nobody's done it in the year since that comment. -- add installer status message for Wiping Swap Space https://bugs.launchpad.net/bugs/432422 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550850] Re: compiz exits with radeon error
I've just found a way to reproduce the issue on my system. I ran evince (the PDF viewer) on a file someone sent me, which produces a very wide window that fills the entire screen. The first time I ran this, compiz immediately died after this window went up. So I investigated. I logged out and back in, tried just running evince on this file. No crash. So logged out and back in, started four terminal windows (my usual), then evince, no crash. So started Firefox with my usual sixty or seventy tabs, then ran evince. No crash. But when I moved that window off the lower right corner of the screen (so that about 40% of it was on the screen, the rest offscreen), bam, compiz failed. I rebooted the system, logged in, started four terminals, checked dmesg (no relocation messages), started Firefox, ran evince on this file. No crash. Used the middle button in the window frame top to move it around and generally offscreen in the lower right corner. No crash. Let it sit there for a few seconds after releasing the middle button. Bam, crash! And there in dmesg were seven messages: [ 525.385000] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! [ 525.824032] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! [ 526.129675] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! [ 531.537754] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! [ 536.836914] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! [ 536.872722] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! [ 536.940502] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! I've attached the PDF file that triggers this behavior. This is on an HP dc5750 (AMD dualcore desktop, 5GB RAM, with Radeon graphics attached to 1980x1200 HP LP2465 screen). I'll attach dmesg | egrep drm|radeon output and X log. Hmm, there is an *ERROR* in dmesg about forcing to 32M GART size (because of ASIC bug ?) -- could that be related? ** Attachment added: PDF file that triggers failing compiz/drm interaction http://launchpadlibrarian.net/51151200/A%20Neuroscientist%20Uncovers%20A%20Dark%20Secret%20_%20NPR.pdf -- compiz exits with radeon error https://bugs.launchpad.net/bugs/550850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550850] Re: compiz exits with radeon error
** Attachment added: /var/log/Xorg.0.log http://launchpadlibrarian.net/51151359/Xorg.0.log -- compiz exits with radeon error https://bugs.launchpad.net/bugs/550850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550850] Re: compiz exits with radeon error
** Attachment added: dmesg | egrep drm|radeon after compiz dies http://launchpadlibrarian.net/51151406/1 -- compiz exits with radeon error https://bugs.launchpad.net/bugs/550850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550850] Re: compiz exits with radeon error
Here's a screenshot of sample screen corruption. This comes and goes (making the program repaint the window often fixes it). Notice: * Mangled fonts, e.g. in right-hand side of screen Change your plan or services mangles the g, and it's also mangled above there in messages you've used. Also mangled in the text boxes, though it's harder to tell since they got overlaid with upside-down stuff. * Welcome back! box was rendered upside-down, along with Log in to My T-Mobile. * Horizontal bar of colored static near bottom of window. Usually when I see this static, it's not so colorful, more like diagonal lines of black white. See also the steeper diagonal line of black white cutting through the bottom blue bar. Usually by the time it starts mangling fonts, it's getting close to crashing compiz within the next hour. The horizontal lines of static come and go fairly frequently, for any window that's updating on the screen, and don't seem to lead to immediate crashes. ** Attachment added: Firefox (abrowser) screenshot showing mangled fonts, upside-down sections, static near bottom of window. http://launchpadlibrarian.net/50961178/Screenshot-My%20T-Mobile%20-%20Web%20Browser.png -- compiz exits with radeon error https://bugs.launchpad.net/bugs/550850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583891] Re: X.org crashes sometimes. [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
*** This bug is a duplicate of bug 550850 *** https://bugs.launchpad.net/bugs/550850 ** This bug has been marked a duplicate of bug 550850 compiz exits with radeon error -- X.org crashes sometimes. [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! https://bugs.launchpad.net/bugs/583891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550850] Re: compiz exits with radeon error
This is also happening for me since I upgraded my HP dc5750 PC to Ubuntu 10.04. The desktop runs fine for a few days, then I start seeing odd static in windows, including lots of horizontal lines in parts of Firefox windows, plus sometimes, garbled fonts in some firefox windows. Then without warning the window manager goes away, leaving me a bunch of undecorated windows. I eventually figured out (by comparing ps listings before and after) that when that happens, compiz died. When I'm in that state (as my desktop is right now as I type this), I can run compiz from a terminal window, and it reports: WARNING: Application calling GLX 1.3 function glXCreatePixmap when GLX 1.3 is not supported! This is an application bug! drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream. See dmesg for more info. [1]+ Exit 244/usr/bin/compiz and almost immediately terminates. (It starts to decorate windows, etc, then it all gets torn down again.) dmesg reports: [356951.921231] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! a few times when that happens. It's not clear whether compiz is building a parameter to drm wrongly, or whether drm is wrongly rejecting a valid parameter from compiz. But what IS clear is that restarting compiz once the system gets into this state doesn't do any good. However, logging out (using the menu item at the upper right corner of the screen) and logging back in DOES eliminate the problem (for a few days). And a power cycle also eliminates it. What further info can we get you to help debug it? It happens pretty regularly, and when it does, I can usually type into a terminal and/or a web browser, so there's lots that could be done. (Sometimes it refuses to change the input focus while in this state; I haven't figured out why or how to work around that.) -- compiz exits with radeon error https://bugs.launchpad.net/bugs/550850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580984] Re: Running firefox causes problem with screen refreshing
*** This bug is a duplicate of bug 550850 *** https://bugs.launchpad.net/bugs/550850 ** This bug has been marked a duplicate of bug 550850 compiz exits with radeon error -- Running firefox causes problem with screen refreshing https://bugs.launchpad.net/bugs/580984 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 491572] Re: [lucid][rv350] radeon drm error (AGP)
This appears to be a duplicate of #550850 and #583891. -- [lucid][rv350] radeon drm error (AGP) https://bugs.launchpad.net/bugs/491572 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578078] Re: regular system freezes with KMS on rc410 ati video chip
I am experiencing bug #550850 (which is also duplicated several times), whose main symptom is garbled screen output followed at some length by a crash in compiz, with the error message Failed to parse relocation -12! in dmesg. There may be a correlation between these two bugs. Altogether I found five bugs which included this string, and four of them were the same bug (I marked them as dups, except this one). -- regular system freezes with KMS on rc410 ati video chip https://bugs.launchpad.net/bugs/578078 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455167] Re: Ubiquity should put install image onto target disk for apt's use
It seems that the thrust of this bug has not been perceived. Even when I have a full DVD install image sitting on the hard drive of my Ubuntu system, there appears to be no way to *install packages from it* without manually groveling around in its subdirectories and running dpkg! There appears to be no way to tell apt-get Here's a big local DVD ISO image that you can get packages from, when they haven't changed since the release. Apt-cdrom does not do this, or if somehow it does, the way to make it do this is completely unclear. (Of course, if a package has been updated since the release, apt-get should get the latest version from the net. But there's no need to get an unchanged package from the net -- it has already been downloaded once in the DVD image.) Such an option would significantly reduce the bandwidth needed for Ubuntu mirrors -- since the vast majority of subsequent package installs could come from the user's own hard drive rather than over the net. -- Ubiquity should put install image onto target disk for apt's use https://bugs.launchpad.net/bugs/455167 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455167] Re: Ubiquity should put install image onto target disk for apt's use
I'm trying to get this bug to not automatically expire. If Ubuntu keeps ignoring my bug reports then I'll just stop making bug reports -- which is not what I want and not what you want. But somehow there's this daemon for throwing away bug reports *automatically*. ** Changed in: ubiquity (Ubuntu) Status: Incomplete = New -- Ubiquity should put install image onto target disk for apt's use https://bugs.launchpad.net/bugs/455167 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 412647] Re: Firefox is not able to play mp4 video tags
The upstream bug (moz bug 422540) hasn't progressed in months; if Ubuntu developers want this feature, please lend a hand. -- Firefox is not able to play mp4 video tags https://bugs.launchpad.net/bugs/412647 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583891] Re: X.org crashes sometimes. [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
I'm not entirely convinced either. But I find it suspicious that various processes are crashing with the same kernel error message, coming from the same DRM driver in the kernel. Whichever process gets the error is the one that crashes, so when it's compiz, you have windows but no window manager; when it's X, the whole window system dies. The fact that a variety of programs are crashing -- all talking to one driver -- leads me to suspect that the bug is in the driver, not in the programs. But only time and further investigation will tell. -- X.org crashes sometimes. [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! https://bugs.launchpad.net/bugs/583891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550850] Re: compiz exits with radeon error
I had originally marked bug #583891 as a duplicate of this. Someone else detached it, arguing that it may not be the same bug because the X server or other processes are crashing with the Failed to parse relocation -12 message, rather than compiz. This makes me suspect a bug in the kernel DRM driver, rather than in compiz or the other crashing programs. Perhaps these are the same bug, perhaps different. I think that whoever looks at either bug should know about the existence of the other, though, hence this comment. -- compiz exits with radeon error https://bugs.launchpad.net/bugs/550850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248324] Re: can't access add to panel... dialogue
The changes in 10.04 seem to have made the problem worse, not better. Clever people in 9.10 used to be able to work around the problem. Now in 10.04 you have to be a true genius, or merely insane, (or find this bug report) to work around the problem. The proposed fix in #19 is to tell users to ignore the default UNR interface, switch to GNOME, and then spend a bunch of time (both in a terminal, with commands that nobody will ever find on their own, then doing further mucking about on the screen) to customize GNOME so it looks just like the default UNR interface. Then, finally, you can add one item to your panel!!! And the rationale seems to be it's compulsory.(*) Yeah, we know you made it compulsory not to edit the panel in 10.04. But this is software freedom. We can, and should, change things we don't like. Is the problem that the UNR interface is cheating by using a bunch of GNOME components, but not using a wholly separate set of GNOME properties? (So that you could customize your UNR screen, and customize your GNOME screen, and your home directory dot-files could remember both of those settings.) If it's impossible for one user to have two fully functional GNOME screen layouts, and choose among them at login time, perhaps this should be an upstream bug or feature request to the GNOME folks? (*) Perhaps this was just a non-native English speaker being unclear why it's not possible. The word compulsory often has a connotation of people who are ordering you around for no good reason -- like a corrupt policeman might, or like a bureaucrat who cares nothing for you or your freedoms. Like we'll force you, whether you like it or not. -- can't access add to panel... dialogue https://bugs.launchpad.net/bugs/248324 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455068] Re: Merely starting Firefox gives user a permanent Google cookie
I just verified that this bug is still present in Lucid 10.04 (the UNR version installed onto a fully erased drive in a netbook). (It gets a cookie from Google, but not one from the BBC any more. I'm not sure why not; the Recent Headlines smart-bookmark is still present; perhaps BBC changed their cookie practices.) -- Merely starting Firefox gives user a permanent Google cookie https://bugs.launchpad.net/bugs/455068 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581250] [NEW] Broadcom 4312 doesn't work with Lucid - needs upstream b43-fwcutter v.13
Public bug reported: Binary package hint: b43-fwcutter When first booting Lucid Netbook remix on Acer Aspire One D150, it fails to access wireless because it needs some proprietary firmware. Even after installing that with jockey, though, it barely works (very slow access, 1-second ping times, etc). Before installing the firmware, the kernel presented a detailed message saying to go to this web site and read it ALL and follow the instructions: wireless.kernel.org/en/users/Drivers/b43 On that page it says that recent Ubuntu's just work -- but it doesn't, and I think I figured out why. It also says that my wireless chipset (Broadcom 4312) uses an LP (low power) physical interface, and thus also needs a different firmware (4.178.10.4) and a later version of b43-fwcutter (v.13). Ubuntu ships Lucid with b43-fwcutter v.12 -- and the install script doesn't know to get the 4.178.10.4 firmware for this hardware. I think if the new version of b43-fwcutter was provided, and the script fixed to match the kernel page, then it would probably Just Work, as promised. --- As a second minor thing, the description of the proprietary drivers in jockey for this hardware is not understandable. It offers both Broadcom B43 wireless driver (which is really fwcutter, which doesn't install ANY drivers, just installs firmware that the Linux driver can push into the chip), and Broadcom STA wireless driver, which is something else entirely, and which appears to involve a kernel rebuild, possibly adding proprietary binary modules to it. To the naive user (or even experienced guys like me), how would I pick between the two? There's no button for further details, and little guidance; you just have to try each one and see, which is dumb. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: b43-fwcutter 1:012-1build1 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Sun May 16 02:12:18 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu-Netbook 10.04 Lucid Lynx - Release i386 (20100429.4) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: b43-fwcutter ** Affects: b43-fwcutter (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid ubuntu-une -- Broadcom 4312 doesn't work with Lucid - needs upstream b43-fwcutter v.13 https://bugs.launchpad.net/bugs/581250 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581250] Re: Broadcom 4312 doesn't work with Lucid - needs upstream b43-fwcutter v.13
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48535097/Dependencies.txt -- Broadcom 4312 doesn't work with Lucid - needs upstream b43-fwcutter v.13 https://bugs.launchpad.net/bugs/581250 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581250] Re: Broadcom 4312 doesn't work with Lucid - needs upstream b43-fwcutter v.13
I thought ubuntu-bug was going to add my dmesg and such, but stupidly it didn't, so here is dmesg and lspci -vnn. ** Attachment added: dmesg http://launchpadlibrarian.net/48535739/dmesg -- Broadcom 4312 doesn't work with Lucid - needs upstream b43-fwcutter v.13 https://bugs.launchpad.net/bugs/581250 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581250] Re: Broadcom 4312 doesn't work with Lucid - needs upstream b43-fwcutter v.13
** Attachment added: lspci -vnn http://launchpadlibrarian.net/48535749/lsp -- Broadcom 4312 doesn't work with Lucid - needs upstream b43-fwcutter v.13 https://bugs.launchpad.net/bugs/581250 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 441013] Re: The Synaptic Touchpad on my Eee Pc 701 doesn't work correctly
Oh, I see. If you add tags like needs-upstream-testing to a bug, then it becomes incomplete, so then a robot will expire it a few months later. It's a cheat to get bugs to go away. The product is so much better when bug reports get swept under the rug by people or robots who don't actually understand them. -- The Synaptic Touchpad on my Eee Pc 701 doesn't work correctly https://bugs.launchpad.net/bugs/441013 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 441013] Re: The Synaptic Touchpad on my Eee Pc 701 doesn't work correctly
This bug appears to have been fixed. The problem is as reported in comments #3 to #4, and the fix was reported in #5. Someone fixed the default value in the release. I just tested this on Lucid and it worked for me. (I don't have an EEE PC but my Acer Aspire One D250 touchpad had the same trouble before the fix went in.) Why this would need kernel logs or upstream testing, I have no idea. I think the problem is either some automated robot, or else a human acting like one, added those tags to this bug report. -- The Synaptic Touchpad on my Eee Pc 701 doesn't work correctly https://bugs.launchpad.net/bugs/441013 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455151] Re: disconnect wired network leaves IPv6 running, only disconnects IPv4
*** This bug is a duplicate of bug 215497 *** https://bugs.launchpad.net/bugs/215497 ** This bug has been marked a duplicate of bug 215497 IPv6 configuration is not flushed when interface goes down -- disconnect wired network leaves IPv6 running, only disconnects IPv4 https://bugs.launchpad.net/bugs/455151 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 412647] Re: Firefox is not able to play mp4 video tags
The problem is that Firefox-3.5 (and 3.6) contains code specific to the Ogg and Wav file formats and specific codecs. Though the original video tag support included generic gstreamer support, MozCorp for some reason rewrote that to exclude the use of system-provided codecs. See, for example, the method nsHTMLMediaElement::CanHandleMediaType() in mozilla-1.9.1/content/html/content/src/nsHTMLMediaElement.cpp, and the subsequent methods. This means that even if you have e.g. an H.323 codec installed in your Ubuntu system, Firefox won't use it to implement the video tag. This prevents Ubuntu users from playing e.g. Youtube or Vimeo videos by using free software. Strictly speaking, this is an enhancement request -- the upstream code contains a limitation that is not appropriate for Ubuntu users, but it's not strictly speaking a bug. The support in Firefox for video and audio was tracked in 3 mozilla bugs: Bare video with no codecs: https://bugzilla.mozilla.org/show_bug.cgi?id=382267 Ogg Theora/Vorbis codecs: https://bugzilla.mozilla.org/show_bug.cgi?id=422538 Gstreamer backend for video and audio: https://bugzilla.mozilla.org/show_bug.cgi?id=422540 This third set of patches is not yet in the upstream Firefox releases. It was used for prototyping the video support, it limps on embedded Firefox on the N810, but looks like it could use some love from a gstreamer expert in the Ubuntu community. ** Bug watch added: Mozilla Bugzilla #382267 https://bugzilla.mozilla.org/show_bug.cgi?id=382267 ** Bug watch added: Mozilla Bugzilla #422538 https://bugzilla.mozilla.org/show_bug.cgi?id=422538 ** Bug watch added: Mozilla Bugzilla #422540 https://bugzilla.mozilla.org/show_bug.cgi?id=422540 -- Firefox is not able to play mp4 video tags https://bugs.launchpad.net/bugs/412647 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455167] Re: Ubiquity should put install image onto target disk for apt's use
apt-cdrom does NOT work this way. It keeps insisting that I mount a physical CDROM, even when the image is mounted, even when I passed -m and -d /mnt/ubu910 to apt-cdrom add. It's just broken for use with ISO images. And if you leave an apt-cdrom entry in /etc/apt/sources.list, it screws up all possibility of using apt-get. It insists on getting everything from the CDROM, and when you don't have a CDROM, it doesn't just go on and use the network -- it keeps looping, insisting that you mount a CDROM. Maybe bandwidth is free for Canonical, but if it isn't, I really recommend fixing this stuff, so that people can just install 95% of the packages from the DVD image that they already have, without having to suck the identical package over the Internet. -- Ubiquity should put install image onto target disk for apt's use https://bugs.launchpad.net/bugs/455167 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378391] Re: Source rename clobbered local changes (so tapping not working in Karmic)
According to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/441013/comments/5: The behavior in realease Karmic has changed. You will be able to try it on a live cd and install tommorow. Enable mouse clicks with touchpad is now enabled by default. It has had this behavior since RC build. -- Source rename clobbered local changes (so tapping not working in Karmic) https://bugs.launchpad.net/bugs/378391 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 441013] Re: The Synaptic Touchpad on my Eee Pc 701 doesn't work correctly
This is not a ($*#$*#( duplicate! The problem is the regression from Jaunty. That problem was not fixed by adding a new Control Panel item that re-enables the old behavior. The problem is that you NEED to re- enable the old behavior. ** This bug is no longer a duplicate of bug 378391 Source rename clobbered local changes (so tapping not working in Karmic) -- The Synaptic Touchpad on my Eee Pc 701 doesn't work correctly https://bugs.launchpad.net/bugs/441013 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 441013] Re: The Synaptic Touchpad on my Eee Pc 701 doesn't work correctly
There are now more than a dozen bugs reported against this. See the original bug report at #378391. The problem appears to be that as people report the bug, they are marked as dups and lniked to that bug -- but that one is marked Fix Released. So nobody does anything to fix the bug, which is that the behavior regressed against Jaunty. (The fact that you can go into a Preferences item and restore the Jaunty behavior is nice, but the bug is that the Jaunty behavior changed. What worked in Jaunty does not work in Karmic.) All that's needed to *really* fix this bug is to change the default preference -- so that tapping touchpads works by default, rather than only after you enable them. -- The Synaptic Touchpad on my Eee Pc 701 doesn't work correctly https://bugs.launchpad.net/bugs/441013 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 391177] Re: touchpad tap to click should be enabled by default
*** This bug is a duplicate of bug 378391 *** https://bugs.launchpad.net/bugs/378391 This is *not* a duplicate. The original bug was about an unintentional regression. That has been fixed. This is a complaint about what appears to be an intentional regression (making tap-to-click work as before, BUT ONLY IF YOU TURN IT ON IN MOUSE SETTINGS). We can and should debate what to do about this -- but it's a DIFFERENT PROBLEM and doesn't deserve to be discarded into the the we fixed that pile. -- touchpad tap to click should be enabled by default https://bugs.launchpad.net/bugs/391177 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455151] Re: disconnect wired network leaves IPv6 running, only disconnects IPv4
Thanks for trying! And for the very explicit, useful instructions. But, no, that commit did not fix it for me. Did you try reproducing the problem yourself, or don't you have an Ethernet network that offers both DHCP for v4 address assignment and RA for IPv6 address assignment? -- disconnect wired network leaves IPv6 running, only disconnects IPv4 https://bugs.launchpad.net/bugs/455151 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315646] Re: [Feature Request] OEM config should offer support to show EULAs
Free software (and Ubuntu in particular) should not be trying to impose clickwrap contracts on end-users. Our software is licensed under a copyright license. Any terms that don't work in a copyright license (e.g. because they try to control something other than whether users can copy the software) do not belong in free software. If the software is actually free, then a user who disagrees with the proposed clickwrap license is free to decline it, and then go into his or her own machine and modify the software to eliminate the clickwrap license. Being able to remove bugs, misfeatures, and impediments from the software is the essence of the freedom that we grant to every user. I have personally done this to several attempted free software EULAs, including on Fedora, a Dell netbook, and on Mozilla Firefox. See: http://www.toad.com/gnu/sysadmin/ and search for EULA. -- [Feature Request] OEM config should offer support to show EULAs https://bugs.launchpad.net/bugs/315646 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
