Screenshot showing same behavior, xorg + None for paravirtualization:
https://i.imgur.com/6pB3Npc.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1971010
Title:
[vmwgfx]
I have the exact same bug, using Xorg. VM worked until updated to
Jammy, now shows just like in OP's video: Launcher is drawn fully, but
only the top left part of the background draws. Dragging windows in
working portion of screen with mouse doesn't work.
The paravirtualization setting has no
Public bug reported:
Since updating to network-manager 1.2.4-0ubuntu1 and libnss-resolve
231-7 on the 28th, yakkety is now ignoring manual DNS settings on wifi
connections. The resolv.conf file is points to 127.0.1.1 instead of
what is configured in the connection.
To recreate
---
On
Same thing. Reinstalling indicator-datetime and restarting the unity-
panel-service does *not* resolve the issue either. I see the following
in syslog:
Jul 19 05:29:27 sager systemd[1]: Started Time & Date Service.
Jul 19 05:29:27 sager kernel: [ 875.635184] traps: indicator-datet[22136] trap
I've seen the same symptoms on several of the updates during the vivid
development cycle. I believe I've seen the problems while others
haven't because always I go in and change the default theme, colors,
positions, etc. and have multiple monitors.
My workaround has been to delete everything in
When I try to use ubuntu-bug on the crash file (with and without sudo),
apport seems to silently crash without ever getting to the point of
uploading the bug.
You were correct in your workaround. I removed the iPhone I had in the
bluetooth configuration (as well as some other MAC-named entry I
I've tried apport on the crash file repeatedly, but I don't see anything
after continueing on the first dialog.
There's also nothing in the apport, dmesg, or syslog files (nor command
line) to indicate apport is having a problem. The apport service is
still running fine (and I've restarted it
Public bug reported:
The network-manager updates in vivid today [network-manager:amd64
(0.9.8.8-0ubuntu34, 0.9.10.0-4ubuntu2)] have completely broken the
network-manager service on my system.
--
evil@clevo:~$ sudo service network-manager restart
stop: Unknown instance:
I'm muting this bug for myself. In the two years since I reported it,
I've moved on from Blackberry phones and no longer have a device with
which to test. I'm sure one of the other 29 people who marked it as
affecting them can help with testing, if a fix for the regression is
ever created.
--
9 matches
Mail list logo
