[Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
Thankyou (my bug report a duplicate of this one). Although my third monitor is defective at the moment I will be using three 4K horizontal (Intel HD620) to run Libreoffice Calc across all three. Thankyou again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828665] Re: [regression] Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor) since ~7th/8th May
For the confirmation, I'd need guidance. Which source/mutter link to click to reinstall the prior version (or is it all of them?). Since writing the above report, by reflex more Ubuntu updates have been accepted (there have been very many this week - perhaps four or five) - new dpkg.log attached. After each new update the resolutions and frequencies sent to both monitors were correct; without problem. This morning, monitor 2 (the new one) followed the boot sequence in a mode I've never seen before - all pink and at ordinary HD 1920 (it seems). Then it went blank for half a second. Then it put up the usual message that it was changing to 4K at 30 Hz, then the desktop came up fine. [Coincidentally, an email arrived that bug 1714178 (and my bug duplicate 1795439) have been fixed (released) to overcome the modesetting driver 8192x8192 limitation. I may try again using three 4K horizontal monitors - when the third is repaired. Are the patchset and merge to drm-tip before or after this particular incident?]. I feel to add (by experience) that the former damaged monitor 2 was perhaps more vulnerable than most to sudden fast mode changes. With a previous PC (ubuntu 16.04) with Intel HD600, that monitor had to receive a valid mode at a very specific moment (which meant the user had to learn to push on the power buttons precisely one second apart) else the monitor would revert immediately to high Hz modes at inferior resolutions or shut down. With this configuration Intel HD620 and Ubuntu Bionic Beaver, both monitors can be on, will move to sleep mode and wait - great! The user can switch on the PC when they're ready. Just to say that, perhaps monitor 2 was vulnerable to even a blip at 60Hz. On the other hand, that doesn't explain how monitor 1 found itself attempting 4096 which is also part of this bug report. Can I still help in confirmation work by going back to the prior version? ** Attachment added: "dpkg.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828665/+attachment/5266146/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828665 Title: [regression] Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor) since ~7th/8th May To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828665] [NEW] Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor)
Public bug reported: Now at Ubuntu 18.04.2 LTS, Gnome 3.28.2 Deduction. The user device settings menu for desktop control dual monitors offer the correct modes available. The Bionic Beaver update does something different. Dual monitor configuration (Formerly Primary on Display Port 3840x2160 30Hz, Secondary on HDMI 3840x2160 30Hz on a three video output Intel HD620) for Cancer Research using LibreOffice Calc across both. Upgrades permitted manually rather than auto and usually done within a day. Since five months both monitors were operating HDMI (Display port not connected, not used) with Primary on HDMI2 and Secondary on HDMI1, both at 3840x2160 30Hz. Neither monitor is capable of 60Hz at UHD which is quite alright for office work. When installing such devices, strictly only the 3840x2160 30Hz mode is available on the settings page. After the most recent update (7/8th may), the primary screen was blank on reboot (abnormal) and the secondary screen showed the extended desktop without menus (as usual). Rebooting to see the primary was unsuccessful and then the secondary monitor failed completely (confirmed the next day as graphics card hardware, broken). Cold disconnect of the secondary (awaiting repair), another boot brought up Primary display only yet flickering occasionally. Primary Display. Considering the possibility of error in the graphics since the update - the Device settings (normal user page) revealed that the update had changed the output to HDMI 4096 lines (which the PC monitor can't do and the user can't select - outside specification). I was in such a hurry to save it also from damage that I put back the resolution to 3840x2160 30Hz immediately, without looking at which frequency had been set with the 4096 value. Now on rebooting, the display settings menu shows appropriately only 3840x2160 30 Hz as choice. It seems the Bionic Beaver update needed something else and set 4096 (which the user can't and notwithstanding the original user configuration). Secondary Display. I don't know what it set, but it blew the monitor card. The linux sent either 3840 at 60 Hz or 4096 at any frequency without negociation, without being able to respect the user settings. It's also possible that it used a very low resolution for a few seconds which the secondary monitor can't do either; it's (well, it was) a real PC monitor with choices of DP or HDMI yet can jump into various modes (such as 60/75Hz for gamers). After some Ubuntu upgrades in the past (blank secondary screen), it was necessary to go back into the monitor menu to switch off again the gamer mode. Something similar happened in 2017 with Light Ubuntu Update. The Secondary (very expensive) display making very alarming noises and staying blank for half a day. Now it's truly broken (I know it's the driver circuit and which parts). Waiting for repair or replacement, the system is in use now with the same Primary PC monitor and a UHD television as secondary to get by. I worked 20 years on PC systems and monitors (for ship control) and accept that in the past we nearly always used a simple basic portable VGA monitor for system upgrades, then reconnected the user's gear later. I think I'll only do (and postpone) Linux upgrades from now using a spare single desktop monitor at 1920x1080. That was a very worrying experience. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 11 11:21:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 620 [1297:4052] InstallationDate: Installed on 2018-09-13 (239 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 046d:c30a Logitech, Inc. iTouch Composite Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. DS77U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=9cdb8aeb-51e4-4cb5-95e7-b58572bf4dd7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.08 dmi.board.asset.tag: Default string dmi.board.name: FS77U dmi.board.vendor: Shuttle Inc.
[Bug 1795439] [NEW] Triple 4K displays Intel HD620 max output of 8192x8192
Public bug reported: Brand new Shuttle PC direct from factory, Kaby Lake with Intel HD620 (which uses part of the 16GB RAM) with Bionic-Beaver-latest install last month (september 2018) for Cancer Research. The application is Libre Office 6.0.6.2 with very many linked graphics per sheet (nearly all columns used for some analyses). The Display Port plus HDMI1 plus HDMI2 outputs are all simultaneous 4K (unlike the Intel HD600) which is ideal for this type of research work (all three monitors are very large 42"+). One application across all three monitors to compare any detail. Else than a presentation luxury, it's where the whole work was headed since four years - like engineering, the size of the surface of a table. The Xorg interpretation that shows up in xrandr is default limit at 8192x8192 but the user doesn't know it. Bionic Beaver "settings" allows attempts to move and modify, illustrates the effort, finds then loses the third screen, crashes if the user persists and doesn't mention the limit. It works (and very well) only if two displays are left-right and one is placed underneath or over the top. It is possible to find that out by trial (and lots of error). According to askubuntu, the Intel gen 6 and up (or thereabouts) all support 16384x16384. One user confirms Ubuntu 18.04 offers that full boundary if the driver is Nvidia but not if it's Intel i915. The user also stated that this was "a known problem with ubuntu17 and gnome and fixed" but I can't find any reference about that, nor how to do it. A suggested source code "Intel side" patch was commented on this askubuntu page last week https://askubuntu.com/questions/1045664/kubuntu-18-7th-gen-intel-graphics-incorrect-max-resolution Intel sites suggest contacting Ubuntu and the Vendor first. So I post the bug here. [By the way, the other PC was on 18.04 Lubuntu with Libreoffice 6.10 and crashed or froze about ten times per day (Open GL or without). This new PC and the previous are now both with Bionic Beaver and Gnome and not once has either hesitated, not one single stoppage of any type. Absolutely amazing. Wonderful. The stability is crucial and I hope developers and Canonical receive praise - an important decision in favour of users. My suffering is ended. Thankyou]. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Mon Oct 1 16:50:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 620 [1297:4052] InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 046d:c30a Logitech, Inc. iTouch Composite Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. DS77U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=9cdb8aeb-51e4-4cb5-95e7-b58572bf4dd7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.08 dmi.board.asset.tag: Default string dmi.board.name: FS77U dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.08:bd03/12/2018:svnShuttleInc.:pnDS77U:pvrV1.0:rvnShuttleInc.:rnFS77U:rvr1.0:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: D dmi.product.name: DS77U dmi.product.version: V1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu
[Bug 1700812] Re: pam_cap is provided by the libpam-cap package on x86_64 xenial
"So if this is a bug, it is a bug against manpages.ubuntu.com." Yes, I misspoke. To clarify I'm used to seeing the "provided by" link on manpages.ubuntu.com to link to the package I need to install to get the thing the man page references. That may just be a false association though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700812 Title: pam_cap is provided by the libpam-cap package on x86_64 xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1700812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700814] [NEW] Default capability of cap_setfcap+i should be set on setcap
Public bug reported: If I grant a user (via pam_cap) cap_setfcap+i, I would then expect them to be able to use setcap without sudo. setcap is not provided with any default file capabilities however, so either the user has to sudo, or I have to grant the setfcap capability to setcap with setcap. In my mind, it would be reasonable to grant setfcap+i to setcap by default on installation. ** Affects: libcap2 (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/1700814 Title: Default capability of cap_setfcap+i should be set on setcap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1700814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700812] [NEW] pam_cap is provided by the libpam-cap package on x86_64 xenial
Public bug reported: The man page for pam_cap (http://manpages.ubuntu.com/manpages/xenial/man8/pam_cap.8.html) claims that it is provided by the libcap2-bin package. This is incorrect, it is actually provided by the libpam-cap package (which is recommended by libcap2-bin.) ** Affects: libcap2 (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/1700812 Title: pam_cap is provided by the libpam-cap package on x86_64 xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1700812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587572] Re: Installer doesn't provide UTC option for timezone
*** This bug is a duplicate of bug 1582865 *** https://bugs.launchpad.net/bugs/1582865 ** This bug has been marked a duplicate of bug 1582865 Can't pick UTC as timezone in installer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587572 Title: Installer doesn't provide UTC option for timezone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1587572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301015] Re: Networking does not restart
Regardless of whether it's officially supported or not, the method did solve a lot of problems in one command. The only times it has caused issues for me is when I have tun devices created by other services. In general, I feel a better solution would be to have the networking only restart those adapters which it controls (seen in /etc/interfaces). Can you point us to the discussion you had on a mailing list, or bug, or otherwise where it was discussed that this change needed to be made? Otherwise it seems like it was made by fiat and it's now 13 to 1 against. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301015 Title: Networking does not restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313847] [NEW] xrandr: Configure crtc0 failed on awake from sleep
Public bug reported: Every time I put my laptop to sleep and wake it up again I am presented with the graphical login prompt as expected. The prompt works, I have a mouse, keyboard works, etc. Once I successfully login the display turns black and remains that way no matter how long I wait. The computer is responsive and I can switch to a tty. Switching to a tty and then back to the graphical desktop does not produce anything (screen remains black.) From the TTY I've tried to configure X manually using xrandr and the --display argument: `xrandr --output LVDS1 --mode 1366x768 --pos 0x0 --rotate normal --display :0` This gives me the error xrandr: Configure crtc0 failed. Note that 1366x768 is the native display mode of my monitor. If it matters I'm using the i915 driver (I have an intel graphics controller, revision 9). If I run this command after a successful boot, it works (I can change to a different display mode and then back again no problem). Logs don't seem to have anything interesting in them; but I may not be looking in the right logs at the right time. Guidance needed :) If I reboot the computer from the tty; I get the xfce graphical shutdown screen. I'm currently running xubuntu 14.04. This laptop used to run xubuntu 12.10 without issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 28 09:57:21 2014 InstallationDate: Installed on 2014-04-20 (8 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313847 Title: xrandr: Configure crtc0 failed on awake from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1313847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232877] Re: Touchpad reported as: elantech: unknown hardware version, aborting
Here is a I made patch that fixes this. I have submitted it upstream. A BIOS update is unnessesary. I have tested it and it works, I would appreciate other people trying it though. ** Attachment added: patch for drivers/input/mouse/elantech.c to allow detection of newer elantech touchpads. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232877/+attachment/3922239/+files/patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232877 Title: Touchpad reported as: elantech: unknown hardware version, aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 985121] Re: Ginn doesn't subscribe to gestures
Bug confirmed in Saucy, on Acer Aspire S7-392. Is there work being done on this bug? It's now 3 releases old, and there has been no indication of progress for fixing it. As noted by others above, the problem seems to be an interaction with Unity. It is probably a bad thing if Unity, a Canonical project, is interfering with Ginn, another Canonical project. If ther person the bug is assigned to is overworked, I would like to offer my assistence in any way possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/985121 Title: Ginn doesn't subscribe to gestures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-nexus7/+bug/985121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007714] [NEW] package grub-common 1.99-21ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
Public bug reported: happened during update ProblemType: Package DistroRelease: Ubuntu 12.04 Package: grub-common 1.99-21ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Sat Jun 2 16:48:50 2012 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic-pae root=UUID=8774aeec-6c88-4f84-9219-9ea9f1797f9e ro quiet splash SourcePackage: grub2 Title: package grub-common 1.99-21ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.d.grub.common: 2012-04-18T05:53:43 ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007714 Title: package grub-common 1.99-21ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007714] Re: package grub-common 1.99-21ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007714 Title: package grub-common 1.99-21ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
