The bug shows up now even in xfce4. It did not earlier with 17.04. Now all
the managers show up the bug.
Will do the other tests later. It is now 1.30 am and I have to get some
sleep.
Thanks
Peter
On Fri, Aug 17, 2018 at 1:00 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> That l
That log appears to be from XFCE which you said does not exhibit the
bug.
Please do the 3-monitors test with gnome-shell, and run 'journalctl -f'
there.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpa
When I use ubuntu on wayland, the third screen is displayed, but the second
screen is not and there is no keyboard or mouse input. Have to reboot with
the screen unplugged.
Peter
On Fri, Aug 17, 2018 at 12:29 AM Peter Wallbridge
wrote:
> Nothing normally
> The following with the third monitor
Nothing normally
The following with the third monitor plugged in:
peterw@simulator:~$ journalctl -f
-- Logs begin at Tue 2018-05-29 18:26:24 EDT. --
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769
772 800 +hs
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launc
Going back to your JournalErrors.txt:
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0):
Page flip failed: Invalid argument
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) RADEON(0):
present flip failed
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-sessio
Separately, please also try clicking the cog wheel button on the login
screen and selecting:
Ubuntu on Wayland
Does that fix it?
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which i
GPUs:
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
Gen Core Processor Integrated Graphics Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
Processor Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
0
** Changed in: xkeyboard-config (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1738630
Title:
[improvement] xkb configuration cannot be
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xkeyboard-config (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net
*** This bug is a duplicate of bug 1738630 ***
https://bugs.launchpad.net/bugs/1738630
** This bug has been marked a duplicate of bug 1738630
[improvement] xkb configuration cannot be extended without rebuilding
xkb-data package
--
You received this bug notification because you are a mem
I suggest that you download the Xubuntu 18.10 daily ISO, then boot into
live mode and check if the issue with the open source driver is present
too.
Another thing to test is to see if disabling the builtin compositor
(Settings > Windows Manager Tweaks > Compositor) eliminates the glitch.
--
You
Public bug reported:
Locally modified keyboard layouts are overwritten on package upgrades
(in my case from 16.04 to 18.04) without asking if the user wants to
keep the local version or install the maintainers version.
This leads to problems and extra work for the system administrator.
The corre
On Thu, Aug 16, 2018 at 11:27 AM Peter Wallbridge
wrote:
> Here are three photos that might help.
>
>
> I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
> keyboard will not be active
>
>
> 1 - img_2008.jpg Showing all three terminals plugged in
>
>
> 2. img 2010 showing dis
Here are three photos that might help.
I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
keyboard will not be active
1 - img_2008.jpg Showing all three terminals plugged in
2. img 2010 showing display screen (All displays appear to be available.
3. img-2011.jpg
As so
On Thu, Aug 16, 2018 at 11:27 AM Peter Wallbridge
wrote:
> Here are three photos that might help.
>
>
> I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
> keyboard will not be active
>
>
> 1 - img_2008.jpg Showing all three terminals plugged in
>
>
> 2. img 2010 showing dis
** This bug is no longer a duplicate of bug 1731294
Keyboard shortcuts stop working; restarting unity-settings-daemon fixes them
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1746752
Title:
And again with today's updates. 8 months and still no fix. What a mess.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1737750
Title:
nvidia-graphics-drivers-304 304.137-0
1... Output of xrandr and lspci
xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-2 connected 1920x1080+1920+0 (normal left inverted right x axis y
axis) 477mm x 268mm
1920x1080 60.00*+
Public bug reported:
After updating to 18.04 from 16.04, every time I try to type a character
that's not a letter or a number in the nautilus location bar, like "/"
or "~", it hangs.
Something related to this happens with the calculator. The attachment is
after opening it over the window where I'
** Summary changed:
- gnome-shell crash, UI unresponsive
+ gnome-shell UI unresponsive
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Tags added: no-click
** Tags removed: no-click
** Tags added: noclick
--
You received this bug notification because you are a member of Ubuntu-X,
Public bug reported:
Whilst working normally, I was unable to interact with gnome-shell. The
clock at the top of the screen continued to increment, and I could ssh
in to the machine, but clicking anywhere on the screen resulted in
nothing. Changing to another VTY and back again had no effect.
I
just to give some feedback, I have a optimus laptop with i7 sandibridge
and nvidia GT550M, there is a led that indicates the nvidia GPU is
always in use also after using the ppa to test, the laptop is indeed
very hot also after I select intel and reboot and the led indicates that
the nvidia GPU is
** Summary changed:
- /usr/lib/xorg/Xorg:6:OsAbort:AbortServer:FatalError:xf86VTEnter:xf86VTSwitch
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from xf86VTEnter() from xf86VTSwitch()
--
You received this bug notification because you are a member of Ubuntu-X,
whi
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
xorg-server. This problem was most recently seen with package version
2:1.19.6-1ubuntu4, the problem page at
https://errors.ubuntu.com/problem/13b30a5bb7956db93e4bd3202c35880bae849e51
contains m
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from xf86VTEnter()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from xf86VTEnter() from WakeupHandler()
--
You received this bug notification because you are a mem
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
-
/usr/lib/xorg/Xorg:7:xf86XVEnterVT:xf86VTEnter:systemd_logind_vtenter:message_filter:dbus_connection_dispatch
+ Xorg() crashed with SIGBUS in xf86VTEnter() from systemd_logind_vtenter()
from
Looks similar to bug 1421808, but now slightly different.
** Summary changed:
- Xorg crashed with SIGABRT
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from xf86VTEnter() from systemd_logind_vtenter()
** Information type changed from Private to Public
--
You re
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
nvidia-graphics-drivers. This problem was most recently seen with package
version 2:1.19.6-1ubuntu4, the problem page at
https://errors.ubuntu.com/problem/5cfe0f5b5609a8be09f98bec1249098ac5394022
29 matches
Mail list logo
