I also see these on 18.04 bionic server installs ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/827151
Title:
Annoying log message "DIGEST-MD5 common mech free"
OK, the touchpad issue is not related at all, there is a kernel driver
explanation of that. Now it works (the touchpad) but still, the
mentioned dbus error message occurs from time to time, not so consistent
though now.
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "core dump file"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+attachment/5214227/+files/apport_core_0k2jxx4e
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
** Attachment added: "crash file from /var/crash"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+attachment/5214228/+files/_usr_bin_dbus-daemon.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus
Public bug reported:
At almost every boot and login after a while I get a "Ubuntu 18.10 has
experienced an internal error" window. However it says, coredump size is
too small (see attached screenshot).
Also no idea if it is related but touchpad of the notebook does not work
only external mouse.
Same problem with powerdns, I can't run it with apparmor profile,
because it complains:
operation="sendmsg" info="Failed name lookup - disconnected path"
error=-13 profile="/usr/sbin/pdns_server" name="run/systemd/journal/dev-
log" pid=17236 comm="pdns_server" requested_mask="w" denied_mask="w"
With wayland, the problem is even worse, with X11 I could at least use
xrandr to set the correct resolution. This is not an option with wayland
though, so I cannot even use my desktop normally, I guess I should
downgrade ubuntu, since no way to use the machine in a sane way anymore,
and not so
Ok, I've found a workaround, to specify this kernel parameter in GRUB:
video=VGA-1:1920x1080@60
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong
With wayland, the problem is even worse, with X11 I could at least use
xrandr to set the correct resolution. This is not an option with wayland
though, so I cannot even use my desktop normally, I guess I should
downgrade ubuntu, since no way to use the machine in a sane way anymore,
and not so
Please tell me, if you need further information of some kind of co-
operation to resolve this issue. Thanks a lot, in advance.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Another interesting finding with grep'ing around in /var/log for VGA-1:
root@vega:/var/log# grep VGA-1 syslog
May 4 14:27:10 vega unity-settings-[1644]: unable to get EDID for
xrandr-VGA-1: unable to get EDID for output
And maybe the even more interesing part in /var/log/gpu-manager.log
I'm really not an xrandr / etc wizard, but what looks strange for me,
that it seems something reports "VGA-1" when all the examples on the Net
(and in xrandr man page) mentions "VGA". Even in Xorg.log:
root@vega:~# fgrep VGA /var/log/Xorg.0.log
[25.034] (II) modeset(0): Output VGA-1 has no
Public bug reported:
I've never had a problem like this before. Now, after upgraded to Ubuntu
17.04 it was already strange to see the boot logo in a kind of low and
fuzzy resolution. And it remained for the LightDM login screen, also for
the desktop after logged on. System setting -> Display
Public bug reported:
My problem seems to be rather specific. I develop an emulator for a 8
bit computer with SDL2, capable of running on Linux and Windows. I use
cross-compiling with mingw for Windows, and wine to test it. It seems
the problem occurs when I try the windows build, with full screen
Meanwhile, I've upgraded to 15.10. Now the system _mostly_ works, but
let's say about every 5th boot the system freezes with black screen if
systemd is used. Upstart always work. Interestingly in most cases
systemd works as well, but not always. I cannot find any reason about
this always changing
** Summary changed:
- Xserver does not start on boot (low-graphics mode)
+ Xserver does not start on freezes with systemd + lightdm
** Summary changed:
- Xserver does not start on freezes with systemd + lightdm
+ Xserver does not start or freezes with systemd + lightdm
--
You received this
This bug seems to be still valid, but its behaviour is somewhat
different at least for me. When I first noticed this, X did not start at
all, and it dropped to the screen to allow to choose for low graphics
mode, exit to console, etc. Now, X starts however it freezes in a way
that no keyboard can
It seems though it can be guessed more or less what can cause problems
(ie thinkpad + lightdm + systemd) the exact details are not the same,
and some other conditions can/do count as well. Also the not always
factor sometimes, kinda odd.
However, as bug 1340964 if often referenced for me, and it
For me, it's kinda odd. It seem to work (and worked even some day ago),
then trying again (boot again) and it does not work again then ...
Recently it seems to be quite unpredictable. But it can be a reason that
sometimes I attach external monitor via the VGA D-SUB connector, but
sometimes I
Ok, I was too fast ... Tried again: now, X server starts and logic
screen is shown (though with the default background not the one based on
the last user logged in) but keyboard does not usable and no mouse
cursor either. Still, choosing upstart seems to work!
--
You received this bug
Today I tried again and now it seems system boots normally, I can log
in, with lightdm+systemd. I guess some of the updates solved the
problem, but it would be useful to hear that it's not only me ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
@asala But does using upstart (or systemd, but with gdm instead of
lightdm) fixes it for you? Then it can be said, at least lightdm+systemd
issue ... However reading duplicates, and comments here, at least it
seems, Lenovo Thinkpads are highly affected for some reason, even if not
only ...
--
ThinkPad L520: exactly the same as professordes wrote: systemd + lightdm
does not work, dropping to console login freezes (interestingly it
worked some days ago when I managed to use service lightdm stop/start
to cure the problem at least so systemd could be used with some extra
work though, not
Now it turns out even more bizarre, I can no longer use my notebook with
systemd. After having that low-graphics dialog, only exit to console
helped (eg stopping/starting lightdm service by hand) but now exit to
console cause a freeze that the computer does not react to keyboard
anymore (not even
And it seems after I can login the crash report dialog brings me to bug
1340964 then. What is interesting for me: why is there a problem Xorg
does not start, when it does if I try it then.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hmm, reading the duplicates, it seems it's a Lenovo notebook + systemd +
lightdm combined problem, and does not occur too much if all of the
three conditions do not meet? For me, it's true, all of them, and I have
the problem at least ...
--
You received this bug notification because you are a
The dialog box saying low graphics mode allows me to exit to console, if
I do that, I can see on console 7 (ALT+F7):
[FAILED] Failed to start Light Display Manager.
See systemctl status lightdm.service for details.
[DEPEND] Dependency failed for Graphical Interface.
Entering the suggested
** Package changed: xorg (Ubuntu) = lightdm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1434396
Title:
Xserver does not start on boot (low-graphics mode)
Public bug reported:
After upgrading to (32bit) vivid I hadn't got any problem, but since a
day (daily upgraded) booting results in a dialog saying low graphics
mode and a dialog window about this. Choosing running in default mode
causes to boot splash to be shown forever. if I choose exit to
** Summary changed:
- Xserver does not start, on boot (low-graphics mode)
+ Xserver does not start on boot (low-graphics mode)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
By the way I am not sure if it's related: on booting backlight of the
LCD (of the notebook) is always set to minimal during the boot at one
moment, barely visible (but surely I can use the keyboard Fn +
corresponding key to increase to a readable level). It was also the
situation with the previous
Public bug reported:
I am not sure if it's bug of xserver-xorg or other package. The problem:
after reboot everything seems to be fine, scrolling within windows,
moving windows are smooth and fast. After some time however everything
becomes quite slow, eg output in gnome-terminal which made the
I don't know if it helps, but I always had problems like no input field
for password or the double unlock (if the first problem does not
occur, unlock presented another unlock field with a sightly different
screen) problem on my notebook. Then I noticed, I have a package
installed named
Another observation: in case of problem also shutdown does not work
sometimes, it simply doesn't do anything, even if try multiple times.
The only solution then: switch to text console, log in, give command
init 0 as root.
--
You received this bug notification because you are a member of Ubuntu
34 matches
Mail list logo
