[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) due to outdated gcc-4.8

2018-04-06 Thread Simon Reed
Running Xubuntu 14.04 and just upgraded to 3.13.0-144 from 3.13.0-143
and needed to re-apply the fix again.

The fix I have used is to edit  /usr/src/linux-
headers-3.13.0-144/include/linux/vermagic.h

$ cd /usr/src/linux-headers-3.13.0-144/include/linux
$ diff vermagic.h vermagic.h.WAS 
27,28c27
< /* #ifdef RETPOLINE */
< #if 1
---
> #ifdef RETPOLINE

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1750937

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) due to outdated gcc-4.8

Status in gcc-4.8 package in Ubuntu:
  Fix Released

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1750937/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1044111] Re: blkid is hanging on probing nonexistant floppy drive

2015-06-03 Thread Simon Reed
Is there no better solution than to say "Change your BIOS settings"?
There is nothing to put the idea in the user's mind that that may be the
problem, especially these days when many users have never seen a floppy
disk in their lives.

blkid will make gparted lock up for 20 minutes or more, other commands
fail much more quickly.  Because gparted calls blkid, one never sees any
output from blkid when it is causing gparted to seem to hang.  This
means people installing Linux for the first time think the installer
does not work and they are likely to go away and not come back saying
"Linux won't work on this PC".  A PC that likely has a functioning
Windows on it.

At the very least there needs to be some sort of clue to the user, for
example, programs that rely on blkid checking to see if it takes ages to
respond and then informing the user the BIOS might need changing to
match the actual drives installed, and the "System Requirements"
documents for the various distributions changed to say "make sure your
BIOS matches your installed drives because there is one time where it
will cause your PC to hang which is when you install Linux".

As it stands, this problem is an example of "Linux is too hard to use".

It actually took me over 20 hours of determined struggling to finally
work out why I could not seem to install Linux on my laptop, despite
trying many distros, and to work out it was this blkid / gparted
problem.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1044111

Title:
  blkid is hanging on probing nonexistant floppy drive

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  1. Lubuntu 12.10 i386 3.5.0-11-generic
  2. util-linux 2.20.1-5.1ubuntu1
  3. I expected sudo blkid to display partition stats. This bug is reference to 
bug #1029149 gparted never completing scanning all devices.
  4. I do not get the desired output from gparted or sudo blkid.

  The attached screenshot show the lack of results when using the sudo
  blkid command.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: util-linux 2.20.1-5.1ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
  Uname: Linux 3.5.0-11-generic i686
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: i386
  Date: Thu Aug 30 18:33:46 2012
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120826)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1044111/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1044111] Re: blkid is hanging, or at least taking a long time to process partition statistics

2015-05-01 Thread Simon Reed
I'm not sure whether to update this bug or:
- bug 155047 https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/155047
- bug 1029149 https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1029149
as I suspect they are really all duplicates as they suffer the symptoms of this 
blkid bug.

I have been struggling to install LXLE 12.04.5 because of this bug.
gparted sits on "Scanning all devices..." for over 20 minutes every time
a change is made in gparted.

The problem is made worse by the Sony PCG-FX201 laptop not having any
option in the BIOS to say there is no floppy drive.  My workaround was
to put the floppy drive back in the laptop (one can either plug in the
floppy drive, a 2nd battery, or a weight-saver).

On installing the floppy drive, gparted continues and then works
normally.  (No floppy disk is required.)

It is caused by sudo blkid pausing for ages (appearing to hang) when
there is no floppy drive but responds instantly when it is installed.

I don't think blkid should hang when a drive is absent.

util-linux  2.20.1-1ubuntu3.1
libparted  2.3
GParted  0.18.0  0.18.0-1~getdeb1
LXLE  12.04.5 LTS
3.2.0-83-generic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1044111

Title:
  blkid is hanging, or at least taking a long time to process partition
  statistics

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  1. Lubuntu 12.10 i386 3.5.0-11-generic
  2. util-linux 2.20.1-5.1ubuntu1
  3. I expected sudo blkid to display partition stats. This bug is reference to 
bug #1029149 gparted never completing scanning all devices.
  4. I do not get the desired output from gparted or sudo blkid.

  The attached screenshot show the lack of results when using the sudo
  blkid command.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: util-linux 2.20.1-5.1ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
  Uname: Linux 3.5.0-11-generic i686
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: i386
  Date: Thu Aug 30 18:33:46 2012
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120826)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1044111/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 718635] Re: Error message "Your computer does not have enough free memory" when core dump or stacktrace failed to be created is misleading

2015-03-09 Thread Simon Reed
I got this running warzone2100 (at the very end of the campaign, BTW).
I am using 4.5GB of my 7.8GB available and using 120KB of my 16GB swap
file.

Xubuntu 14.04

Linux simonX64 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux

(Incidentally, I re-loaded the last saved game, finished the campaign
again and there was no crash.)

** Attachment added: "InsufficientMemory_crash.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/718635/+attachment/4338791/+files/InsufficientMemory_crash.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/718635

Title:
  Error message "Your computer does not have enough free memory" when
  core dump or stacktrace failed to be created is misleading

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apport

  On Unity fully updated, when I login there is a X crash (attached), an apport 
dialog is displayed but complains about:
  ---
  Sorry, the program "Xorg" closed unexpectedly

  Your computer does not have enough free memory to automatically analyze the 
problem and send a report to the developers.
  ---

  You can only close and the report is canceled.

  Of course there's enough memory

  This message is displayed when the core dump or stacktrace can't be
  attached to the report. This should be changed to something closer to
  the real issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: apport 1.17.2-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
  Uname: Linux 2.6.38-3-generic i686
  ApportLog:
   ERROR: apport (pid 8213) Mon Feb 14 10:17:49 2011: called for pid 741, 
signal 6
   ERROR: apport (pid 8213) Mon Feb 14 10:17:49 2011: executable: /usr/bin/Xorg 
(command line "/usr/bin/X :0 -br -verbose -auth 
/var/run/gdm/auth-for-gdm-ics1IG/database -nolisten tcp vt7")
  Architecture: i386
  Date: Mon Feb 14 10:54:38 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US.UTF-8:en
   LANG=en_US.UTF-8
   LC_MESSAGES=en_AG.utf8
   SHELL=/bin/bash
  SourcePackage: apport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/718635/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp