[Bug 1944427] [NEW] Create from screenshot of region always fails: g_2dio_2derror_2dquark.Code19: Operation was cancelled
Public bug reported: Do: File > Create > Screenshot > Select a region to grab > Snap > drag box Results in error: Execution error for 'Screenshot': GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code19: Operation was cancelled ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gimp 2.10.18-1 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 11:29:08 2021 InstallationDate: Installed on 2020-01-06 (623 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gimp UpgradeStatus: Upgraded to focal on 2020-10-09 (346 days ago) ** Affects: gimp (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/1944427 Title: Create from screenshot of region always fails: g_2dio_2derror_2dquark.Code19: Operation was cancelled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1944427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617995] Re: Evince says "The document contains no pages" while viewing pdf file
Example PDF (at least, it seems to reproduce the same error message): https://sec.report/lux/doc/102081415.pdf I opened an upstream issue: https://gitlab.freedesktop.org/poppler/poppler/-/issues/1140 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617995 Title: Evince says "The document contains no pages" while viewing pdf file To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1617995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617995] Re: Evince says "The document contains no pages" while viewing pdf file
** Bug watch added: gitlab.freedesktop.org/poppler/poppler/-/issues #1140 https://gitlab.freedesktop.org/poppler/poppler/-/issues/1140 ** Also affects: evince via https://gitlab.freedesktop.org/poppler/poppler/-/issues/1140 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617995 Title: Evince says "The document contains no pages" while viewing pdf file To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1617995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911055] [NEW] [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Public bug reported: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS: 7feb4c09ea80() GS:8e46ada4() knlGS: [ 325.010602] CS: 0010 DS: ES: CR0: 80050033 [ 325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 003606e0 [ 325.010603] Call Trace: [ 325.010610] ? _nv002768kms+0x96/0xd0 [nvidia_modeset] [ 325.010616] ? _nv002328kms+0xb5/0x110 [nvidia_modeset] [ 325.010624] ? _nv000742kms+0x168/0x370 [nvidia_modeset] [ 325.010823] ? _nv036002rm+0x62/0x70 [nvidia] [ 325.010910] ? os_get_current_tick+0x2c/0x50 [nvidia] [ 325.010921] ? _nv002771kms+0x433/0x600 [nvidia_modeset] [ 325.010928] ? _nv002771kms+0x3fc/0x600 [nvidia_modeset] [ 325.010930] ? __schedule+0x2eb/0x740 [ 325.010935] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010939] ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset] [ 325.010944] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010948] ? _nv000744kms+0x2a/0x40 [nvidia_modeset] [ 325.010952] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] [ 325.010957] ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset] [ 325.010961] ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset] [ 325.011016] ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia] [ 325.011017] ? do_vfs_ioctl+0x407/0x670 [ 325.011019] ? do_user_addr_fault+0x216/0x450 [ 325.011020] ? ksys_ioctl+0x67/0x90 [ 325.011021] ? __x64_sys_ioctl+0x1a/0x20 [ 325.011023] ? do_syscall_64+0x57/0x190 [ 325.011024] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 325.011025] Modules linked in: rfcomm ccm aufs overlay cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci snd_sof_intel_hda_common nvidia_uvm(O) snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match nvidia_drm(PO) snd_soc_acpi nvidia_modeset(PO) snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine nls_iso8859_1 intel_rapl_msr mei_hdcp intel_rapl_common nvidia(PO) x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_usb_audio snd_hda_intel snd_usbmidi_lib iwlmvm snd_intel_dspcfg snd_hda_codec snd_seq_midi kvm_intel snd_seq_midi_event snd_hda_core snd_hwdep mac80211 kvm snd_rawmidi libarc4 snd_pcm rapl intel_cstate snd_seq mxm_wmi dcdbas intel_wmi_thunderbolt wmi_bmof dell_wmi_descriptor snd_seq_device 8250_dw snd_timer iwlwifi
[Bug 1911055] Re: [nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Suspend/resume was previously working in nvidia-455.38 ** Summary changed: - [nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed + [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1911055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698248] Re: avahi-daemon constantly registers/withdraws IPv6 address record
On my network, tcpdump suggests this happened in response to the router sending an IPv6 router advertisement every few minutes, and was stopped after: ip6tables -A INPUT -p icmpv6 --icmpv6-type router-advertisement -j DROP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698248 Title: avahi-daemon constantly registers/withdraws IPv6 address record To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1698248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998310] Re: .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%) after resume or when coming back from tty to X session
See https://forum.xfce.org/viewtopic.php?id=13926 and upstream issue https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/168 There is a partial fix which apparently fixes the desktop shortcuts being locked, but not the multiple calls to xmodmap: https://gitlab.xfce.org/atomsymbol/libxfce4ui/-/commit/85d8d390f9f2265613da4291992523937a7a2519 XFCE desktop shortcuts are unusable for about 30-40 seconds after switching from tty to Xorg if there exists a .Xmodmap file in $HOME. Without a .Xmodmap file, the delay is about 10 seconds. Similar behavior gets triggered when a keyboard is reconnected to an USB port. With this patch, desktop shortcuts are usable immediately (likely in less than 0.25 seconds after switching from tty to Xorg). An issue not fixed by this patch is that /usr/bin/xmodmap can be executed about 30 times after switching to Xorg. However, on the tested machine with a relatively small .Xmodmap this does not pose a performance issue which would be noticeable by the user. ** Bug watch added: gitlab.xfce.org/xfce/xfce4-settings/-/issues #168 https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/168 ** Also affects: linux via https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/168 Importance: Unknown Status: Unknown ** Project changed: linux => xfce4-settings ** Package changed: linux (Ubuntu) => xfce4-settings (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998310 Title: .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%) after resume or when coming back from tty to X session To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/998310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998310] Re: .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%) after resume or when coming back from tty to X session
I noticed this on Debian (buster). It appears to be caused by the keyboard being detected multiple times, resulting in xfsettingsd running xmodmap multiple times. To monitor, run: XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon After suspend/resume (or just unplug/plug the USB keyboard), xfsettingsd launches xmodmap multiple times: xfce4-settings(keyboard-layout): spawning "xmodmap /home/user/.Xmodmap" xfce4-settings(keyboard-layout): New keyboard detected; restoring XKB settings. Warning: Only changing the first 3 of 10 buttons. xfce4-settings(keyboard-layout): spawning "xmodmap /home/user/.Xmodmap" xfce4-settings(keyboard-layout): New keyboard detected; restoring XKB settings. Warning: Only changing the first 3 of 10 buttons. xfce4-settings(keyboard-layout): spawning "xmodmap /home/user/.Xmodmap" Warning: Only changing the first 3 of 10 buttons. xfce4-settings(keyboard-layout): New keyboard detected; restoring XKB settings. xfce4-settings(keyboard-layout): spawning "xmodmap /home/user/.Xmodmap" xfce4-settings(keyboard-layout): New keyboard detected; restoring XKB settings. xfce4-settings(keyboard-layout): spawning "xmodmap /home/user/.Xmodmap" xfce4-settings(keyboard-layout): New keyboard detected; restoring XKB settings. As a test, doing: for x in {1..10}; do bash -c 'xmodmap ~/.Xmodmap &'; done Has similar results of high CPU in xorg and xmodmap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998310 Title: .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%) after resume or when coming back from tty to X session To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/998310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908396] Re: laptop display is enabled even though lid is closed
Another symptom is that opening and then closing the laptop lid leaves two of the external monitors unusable - the desktop images on the monitors are unchanged but windows can't be interacted with. The only way I have found to fix this is to open a terminal on the one working monitor, and then run a script to cycle the two affected monitors off and on: xrandr \ --output DP-1 --off \ --output HDMI-0 --off sleep 3 xrandr \ --output DP-1 --auto --rotate left --right-of DP-1-1 \ --output HDMI-0 --auto --rotate left --right-of DP-1 After this, all the external monitors are working ok. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908396 Title: laptop display is enabled even though lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908396] Re: laptop display is enabled even though lid is closed
** Attachment added: "journal.gz" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908396/+attachment/5444197/+files/journal.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908396 Title: laptop display is enabled even though lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908396] Re: laptop display is enabled even though lid is closed
** Attachment added: "display_settings.png" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908396/+attachment/5444196/+files/display_settings.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908396 Title: laptop display is enabled even though lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908396] [NEW] laptop display is enabled even though lid is closed
Public bug reported: Hardware: Razer Blade 15 with 3 external rotated (portrait) monitors. Driver: nvidia-455 This problem occurs in Ubuntu 20.04 LTS. Ubuntu 20.10 works ok. If I boot the laptop with the lid closed, "Screen Display" settings shows the laptop display is active, and it's possible to drag a window off the screen to where the laptop display is supposed to be (but lid is closed, it's off). If I then suspend and resume, the screen sizing gets messed up - hitting F11 to fullscreen a window on the 2nd monitor results in it expanding to fill 2 monitors instead of 1. However, if I open the laptop lid, and suspend with the lid open, then F11 fullscreen correctly fills 1 monitor as it should. I suspect this sizing issue could be caused by the laptop screen being incorrectly included in the screen size calculations. Regarding Ubuntu 20.10 working, it seems 20.10 has the same Nvidia-455 driver, so I tested the 5.8.18 linux kernel with 20.04 to try and determine if it was kernel issue, but the problem still occurred. Possibly related: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1897530 ** Affects: xorg-server (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/1908396 Title: laptop display is enabled even though lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
Are there any known regressions/issues from this fix? The actual crash seems to be fixed but there still seems to be some confusion between the laptop display and external monitors, the internal display is active when the lid is closed, and suspend with lid closed messes up the desktop/monitor "fullscreen" size. I'm using a Razer Blade 15 with 3 external monitors. If I boot the laptop with the lid closed, "Screen Display" settings shows the laptop display is active, and it's possible to drag a window off the screen to where the laptop display is supposed to be (but lid is closed, it's off). If I then suspend and resume, the screen sizing gets messed up - hitting F11 to fullscreen a window on the 2nd monitor results in it expanding to fill 2 monitors instead of 1. However, if I open the laptop lid, and suspend with the lid open, then F11 fullscreen correctly fills 1 monitor as it should. Ubuntu 20.04 LTS has the problem. Ubuntu 20.10 works ok (lid closed on boot=no active laptop display, after suspend F11 still works) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897530 Title: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901695] Re: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary driver)
Sounds somewhat similar to bug #1879893 but it appears that is supposed to be fixed now. ** Description changed: Steps to reproduce: - - Boot docked laptop (i.e. lid closed, external monitors connected, USB keyboard plugged in) - - Log in, click desktop menu item "Power off / logout -> suspend" - - Laptop will suspend - - Press key on USB keyboard to resume - - Resume fails - external monitor shows black screen with cursor - - (this used to work ok in Ubuntu 18.04) + - Boot docked laptop (i.e. lid closed, external monitors connected, USB keyboard plugged in) + - Log in, click desktop menu item "Power off / logout -> suspend" + - Laptop will suspend + - Press key on USB keyboard to resume + - Resume fails - external monitor shows black screen with cursor + - (this used to work ok in Ubuntu 18.04) Journal shows that Xorg failed: + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0): DELL 2209WA (DFP-0): connected + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0): DELL 2209WA (DFP-0): Internal TMDS + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0): DELL 2209WA (DFP-0): 165.0 MHz maximum pixel clock + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0): + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0): DFP-1: disconnected + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0): DFP-1: Internal DisplayPort + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0): DFP-1: 1440.0 MHz maximum pixel clock + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0): + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0): DELL 2209WA (DFP-2): connected + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0): DELL 2209WA (DFP-2): Internal TMDS + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0): DELL 2209WA (DFP-2): 165.0 MHz maximum pixel clock + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0): + Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1050x1680 +2102+0 {ViewPortIn=1050x1680, ViewPortOut=1680x1050+0+0, Rotation=90}, DP-1: nvidia-auto-select @1050x1680 +1050+0 {ViewPortIn=1050x1680, ViewPortOut=1680x1050+0+0, Rotation=90}" + ... Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) modeset(G0): failed to set mode: No space left on device Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Fatal server error: Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) EnterVT failed for gpu screen 0 Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Please consult the The X.Org Foundation support Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: at http://wiki.x.org Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: for help. Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Server terminated with error (1). Closing log file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901695 Title: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901695] [NEW] Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary driver)
Public bug reported: Steps to reproduce: - Boot docked laptop (i.e. lid closed, external monitors connected, USB keyboard plugged in) - Log in, click desktop menu item "Power off / logout -> suspend" - Laptop will suspend - Press key on USB keyboard to resume - Resume fails - external monitor shows black screen with cursor - (this used to work ok in Ubuntu 18.04) Journal shows that Xorg failed: Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) modeset(G0): failed to set mode: No space left on device Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Fatal server error: Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) EnterVT failed for gpu screen 0 Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Please consult the The X.Org Foundation support Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: at http://wiki.x.org Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: for help. Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Server terminated with error (1). Closing log file. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-shell (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901695 Title: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901695] Re: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary driver)
** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+attachment/5427808/+files/journal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901695 Title: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768264] Re: terminator separator is transparent
This bug is present in a fresh install of Ubuntu 18.04.2. As a workaround I changed line 446 in terminator.py to: css = """ .terminator-terminal-window { background-color: white} Which seems to work. Changing .pane-separator didn't work. In fact, changing the pane separator size in settings didn't work at all - it is always fixed at 1 pixel and transparent. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768264 Title: terminator separator is transparent To manage notifications about this bug go to: https://bugs.launchpad.net/terminator/+bug/1768264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
Are you using btrfs? If so, the relevant Debian bug report is probably https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784881 ** Bug watch added: Debian Bug tracker #784881 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784881 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586748] Re: Lubuntu 16.04 does not install on Acer Aspire 1410 [drm:intel_set_cpu_fifo_underrun_reporting[i915] Error Pipe A unknown]
** Summary changed: - Lubuntu 16.04 does not install on a non-pae processor + Lubuntu 16.04 does not install on Acer Aspire 1410 [drm:intel_set_cpu_fifo_underrun_reporting[i915] Error Pipe A unknown] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586748 Title: Lubuntu 16.04 does not install on Acer Aspire 1410 [drm:intel_set_cpu_fifo_underrun_reporting[i915] Error Pipe A unknown] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098011] Re: atop unusable in Quantal: trap divide error
** Bug watch added: Debian Bug tracker #823135 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823135 ** Also affects: atop (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823135 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098011 Title: atop unusable in Quantal: trap divide error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atop/+bug/1098011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1479136] Re: [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards
Best way would be to get the patch in to the stable series so it's fixed across all distributions: https://www.kernel.org/doc/Documentation/stable_kernel_rules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1479136 Title: [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307105] Re: Kernel install fails due PAE checks
> Physical Address Extensions (PAE) 32-bit is available. If the pae flag is not present in /proc/cpuinfo then PAE is not enabled on your particular CPU, even if it is available for other CPUs in the same family. The CPU indicates PAE support (or not) in the result of the CPUID instruction, which is hardcoded in the processor microcode. > Are there any adverse effects known about the boot parameter "forcepae"? I have not seen any reports of adverse effects, but given the small number of users and non-extensive testing it is possible. > If that is so, then the PAE flag can be set / forced without problems. afaik those errata would not be a problem as Linux does not use PAT on Pentium M, and the TLB is cleared on init. But there may be other issues or internal errata that Intel hasn't published. Nobody knows why Intel disabled PAE for these processors. As the docs say: forcepae [X86-32] Forcefully enable Physical Address Extension (PAE). Many Pentium M systems disable PAE but may have a functionally usable PAE implementation. Warning: use of this parameter will taint the kernel and may cause unknown problems. The CPU is run out-of-spec so there are no guarantees. If this is not acceptable then the next easiest workaround is to compile your own kernel with PAE disabled (CONFIG_X86_PAE=n). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307105 Title: Kernel install fails due PAE checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1207263] Re: dkms "--kernelsourcedir" option not work
** Bug watch added: Debian Bug tracker #653176 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653176 ** Also affects: dkms (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653176 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207263 Title: dkms "--kernelsourcedir" option not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1207263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 966480] Re: The prompt asking for media removal is not shown at the end of the installation
On 16 February 2016 at 01:19, Brendan Perrinewrote: > This does not happen on 14.04.4 on real harware. It's a race condition so it will happen on some hardware and not others. On some hardware it will happen rarely and on other hardware more often. afaik The underlying bug (see fix comment #35) was not fixed in 14.04, but fixed by moving to systemd for Vivid (15.04) onwards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249244] Re: hp xw4400 has a error in dmesg log
** Bug watch added: Novell/SUSE Bugzilla #516797 https://bugzilla.novell.com/show_bug.cgi?id=516797 ** Also affects: linux (Suse) via https://bugzilla.novell.com/show_bug.cgi?id=516797 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249244 Title: hp xw4400 has a error in dmesg log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 376367] Re: Repeated ACPI Errors and Exceptions in Log Files
*** This bug is a duplicate of bug 1249244 *** https://bugs.launchpad.net/bugs/1249244 ** This bug has been marked a duplicate of bug 1249244 hp xw4400 has a error in dmesg log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/376367 Title: Repeated ACPI Errors and Exceptions in Log Files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/376367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1265192] Re: Install/reinstall wipes out all/other partitions
@marcatq - does running `os-prober` in a terminal show any other operating systems installed? If you run `journalctl -f` in another terminal you'll see the debug output from os-prober - it should test each partition in turn using a different script for each possible OS - /usr/lib/os-probes/mounted/20microsoft should detect an install of Windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1265192 Title: Install/reinstall wipes out all/other partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1265192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1370707] Re: Plymouth does not display the graphical boot splash
** Bug watch added: Gentoo Bugzilla #517572 https://bugs.gentoo.org/show_bug.cgi?id=517572 ** Also affects: plymouth (Gentoo Linux) via https://bugs.gentoo.org/show_bug.cgi?id=517572 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370707 Title: Plymouth does not display the graphical boot splash To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1370707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1356513] Re: plymouth 0.9.0 can not use framebuffer for terminal: none
*** This bug is a duplicate of bug 1370707 *** https://bugs.launchpad.net/bugs/1370707 ** This bug has been marked a duplicate of bug 1370707 Plymouth does not display the graphical boot splash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1356513 Title: plymouth 0.9.0 can not use framebuffer for terminal: none To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1356513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437492] Re: boot stalls on USB detection errors
** Also affects: linux (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785494 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437492 Title: boot stalls on USB detection errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501765] Re: WARNING: CPU: 3 PID: 1033 at /build/linux-X28llO/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]()
*** This bug is a duplicate of bug 1501260 *** https://bugs.launchpad.net/bugs/1501260 ** This bug has been marked a duplicate of bug 1501260 drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501765 Title: WARNING: CPU: 3 PID: 1033 at /build/linux- X28llO/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12326 check_crtc_state+0x2c5/0x440 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1518761] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll
*** This bug is a duplicate of bug 1501260 *** https://bugs.launchpad.net/bugs/1501260 ** This bug has been marked a duplicate of bug 1501260 drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0xb0210614, found 0x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518761 Title: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in dpll_hw_state.wrpll To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1518761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393205] Re: Intel q35 bug on Ubuntu 14.04 (Screen Artifacts)
** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=45092 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393205 Title: Intel q35 bug on Ubuntu 14.04 (Screen Artifacts) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1393205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 592434] Re: ssh -X user@machine hangs when using exit to terminate
** Bug watch added: Debian Bug tracker #639647 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639647 ** Also affects: dbus (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639647 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/592434 Title: ssh -X user@machine hangs when using exit to terminate To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/592434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247557] Re: Please backport mangonel 1.1-0ubuntu1 (universe) from trusty to saucy, raring, quantal, precise
** Also affects: ubuntu Importance: Undecided Status: New ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247557 Title: Please backport mangonel 1.1-0ubuntu1 (universe) from trusty to saucy, raring, quantal, precise To manage notifications about this bug go to: https://bugs.launchpad.net/precise-backports/+bug/1247557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1479136] Re: [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards
To get this fixed you'd need to do a git bisect between 3.13 and 3.16 to find the bad commit, and then report the bug upstream to bugs.freedesktop.org. ** Package changed: ubuntu => linux-meta (Ubuntu) ** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1479136 Title: [ubuntu 14.04.2] Artefacts in radeon driver on kernel 3.16 and upwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507472] Re: XHCI controller causing MacbookPro12, 1 to resume immediately after suspend
** Bug watch added: Linux Kernel Bug Tracker #101681 http://bugzilla.kernel.org/show_bug.cgi?id=101681 ** Also affects: unitylinux via http://bugzilla.kernel.org/show_bug.cgi?id=101681 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507472 Title: XHCI controller causing MacbookPro12,1 to resume immediately after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/unitylinux/+bug/1507472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1497716] Re: MacBookPro12,1 Unable to suspend
*** This bug is a duplicate of bug 1507472 *** https://bugs.launchpad.net/bugs/1507472 ** This bug has been marked a duplicate of bug 1507472 XHCI controller causing MacbookPro12,1 to resume immediately after suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1497716 Title: MacBookPro12,1 Unable to suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507472] Re: XHCI controller causing MacbookPro12, 1 to resume immediately after suspend
** Project changed: unitylinux => linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507472 Title: XHCI controller causing MacbookPro12,1 to resume immediately after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1507472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520887] Re: Workaround Ubuntu 15.10. Network manager applet cannot stably activate mobile broadband using 4G USB modem ZTE MF820D.
*** This bug is a duplicate of bug 1438003 *** https://bugs.launchpad.net/bugs/1438003 settings/nm-settings-connection.c.955 - Connection didn't have requested setting 'ppp'" - see https://bugs.launchpad.net/ubuntu/+source/network- manager-applet/+bug/1508718 ** This bug has been marked a duplicate of bug 1438003 (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520887 Title: Workaround Ubuntu 15.10. Network manager applet cannot stably activate mobile broadband using 4G USB modem ZTE MF820D. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1520887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
@mpnolan 3.16 is considered an old kernel now. Test with the latest git and, if you can still reproduce the bug, follow the instructions on http://permalink.gmane.org/gmane.comp.video.dri.devel/112025 and report the bug upstream including the dmesg with drm.debug=0xe boot parameter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1269883] Re: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port
** Bug watch added: Linux Kernel Bug Tracker #75381 http://bugzilla.kernel.org/show_bug.cgi?id=75381 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=75381 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1269883 Title: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1269883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168900] Re: 10de:0422 Xorg crashes after suspension with Mesa 9.1.1-0ubunt0.3
*** This bug is a duplicate of bug 1238902 *** https://bugs.launchpad.net/bugs/1238902 ** Bug watch added: freedesktop.org Bugzilla #74695 https://bugs.freedesktop.org/show_bug.cgi?id=74695 ** Also affects: nouveau via https://bugs.freedesktop.org/show_bug.cgi?id=74695 Importance: Unknown Status: Unknown ** This bug has been marked a duplicate of bug 1238902 10de:0422 [Asus M2N] Xorg crashed with SIGABRT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168900 Title: 10de:0422 Xorg crashes after suspension with Mesa 9.1.1-0ubunt0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1168900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314405] Re: Screen freezes due to Xorg crashed SIGABRT and nouveau error
** Bug watch added: freedesktop.org Bugzilla #88946 https://bugs.freedesktop.org/show_bug.cgi?id=88946 ** Also affects: nouveau via https://bugs.freedesktop.org/show_bug.cgi?id=88946 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314405 Title: Screen freezes due to Xorg crashed SIGABRT and nouveau error To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1314405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1421992] Re: [nouveau] NVC1 (GT 430) black screen after resuming from hibernate
*** This bug is a duplicate of bug 1314405 *** https://bugs.launchpad.net/bugs/1314405 ** This bug has been marked a duplicate of bug 1314405 Screen freezes due to Xorg crashed SIGABRT and nouveau error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1421992 Title: [nouveau] NVC1 (GT 430) black screen after resuming from hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau-lts-utopic/+bug/1421992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
Øyvind, zob, everyone, This bug has more than one cause. If you still see this in 3.16.0-33 or later and can reproduce it, then test the 4.0.0 kernel, and if it is fixed for you in 4.0.0 (and you can be bothered), you can do a bisect and figure out which patch fixed it.. but if it is not fixed in 4.0.0, then to get it fixed you will need to report it upstream to Intel: boot with drm.debug=0xe and get the complete dmesg up to the WARNING then follow the instructions at https://01.org/linuxgraphics/documentation /how-report-bugs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1060081] Re: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte
This crash appears to be caused by a bug in apt, see Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781858 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1060081 Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1060081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1060081] Re: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte
** Also affects: apt (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #781858 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781858 ** Also affects: apt (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781858 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1060081 Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1060081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097946] Re: software-center crashed with TransactionFailed in _run_transaction(): unprintable TransactionFailed object
This is not a real bug report. The issue is that when a package is not installable (e.g. dependencies conflict etc.) a crash report is automatically created. It is not a real crash, and arguably should not be treated as a crash. If you do get this crash and were brought to this bug report, and want to see what the actual problem is, then open a terminal and do `sudo apt-get install ` where is the name of the package you want to install. The output of apt-get will show you the real problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097946 Title: software-center crashed with TransactionFailed in _run_transaction(): unprintable TransactionFailed object To manage notifications about this bug go to: https://bugs.launchpad.net/software-center/+bug/1097946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
So much for that guess. Recommend you report the bug upstream and try reproducing it in a later kernel (for instructions see http://askubuntu.com/questions/119080/how-to-update-kernel-to-the- latest-mainline-version-without-any-distro-upgrade and you can get the latest drm-intel-nightly packages from http://kernel.ubuntu.com/~kernel- ppa/mainline/drm-intel-nightly/ ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342]
Is this fix also required for Valleyview? https://launchpadlibrarian.net/201861206/kern.log looks like the same stacktrace and afaik Valleyview uses the same GPU core as Ivybridge and Haswell, so it would make sense that it needs the same fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
Your system is Valleyview. Just a hunch, but in the patch try replacing: + } else if (IS_IVYBRIDGE(dev) || IS_HASWELL(dev)) { with + } else if (IS_IVYBRIDGE(dev) || IS_HASWELL(dev) || IS_VALLEYVIEW(dev)) { Will ask upstream about it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
@meira Sorry, somehow I had missed Dirk's comment. According to that, 3.16.0-33 should be fixed. In which case, you can try the latest mainstream kernel. The rest of the comment #71 might apply: If you can still reproduce it after that, then note from dri-devel list: If you can reproduce this somehow, please boot with drm.debug=0xe and attach the complete dmesg up to the WARNING. We seem to loose track of pageflips under obscure circumstances sometimes. We have more band-aids queued up, but fixing the underlying issue would be better ofc. - http://permalink.gmane.org/gmane.comp.video.dri.devel/112025 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
@meira comment #71 This bug should be fixed on Haswell with linux-3.19 or later, or Ivy Bridge with linux-3.17 or later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078445] Re: Xubuntu install fail due partition auto mount defeats Gparted
** Project changed: thunar = gparted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078445 Title: Xubuntu install fail due partition auto mount defeats Gparted To manage notifications about this bug go to: https://bugs.launchpad.net/gparted/+bug/1078445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1265192] Re: Install/reinstall wipes out all/other partitions
Barry's problem could be caused by the issues with 1 drive described in #109 - the installer has no concept of multiple drives and will always choose to install on /dev/sda by default, even if the previous Ubuntu install is on another drive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1265192 Title: Install/reinstall wipes out all/other partitions To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1265192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1060417] Re: mdadm BOOT_DEGRADED setting is ignored
*** This bug is a duplicate of bug 1302195 *** https://bugs.launchpad.net/bugs/1302195 ** This bug has been marked a duplicate of bug 1302195 System with degraded array boots regardless of BOOT_DEGRADED flag -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1060417 Title: mdadm BOOT_DEGRADED setting is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1060417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
** Bug watch added: Debian Bug tracker #780686 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780686 ** Changed in: linux (Debian) Status: New = Unknown ** Changed in: linux (Debian) Remote watch: Debian Bug tracker #759786 = Debian Bug tracker #780686 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966480]
Thanks for clarifying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966480]
main.c forks before opening the listening port (calls ply_create_daemon before start_boot_server). Is this intentional? Would you consider it a bug in plymouthd? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1108185] Re: Page up/dn keys stop working on a page
*** This bug is a duplicate of bug 1057769 *** https://bugs.launchpad.net/bugs/1057769 ** This bug has been marked a duplicate of bug 1057769 Firefox key up / down / page up / page down don't work in web page -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1108185 Title: Page up/dn keys stop working on a page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1108185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966480] Re: The prompt asking for media removal is not shown at the end of the installation
at the time the plymouth upstart jobs were written, plymouthd was ... correctly opening its socket before detaching from the foreground. The fork-before-open-socket behaviour goes back to the first tag of plymouth (0.1.0). It has always been that way. Probably the reason this problem was not noticed earlier is that the time period between execution of plymouthd and execution of plymouth was longer. Older hardware was slower, the time to start plymouth would include the time to load the executable from the CDROM or USB drive. Even on a VM it would be slower if the VM were on a harddrive. But now systems are faster, often physical PCs are booted from USB3 drives, or VMs are on SSD drives, so plymouth gets launched faster, and the race condition is more likely to be hit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966480] Re: The prompt asking for media removal is not shown at the end of the installation
Comment from plymouth upstream: Comment # 4 on bug 89503 from Ray Strode [halfline] main.c forks before opening the listening port (calls ply_create_daemon before start_boot_server). Is this intentional? Yes. Would you consider it a bug in plymouthd? No. Upstart should wait until the parent exits. We exit the parent when plymouthd is ready. It must have a way of coping with this situation, since it's not a novel or exotic way to daemonize. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966480]
Upstart doesn't wait for the call to plymouthd to exit, it just waits for it to fork. The upstart script is like: expect fork exec /sbin/plymouthd --mode=shutdown post-start exec /bin/plymouth show-splash afaics upstart starts plymouthd, and when plymouthd forks, upstart then immediately executes plymouth show-splash. At this point plymouthd isn't ready - race condition - which causes the splash screen to fail. The daemon should ensure that when it completes the (second) fork that it is fully initialized, since Upstart uses the fork count to determine service readiness http://upstart.ubuntu.com/cookbook/#daemon-behaviour This is probably more the fault of the upstart script than of plymouthd. It seems like it will be easier to just fix the script. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966480] Re: The prompt asking for media removal is not shown at the end of the installation
at the time the plymouth upstart jobs were written, plymouthd was only forking once - and correctly opening its socket before detaching from the foreground. This is not correct. main.c:main calls ply_create_daemon before start_boot_server, so the process does fork before binding the port. When the error occurs the plymouthd log states: [main.c] on_display_message:not displaying message Please remove installation media and close the tray (if any) then press ENTER: as no splash Note not displaying message... as no splash. That error message only occurs when the splash screen is not being shown. It is not related to unmounting the filesystem. And considering we're discussing a problem that occurs only on shutdown - there have been no problems with reliability of plymouth splash appearing on boot due to a corresponding race condition - I don't think this is at all a likely explanation for the behavior. Boot and shutdown are different. On boot, plymouth.conf executes plymouthd, then plymouth-splash.conf executes plymouth show-splash. On shutdown, plymouth-shutdown.conf executes both plymouthd and plymouth. Since one script executes both, the timing is tighter. I have tested the patch and it works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966480] Re: The prompt asking for media removal is not shown at the end of the installation
** Bug watch added: freedesktop.org Bugzilla #89503 https://bugs.freedesktop.org/show_bug.cgi?id=89503 ** Also affects: plymouth via https://bugs.freedesktop.org/show_bug.cgi?id=89503 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317164] Re: update-manager / aptdaemon TransactionFailed crashes are not problems with update-manager
The bug report being referred to is bug #1097946 software-center crashed with TransactionFailed in _run_transaction(): unprintable TransactionFailed object -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317164 Title: update-manager / aptdaemon TransactionFailed crashes are not problems with update-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1317164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
14.10 is a development release of Ubuntu that is only supported for another 4 or so months - imho it is unlikely to see any kernel backport efforts in that time frame. There isn't really any point in being on an old development release of Ubuntu, if you aren't going LTS then you might as well just run the latest active development release, 15.04 will have linux 3.19. Linux 3.19 from PPA should work fine, if it doesn't then file a bug here or at https://bugzilla.kernel.org/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064269] Re: When running lightDM user switching doesnt work
** Bug watch added: Debian Bug tracker #683373 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683373 ** Also affects: lightdm (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683373 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064269 Title: When running lightDM user switching doesnt work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1064269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078445] Re: Xubuntu install fail due partition auto mount defeats Gparted
In the past I tried which udisks2-inhibit to find the location of the command, but this always returned no results. Try apt-file: $ apt-file search udisks2-inhibit udisks2: /usr/lib/udisks2/udisks2-inhibit The problem is very easy to reproduce: create VM with blank hard drive and boot xubuntu-14.04.1-desktop-amd64.iso sudo gparted device create partition table partition new, create 20MB ext4 apply Result: as soon as apply is clicked, the partition is created, and XFCE file manager (Thunar) mounts the partition, even though gparted is still running sudo /usr/lib/udisks2/udisks2-inhibit /usr/sbin/gpartedbin Yes, this appears to fix the problem - as tested above, partitions are created but Thunar does not open. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078445 Title: Xubuntu install fail due partition auto mount defeats Gparted To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1078445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078445] Re: Xubuntu install fail due partition auto mount defeats Gparted
It can also be reproduced from parted with: $ sudo parted (parted) mklabel msdos (parted) mkpartfs primary ext2 0 20 ign (parted) --- XFCE automounts the new partition here -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078445 Title: Xubuntu install fail due partition auto mount defeats Gparted To manage notifications about this bug go to: https://bugs.launchpad.net/thunar-volman/+bug/1078445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393089] Re: Intel i915 driver hangs system
*** This bug is a duplicate of bug 1384342 *** https://bugs.launchpad.net/bugs/1384342 ** This bug has been marked a duplicate of bug 1384342 kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393089 Title: Intel i915 driver hangs system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1393089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
** Bug watch added: freedesktop.org Bugzilla #87759 https://bugs.freedesktop.org/show_bug.cgi?id=87759 ** Also affects: xserver-xorg-video-intel via https://bugs.freedesktop.org/show_bug.cgi?id=87759 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
** Bug watch added: bugzilla.opensuse.org/ #905934 http://bugzilla.opensuse.org/show_bug.cgi?id=905934 ** Also affects: linux (openSUSE) via http://bugzilla.opensuse.org/show_bug.cgi?id=905934 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413458] Re: Intermittent Intel GPU Lockup: intel_crtc_wait_for_pending_flips
*** This bug is a duplicate of bug 1384342 *** https://bugs.launchpad.net/bugs/1384342 ** This bug has been marked a duplicate of bug 1384342 kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413458 Title: Intermittent Intel GPU Lockup: intel_crtc_wait_for_pending_flips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1413458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401235] Re: screen hangs on unity with i915 kernel driver
*** This bug is a duplicate of bug 1384342 *** https://bugs.launchpad.net/bugs/1384342 ** This bug has been marked a duplicate of bug 1384342 kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401235 Title: screen hangs on unity with i915 kernel driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
This bug should be fixed on Haswell with linux-3.19 or later, or Ivy Bridge with linux-3.17 or later (or an earlier version of linux that has incorporated the patch above ...else if (IS_IVYBRIDGE(dev) || IS_HASWELL(dev))...) If you can still reproduce it after that, then note from dri-devel list: If you can reproduce this somehow, please boot with drm.debug=0xe and attach the complete dmesg up to the WARNING. We seem to loose track of pageflips under obscure circumstances sometimes. We have more band-aids queued up, but fixing the underlying issue would be better ofc. - http://permalink.gmane.org/gmane.comp.video.dri.devel/112025 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
** Bug watch added: Red Hat Bugzilla #1180810 https://bugzilla.redhat.com/show_bug.cgi?id=1180810 ** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1180810 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #759786 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759786 ** Also affects: linux (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759786 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1384342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422675] Re: No installable kernel was found in the defined APT sources
Is this new usage of boot options general? 1. The entry before -- means that it will be used by the live system / the installer 2. The entry after -- means that it will be carried to and used by the installed system Yes that is correct. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422675 Title: No installable kernel was found in the defined APT sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1422675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422675] Re: No installable kernel was found in the defined APT sources
The problem is not PAE, the problem is that the kernel parameters parser was changed as a result of the systemd debug params controversy. You need to repeat the 'forcepae' twice in the linux kernel parameters, before and after the -- i.e.: linux ... forcepae -- forcepae Kernel patch that changed the previous behaviour was: commit 51e158c Author: Rusty Russell ru...@rustcorp.com.au Date: Mon Apr 28 11:34:33 2014 +0930 param: hand arguments after -- straight to init The kernel parses parameters from the kernel command line up to --; if it doesn't recognize a parameter and it doesn't contain a '.', the parameter gets passed to init: parameters with '=' go into init's environment, others are passed as command line arguments to init. Everything after -- is passed as an argument to init. With forcepae -- forcepae I did a full install of the Vivid ISO link above. It worked ok. (There was a non-related bug, Ubuntu/grub puts vt.handoff=7 in grub.cfg which causes a black screen on boot - looks like bug #913731 or some related regression). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422675 Title: No installable kernel was found in the defined APT sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1422675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422675] Re: No installable kernel was found in the defined APT sources
Joseph Salisbury (jsalisbury) wrote 12.04 is the last release that will support non-PAE. This bug report is not about running non-PAE, it is about running PAE on the Pentium M. Ubuntu 14.04 supports PAE on the Pentium M - the Ubuntu Kernel Team merged the patch on 2014-03-06, shortly before 14.04 was released - https://bugs.launchpad.net/baltix/+bug/930447/comments/284 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422675 Title: No installable kernel was found in the defined APT sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1422675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1132045] Re: Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1033533 *** https://bugs.launchpad.net/bugs/1033533 ** This bug is no longer a duplicate of bug 1213637 Xorg crashed with SIGABRT ** This bug has been marked a duplicate of bug 1033533 Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1132045 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1132045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1134273] Re: Xorg crashed with SIGABRT - exaMemcpyBox() with src=0x0
*** This bug is a duplicate of bug 1033533 *** https://bugs.launchpad.net/bugs/1033533 ** This bug has been marked a duplicate of bug 1033533 Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1134273 Title: Xorg crashed with SIGABRT - exaMemcpyBox() with src=0x0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1134273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213637] Re: Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1033533 *** https://bugs.launchpad.net/bugs/1033533 ** This bug has been marked a duplicate of bug 1033533 Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213637 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1213637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210354] Re: Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1033533 *** https://bugs.launchpad.net/bugs/1033533 ** This bug is no longer a duplicate of bug 1213637 Xorg crashed with SIGABRT ** This bug has been marked a duplicate of bug 1033533 Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210354 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1210354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1164747] Re: Xorg crashed with SIGABRT on nouveau in libexa
*** This bug is a duplicate of bug 1033533 *** https://bugs.launchpad.net/bugs/1033533 ** This bug is no longer a duplicate of bug 1134273 Xorg crashed with SIGABRT - exaMemcpyBox() with src=0x0 ** This bug has been marked a duplicate of bug 1033533 Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1164747 Title: Xorg crashed with SIGABRT on nouveau in libexa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1164747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1118252] Re: GPU lockup while using Chromium
*** This bug is a duplicate of bug 1033533 *** https://bugs.launchpad.net/bugs/1033533 ** This bug is no longer a duplicate of bug 1213637 Xorg crashed with SIGABRT ** This bug has been marked a duplicate of bug 1033533 Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1118252 Title: GPU lockup while using Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1118252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130122] Re: Xorg crashed with SIGABRT - exaMemcpyBox
*** This bug is a duplicate of bug 1033533 *** https://bugs.launchpad.net/bugs/1033533 ** This bug is no longer a duplicate of bug 1213637 Xorg crashed with SIGABRT ** This bug has been marked a duplicate of bug 1033533 Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130122 Title: Xorg crashed with SIGABRT - exaMemcpyBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1130122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 755841] Re: [sandybridge] Graphics tearing when playing video
** Bug watch added: Red Hat Bugzilla #977391 https://bugzilla.redhat.com/show_bug.cgi?id=977391 ** Also affects: xserver-xorg-video-intel (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=977391 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/755841 Title: [sandybridge] Graphics tearing when playing video To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/755841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417233] Re: Trusty: Live session I think closes the keyboard meaning you can't hit enter to reboot
*** This bug is a duplicate of bug 966480 *** https://bugs.launchpad.net/bugs/966480 ** This bug has been marked a duplicate of bug 966480 The prompt asking for media removal is not shown at the end of the installation -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417233 Title: Trusty: Live session I think closes the keyboard meaning you can't hit enter to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1417233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417174] Re: Trusty: live session install keyboard default to EN_US
The keyboard layout for the live session is set by pressing F3 in the boot loader. The keyboard layout for the installed system is set in the Keyboard layout menu immediately after the location map menu - it does default to whatever country you select in the map location, and after selection the layout is changed in the live session (although the layout widget on the menubar isn't updated, which it probably should be). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417174 Title: Trusty: live session install keyboard default to EN_US To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1417174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1378627] Re: chromium-browser crashed with SIGSEGV
** Bug watch added: freedesktop.org Bugzilla #81706 https://bugs.freedesktop.org/show_bug.cgi?id=81706 ** Changed in: mesa Importance: Medium = Unknown ** Changed in: mesa Status: Invalid = Unknown ** Changed in: mesa Remote watch: freedesktop.org Bugzilla #82793 = freedesktop.org Bugzilla #81706 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378627 Title: chromium-browser crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1378627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1378627] Re: chromium-browser crashed with SIGSEGV
** Bug watch added: freedesktop.org Bugzilla #82793 https://bugs.freedesktop.org/show_bug.cgi?id=82793 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=82793 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #757435 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 ** Also affects: chromium-browser (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1123691 https://bugzilla.redhat.com/show_bug.cgi?id=1123691 ** Also affects: chromium-browser (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1123691 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378627 Title: chromium-browser crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1378627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289243] Re: Regression in trusty, i965_dri.so crashes
*** This bug is a duplicate of bug 1378627 *** https://bugs.launchpad.net/bugs/1378627 ** This bug has been marked a duplicate of bug 1378627 chromium-browser crashed with SIGSEGV -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289243 Title: Regression in trusty, i965_dri.so crashes To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1289243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966480] Re: The prompt asking for media removal is not shown at the end of the installation
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966480] Re: The prompt asking for media removal is not shown at the end of the installation
That's not a correct fix. The prompting is supposed to be done via plymouth, not via direct writes to the console. Okay, I didn't know whether plymouth is meant to still be in use at this late stage. The problem is the race condition in plymouth-shutdown.conf: /sbin/plymouthd --mode=shutdown /bin/plymouth show-splash plymouth show-splash can be executed before the plymouthd daemon is up and running. The subsequent message from casper then fails because the splash is not shown: [main.c]on_display_message:not displaying message Please remove installation media and close the tray (if any) then press ENTER: as no splash To fix this just requires making sure that plymouthd is ready before the call to show-splash. Patch attached. ** Patch added: plymouth-shutdown.patch https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/966480/+attachment/4310844/+files/plymouth-shutdown.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966480] Re: The prompt asking for media removal is not shown at the end of the installation
** Also affects: plymouth (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/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966480] Re: The prompt asking for media removal is not shown at the end of the installation
Confirmed in Ubuntu 14.04.1. There seems to be caused by a race condition or undefined behaviour. /etc/rc0.d/casper stop does plymouth --ping to test whether plymouth is running, then does plymouth message to print the message to the screen , then plymouth watch-keystroke to read the enter key press. But at this point, plymouthd --mode=shutdown is already running. This results in a hang with the following processes running: root 3527 0.0 0.0 652 ?Ss 21:28 0:00 /bin/sh -e /proc/self/fd/9 root 3625 0.0 0.0 18072 368 ?S21:28 0:00 @sbin/plymouthd --mode=shutdown root 3629 0.0 0.0 804 ?S21:28 0:00 /bin/sh /etc/init.d/rc 0 root 3863 0.1 0.0 804 ?S21:28 0:00 /bin/sh -x /etc/rc0.d/S89casper stop root 4089 0.0 0.0 388 ?S21:28 0:00 /bin/sh -x /etc/rc0.d/S89casper stop root 4096 0.0 0.0 12808 448 ?S21:28 0:00 plymouth watch-keystroke There could be a race condition between the plymouth --ping test and the action, or between plymouthd being shutdown and the casper script running plymouth, or it could be that the plymouth commands just don't work when plymouthd is in shutdown mode. Either way, this can be fixed by removing the use of plymouth from casper and reverting to the alternative actions which read and write /dev/console. Patch attached. ** Patch added: casper_rm_plymouth.patch https://bugs.launchpad.net/ubuntu/+source/casper/+bug/966480/+attachment/4310060/+files/casper_rm_plymouth.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966480] Re: The prompt asking for media removal is not shown at the end of the installation
It looks like the casper plymouth code that introduced this problem was intended to fix bug #506418 (live cd does not shutdown). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966480 Title: The prompt asking for media removal is not shown at the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/966480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506418] Re: [lucid] live cd does not shutdown
It appears that the fix for this bug introduced long-standing bug #966480 (The prompt asking for media removal is not shown at the end of the installation). if [ -x /bin/plymouth ] plymouth --ping; then plymouth message --text=$MSG plymouth watch-keystroke /dev/null -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/506418 Title: [lucid] live cd does not shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/506418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs