[Kernel-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
** Changed in: procps (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in gamemode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in procps package in Ubuntu: Fix Committed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1979141] Re: ungrammatical line in ip-rule(8) page
** Changed in: iproute2 (Ubuntu) Importance: Undecided => Low ** Tags added: bitesize -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1979141 Title: ungrammatical line in ip-rule(8) page Status in iproute2 package in Ubuntu: New Bug description: The first line under DESCRIPTION on the ip-rule(8) man page is currently: > ip rule manipulates rules in the routing policy database control the route selection algorithm. It should have "control" changed to "that controls" (to apply to "database") or "to control" (to apply to "manipulates"). Ubuntu 22.04 LTS package version 5.15.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1979141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978488] Re: LibreOffice Writer lags freezes high CPU 22.04 LTS
** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1978488 Title: LibreOffice Writer lags freezes high CPU 22.04 LTS Status in Ubuntu MATE: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Upgraded to 22.04 LTS (20.04 no issues). Using Nvidia 4xx series driver. 48GB RAM, dual 1080ti gpu, i7 cpu. LibreOffice Writer constantly lags, losing function, freezes (does not crash) with any type of writer document (odt or xslx). New single page or existing multi-page documents, doesn't matter, same issue after a minute or two. Hates text selection, mouse-wheel scrolling is a tell- tale sign. New Writer windows opened during lag are black. CPU usage in htop is very high for soffice.bin, ~60 - 80%. Must pkill the soffice.bin and use file recover but lag freeze up will occur again soon after opening. I experience the issue with all three installation methods: snap, distro command-line install, or using the LibreOffice ppa "fresh". I've tried changing OpenCL settings, disabling all extensions, disable smooth scrolling, disabling java, have purged install/reinstall and limiting to single window. I have the Marco ppa installed (ppa:ubuntu- mate-dev/marco). Doesn't seem to matter or what mate-tweak option is selected. LO using Yaru or other theme; doesn't matter same effect. Terminal does not show me any helpful errors when Writer is called directly from command line, at least I can easily identify. Guessing this is upstream of MATE and a libreoffice thing; a few similar issues around the web but no good workaround. I can update my exact specs and kernel later as required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-03-27 (1174 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Package: nvidia-graphics-drivers-510 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Tags: third-party-packages jammy Uname: Linux 5.15.0-37-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2022-06-03 (10 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1978488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581594] Re: constantly shows wrong temperature (99°C )
** No longer affects: libatasmart (Ubuntu Yakkety)
** No longer affects: libatasmart (Ubuntu Xenial)
** No longer affects: libatasmart (Ubuntu Trusty)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libatasmart in Ubuntu.
https://bugs.launchpad.net/bugs/1581594
Title:
constantly shows wrong temperature (99°C )
Status in libatasmart:
Unknown
Status in libatasmart package in Ubuntu:
Triaged
Bug description:
Hello, here's my system info
~$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
~$ apt-cache policy udisks2
udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
*** 2.1.7-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C
(210°F), but in reality it's 30°C
~$ sudo smartctl -A /dev/sda
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050Pre-fail Always
- 0
9 Power_On_Hours 0x0012 100 100 000Old_age Always
- 24
12 Power_Cycle_Count 0x0012 100 100 000Old_age Always
- 51
168 Unknown_Attribute 0x0012 100 100 000Old_age Always
- 0
170 Unknown_Attribute 0x0003 100 100 010Pre-fail Always
- 231
173 Unknown_Attribute 0x0012 100 100 000Old_age Always
- 65539
192 Power-Off_Retract_Count 0x0012 100 100 000Old_age Always
- 23
194 Temperature_Celsius 0x0023 070 070 030Pre-fail Always
- 30 (Min/Max 30/30)
218 Unknown_Attribute 0x000b 100 100 050Pre-fail Always
- 0
231 Temperature_Celsius 0x0013 100 100 000Pre-fail Always
- 99
241 Total_LBAs_Written 0x0012 100 100 000Old_age Always
- 337
in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
works well though:
~$ sudo hddtemp /dev/sda
/dev/sda: PNY EU SSD CS1311 240GB: 30°C
To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1581594/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929209 Title: [i915] external monitor goes black for several seconds at a time, randomly Status in linux package in Ubuntu: Confirmed Bug description: At times it is completely debilitating; at other times it does not happen for hours. The physical connections are clean and solid. I guess the attachments will show that I'm using Intel graphics hardware. The monitor is a very popular Samsung one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 16:56:04 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (847 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248843] Re: upgraded from 13.04 to 13.10, network is disabled after suspend
Related bug: LP: #1184262. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248843 Title: upgraded from 13.04 to 13.10, network is disabled after suspend Status in “linux” package in Ubuntu: Confirmed Bug description: Every time after I resume from suspend, the network is disabled. It means I can't re-enable it from the network indicator. I found a workaround, I can use it until somebody will fix this issue. sudo nmcli nm sleep false Thanks, with Regards Viktor ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: viktor 2850 F pulseaudio Date: Thu Nov 7 07:26:26 2013 HibernationDevice: RESUME=UUID=22ff3f35-fc78-4f31-bf01-7daf7725eed4 InstallationDate: Installed on 2011-10-27 (741 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. Dell System Inspiron N7110 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=e0651175-059b-4b06-b993-e1e4f43a6480 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-11-02 (4 days ago) dmi.bios.date: 07/22/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 09G8VY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/22/2011:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn09G8VY:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron N7110 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1035074] Re: Behavior of '~' in Spanish keyboard is wrong
** No longer affects: linux (Ubuntu)
** Changed in: xkeyboard-config (Ubuntu)
Status: New = Confirmed
** Changed in: xkeyboard-config (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1035074
Title:
Behavior of '~' in Spanish keyboard is wrong
Status in “xkeyboard-config” package in Ubuntu:
Confirmed
Bug description:
On Spanish keyboards, whey you hit AltGr+4, a ~ sign is immediately
printed. Instead, nothing should be printed until you hit the next key; if the
next key you hit is a vowel or any latter that can have a tilde over it, then
that character should be produced. For example, if you hit AltGr+4 and then
a, you should get an ã
In order to type a plain ~ you should have to hit AltGr+4 followed by a
space.
In other words the character ~ should work the same way as `, ´ and ¨
and ^ do.
I'm almost sure this was how it used to work until very recently, so I
thing this is a regression introduced by some recent update.
I guess the correct package is not linux but I have no idea which
package it is and how to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-29-generic 3.2.0-29.46
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2293 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Thu Aug 9 22:20:13 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-29-generic N/A
linux-backports-modules-3.2.0-29-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (84 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1035074/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1035074] Re: Behavior of '~' in Spanish keyboard is wrong
** Also affects: xkeyboard-config (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1035074
Title:
Behavior of '~' in Spanish keyboard is wrong
Status in “linux” package in Ubuntu:
Confirmed
Status in “xkeyboard-config” package in Ubuntu:
New
Bug description:
On Spanish keyboards, whey you hit AltGr+4, a ~ sign is immediately
printed. Instead, nothing should be printed until you hit the next key; if the
next key you hit is a vowel or any latter that can have a tilde over it, then
that character should be produced. For example, if you hit AltGr+4 and then
a, you should get an ã
In order to type a plain ~ you should have to hit AltGr+4 followed by a
space.
In other words the character ~ should work the same way as `, ´ and ¨
and ^ do.
I'm almost sure this was how it used to work until very recently, so I
thing this is a regression introduced by some recent update.
I guess the correct package is not linux but I have no idea which
package it is and how to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-29-generic 3.2.0-29.46
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2293 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Thu Aug 9 22:20:13 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-29-generic N/A
linux-backports-modules-3.2.0-29-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (84 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1035074/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 750585] Re: [FFe] support for making linux-libc-dev coinstallable under multiarch
** Changed in: bash-completion (Ubuntu Natty) Status: Triaged = Won't Fix ** Changed in: bash-completion (Ubuntu Oneiric) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/750585 Title: [FFe] support for making linux-libc-dev coinstallable under multiarch Status in “armel-cross-toolchain-base” package in Ubuntu: Fix Released Status in “bash-completion” package in Ubuntu: Triaged Status in “eglibc” package in Ubuntu: Fix Released Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “klibc” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “newlib” package in Ubuntu: Fix Released Status in “armel-cross-toolchain-base” source package in Natty: Fix Released Status in “bash-completion” source package in Natty: Won't Fix Status in “eglibc” source package in Natty: Fix Released Status in “gcc-defaults” source package in Natty: Fix Released Status in “klibc” source package in Natty: Fix Released Status in “linux” source package in Natty: Fix Released Status in “linux-ti-omap4” source package in Natty: Fix Released Status in “newlib” source package in Natty: Fix Released Status in “armel-cross-toolchain-base” source package in Oneiric: Invalid Status in “bash-completion” source package in Oneiric: Won't Fix Status in “eglibc” source package in Oneiric: Fix Released Status in “gcc-defaults” source package in Oneiric: Fix Released Status in “klibc” source package in Oneiric: Fix Released Status in “linux” source package in Oneiric: Fix Released Status in “linux-ti-omap4” source package in Oneiric: Fix Released Status in “newlib” source package in Oneiric: Fix Released Bug description: FFe justification: now that multiarch support for runtime libraries in the base system is available in the archive, the next step in this process is multiarch coinstallability of -dev packages. Although most of the remaining work on multiarch -dev can and will take place in ppa for natty given where we are in the release cycle, any -dev package tree has at its root linux-libc-dev which is built from the 'linux' source package - the package which is updated more frequently than any other by SRU. Rather than trying to keep up with SRUs, or artificially inflating the version of a linux-libc-dev-only package build in ppa, it would be welcome if a multiarch-ready linux-libc-dev could be included in the archive for natty. Risks: anything that looks directly in /usr/include/asm for headers will have problems with this change; anything that uses the system include path from the compiler will not. My best efforts at examining the archive for this issue (see below for details) have turned up only four packages in main and universe that are affected: three C library implementations, and bash-completion. Updating these packages in concert is manageable (patch for eglibc is ready, patches for the others are in preparation), but there's always some risk that the text search on package sources has missed something, and there wouldn't be room for another full archive rebuild before release to catch other breakage. Details: In order to have coinstallable multiarch -dev packages of any sort, linux-libc-dev first needs to be coinstallable since libc-dev depends on it. This seems to be straightforward to achieve; only the asm directory needs to be moved to the multiarch directory path, all the other header files appear to be (sensibly) architecture-neutral and can be shared between architectures. The compiler will find /usr/include/triplet/asm for the corresponding architecture with no problems; I've done a number of test builds that work just fine this way. The only trouble is with software that walks the filesystem looking for asm/foo.h includes instead of trusting the compiler to resolve them. It's unlikely that software should need to do this since the asm headers should as a rule not be directly included from userspace anyway, but the chances are not zero. I didn't expect nearly as many packages to break as did by the move to /usr/lib/triplet, either, so it seems my faith in the sanity of upstream build systems is generally misplaced. And I don't think we have time to discover any resulting issues with another archive test rebuild and fix the resulting packages before the natty release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/armel-cross-toolchain-base/+bug/750585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 800910] Re: Kernel Upgrade forces removal of grub-efi due to missing recommends entry
** Changed in: apt (Ubuntu Oneiric) Status: Confirmed = Won't Fix ** Changed in: apt (Ubuntu Natty) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/800910 Title: Kernel Upgrade forces removal of grub-efi due to missing recommends entry Status in “apt” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Fix Released Status in “apt” source package in Natty: Won't Fix Status in “linux” source package in Natty: Fix Released Status in “apt” source package in Oneiric: Won't Fix Status in “linux” source package in Oneiric: Fix Released Bug description: I'm currently experiencing an issue with installing kernel updates on natty. It seems to want to force install grub-pc -- ignoring the fact that grub-efi is installed. Looking at the dsc for the kernels at present, it seems linux-image-* recommends grub , grub-pc or lilo, but omits grub-efi which means when a kernel upgrade happens it forces removal of it for a recommended bootloader - despite the fact that grub-efi-* is perfectly valid, and is required for EFI booting. keith@Jarvis:~$ uname -a Linux Jarvis 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux keith@Jarvis:~$ apt-cache show linux-image-2.6.38-10-generic | grep Recommends Recommends: grub-pc | grub | lilo (= 19.1) -Keith To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/800910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
