I'm done with this. Took out the nVidia card today, only to run into the
same old performance problems (i.e. no smooth video playback) with the
i915 driver (which were the initial reasons to switch to nVidia). Even
without the card, I'm still running into this bug. Guess I have to
manually remove
Hello Daniel
I did not receive any instructions, or any text at all in your last
message. I am just wanting to know if there is any update on this issue
and how to solve it.
Regards, Adrian
On 22/10/18 6:22 pm, Daniel van Vugt wrote:
> ** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
>
Hello Daniel. I have performed the tasks you requested and have the
relevant text file attached.
Regards, Adrian
On 23/10/18 4:43 pm, Daniel van Vugt wrote:
> Please:
>
> 1. Reboot and run nothing other than one game that will trigger the bug.
> Do not run any other apps.
>
> 2. After the bug
Thanks. It looks like something is crashing at the end (where you see
"whoopsie") but I can't yet tell what.
Firstly, please remove/disable all gnome-shell extensions as they are
often the cause of crashes.
Secondly...
Thank you for taking the time to report this bug and helping to make
Ubuntu
Hi all,
You can add another person to the list
Ubuntu 18.04.1 + all updates + meas 18.2.3
Dell 7470 using internal Intel(R) Core(TM) i5-6300U
No Wayland.
There are many more people like us:
https://askubuntu.com/questions/1038723/slow-recovering-from-lock-screen-ubuntu-18-04
Okay, so I have run the update and reboot commands. I tried to run the
ubuntu-bug command again and I got exactly the same error message as was in
the previous screenshot.
On Tue, 23 Oct 2018 at 20:46, Daniel van Vugt
wrote:
> That screenshot shows that you can't report crash files because your
I'm currently going down the road of replacing the startech device. The only
thing that made me wonder if it was a software problem is that using the
'screen display' utility to move one screen, apply, then revert, seemed to fix
the problem, albeit temporarily.
I noticed while debugging on
Ah! I think you are now hitting bug 1727356. Please also enable the
workaround for that.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1799280
Title:
Low graphics mode with ubuntu 18.04
Just to add, this is the screenshot I took of another attempt. The upgrade
commands are there just to show what I see when I run those commands. They
were run previous to a reboot, then I ran them again to make the screenshot.
Regards, Adrian
On Tue, 23 Oct 2018 at 21:15, Adrian Barbuio
wrote:
Public bug reported:
KPrinter4 is not starting
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.18
** Package changed: xorg (Ubuntu) => kprinter4 (Ubuntu)
--
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/1799379
Title:
printing is not possible
To manage notifications about this bug go to:
Alternatively, try Ubuntu 18.10 which has the fix for bug 1727356 built-
in.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1799280
Title:
Low graphics mode with ubuntu 18.04
To manage
Public bug reported:
After upgrading to Ubuntu 18.10 I can't run eagle:
./eagle: symbol lookup error: /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0:
undefined symbol: xcb_dri3_get_supported_modifiers
https://www.autodesk.com/products/eagle/free-download
libglx-mesa0:
Installed:
Hello Daniel
I attempted all three steps and I came across the message in the
screenshot. When I click send there is no further message. I am not sure
how to find an id number. Also, I checked the gnome-shell file and there
was no file labelled 'extensions'. I assume this is because I have no
Public bug reported:
setxkbmap -layout us,ru -option grp:shift_caps_switch #nor CapsLock, neither
Shift+CapsLock does nothing
I've tried to set it via Gnome Tweak Tools and DConf editor - it doesn't work
as well.
While only one cups switch works
setxkbmap -query
rules: evdev
model:
Hi Daniel,
Many thanks for your email and advice.
When I try to boot from default kernel, I get a frozen screen (once the cursor
appears). It stays frozen and I have to disconnect the power to reboot.
That is why I booted in recovery mode as advised by Ubuntu Forums.
What would be your advice.
That screenshot shows that you can't report crash files because your
system is out of date. To fix that please do a full system update first:
1. sudo apt update
2. sudo apt full-upgrade
3. Reboot
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Many thanks for your quick reply.
Can I fix the bug but still keep my files or would I need to do new
installation.
Thanks.
Sherif
On Tuesday, 23 October 2018, 11:01:01 BST, Daniel van Vugt
wrote:
Alternatively, try Ubuntu 18.10 which has the fix for bug 1727356 built-
in.
--
You
Public bug reported:
I am attempting to do a clean install of Ubuntu 18.04 on a new server
(Supermicro X10DRH-iLN4) with an NVidia GTS 1050. It currently has
14.04 desktop installed and it installs/works without issues. I am
using a live USB stick with either desktop 18.04, 18.04.01 or server
Just tested liveusb with ubuntu 18.10 - bug can be reproduced there as
well
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xkb-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1799390
Title:
shift_caps_switch doesn't work in Ubuntu 18.04
Brilliant. Thanks Daniel. I have enabled the workaround and logged in. I will
also upgrade to 18.10 as per your advice.
Is it possible to ask for advice regarding GRUB rescue on other disk. How can I
report this bug as I can't log in.
Thanks again.
Sherif
On Tuesday, 23 October 2018,
the bug got fixed in xorg, there is no need to target an xorg fix to
cosmic
** Changed in: xorg-server (Ubuntu Cosmic)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Untargetting the xorg part from cosmic since the initramfs was enough to
workaround the problem there
** No longer affects: xorg-server (Ubuntu Cosmic)
** Changed in: xorg-server (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of
I don't have the hw to test it. For the kernel it was easy to just check
that the entries are found in module.alias for i915. I don't see how to
verify that for the xserver, the strings don't seem to be greppable from
any of the binaries.
** Tags removed: verification-done
** Tags added:
Public bug reported:
Ever since I updated from 18.04 to 18.10, I'm no longer able to play a
game like Heroes of Newerth. As soon as the game start after the picking
phase, my system completely shuts off/reboots. Testing with a game like
Warsow gives me the same result.
In about 50% of the
I have been able to get around this by using the nouveau.modeset=0 to
boot the liveusb and get Ubuntu 18.04 installed, however there is still
the compatibility issue of nouveau to a GTX1050
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
You have been subscribed to a public bug:
This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic.
With Cosmic, it is not possible to click on the window buttons after
moving the mouse cursor to the top of the screen. Unlike similar bugs,
no amount of moving left or right triggers
So obviously this is a known bug and literally every panel-like
application is affected. It also seems there is no good solution so far
apart from the aforementioned workaround of switching away from xinput2
via the environment variable.
** Bug watch added: freedesktop.org Bugzilla #92681
that said, the commit in xserver is trivial..
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1789924
Title:
Missing Intel GPU pci-id's
To manage notifications about this bug go to:
Tested with Fedora 29 liveusb - the same bug
KDE Neon 20181011 User - no such bug. Looks like it's something in Gnome
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xkb-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1799390
Title:
I have written a patch that employs the only known/reasonable workaround
so far for the issue within xorg:
https://git.xfce.org/xfce/xfce4-panel/commit/?id=e56e8699e271cea209f5b283421952d9035ad2b5
This commit could be pulled into Ubuntu at very low risk.
** Also affects: xfce4-panel (Ubuntu)
If there is still a Xorg bug here then please log it upstream here:
https://gitlab.freedesktop.org/groups/xorg/-/issues
and tell us the new bug ID.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
FYI, similar skewed stride bugs on:
radeon: bug 1799103
Huawei rack servers: bug 1780076
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1796822
Title:
Desktop live cd boots corrupted
Sorry, I see you already did that on bugs.freedesktop.org.
** Summary changed:
- Window buttons are not clickable at the top of the screen
+ XFCE window buttons are not clickable at the top of the screen
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Thanks. Unfortunately you probably can't report crash files that were
created before the system update. Only crash files from a fully-updated
system are accepted.
So please delete the existing crash files and wait for new ones to be
created.
--
You received this bug notification because you are
I think the conclusion here is that:
1. In the beginning you really had bug 1727356.
2. While trying to work around bug 1727356, you accidentally created
this problem, which is not a bug at all but user error.
So please subscribe to bug 1727356. This bug is now closed as "invalid".
If you have
Yes, it sounds likely to be a hardware problem if it occurs in Windows
too. Closing this bug now.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
I think you need to set these via the gnome config, otherwise g-s-d will
reset the settings
** Package changed: x11-xkb-utils (Ubuntu) => gnome-settings-daemon
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xkb-utils in Ubuntu.
That seems right.
It's working fine now with 18.10.
Thanks for your help. Really appreciate it.
On Wed, 24 Oct 2018 at 3:50 am, Daniel van
Vugt wrote: I think the conclusion here is
that:
1. In the beginning you really had bug 1727356.
2. While trying to work around bug 1727356, you
39 matches
Mail list logo
