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
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 subscrib
** 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
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-modese
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
--
Yo
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 Ubunt
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/-/c
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),
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
** 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
Tit
** 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.n
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
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 "ful
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 ->
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
** 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:
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 p
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
** 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 subscri
** 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
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
> 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 i
** 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
On 16 February 2016 at 01:19, Brendan Perrine wrote:
> 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)
*** 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.
ht
** 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 mem
@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/
** 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 membe
*** 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 subscri
** 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
*** 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 noti
*** 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 noti
** 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
** 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:
Inte
** 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 (
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 notificati
** 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 notificat
*** 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
** 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 mem
*** 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 dup
@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 receiv
** 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 U
** 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 membe
*** 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 i
*** 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: Un
Ø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
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 wit
** 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
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 w
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 fr
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
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 mem
** 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 b
@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
@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 so
*** 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, wh
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
** 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 no
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.ne
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 th
*** 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, w
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
> 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
> 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.
Whe
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
immedia
** 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 memb
The bug report being referred to is bug #1097946 software-center
crashed with TransactionFailed in _run_transaction():
--
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 /
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
** 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 y
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
> 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 b
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 li
** 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://bu
** 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 becaus
** 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 a
*** 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
*** 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
*** 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
> 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 bec
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
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.
*** 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
*** 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
*** 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
*** 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 o
*** 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 o
*** 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: exaMemcpyBo
*** 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
** 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 beca
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
*** 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 Ubu
** 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.o
*** 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.
** 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.deb
** 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
> 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 --mod
** 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
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
-
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 pro
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
1 - 100 of 925 matches
Mail list logo
