It was really meant to be helpful. You should understand this kind of bug
is truly critical. I believe this has not been the case.
I am sorry, I am not able to help in any other way for now and will not
participate in any further discussions or bug reporting.
I wish you all the best.
On Mon, 18
If there is a possibility that copy-paste will result to an error, whole
distro is useless for serious production use.
It is really sad, testing this kind of bug is so uncertain and difficult.
In my opinion programmer should be able to guarantee that such error can
not take place. Otherwise there
I updated proposed mutter 3.36.2 and tried Libreoffice Calc sheet copy -
paste, cut - paste in pretty much same way with the same pc I did at the
time I reported the bug - only few times more.
I did not run into error. I don't have any need for extensive copy - paste
activity any time soon, so
Public bug reported:
I tried to report the bug as Libreoffice bug, but they seem to ignore it as of
problem in ubuntu.
I was advised to report this for ubuntu beta 20.04.
Bugzilla Bug 132213 shows what I was able to describe at the time.
I dis some 50 cut and paste actions while working with
I partly agree. Users don't bother to report the bugs as it is difficult
and as this is free software and complaining feels unjustified. However I
am simply not able to put enough effort to prove my point (will be too busy
for that now). It is incredible that basic functionality is at such a poor
Public bug reported:
Logitec K800 and logitec M535 worked perfectly with Ubuntu 16.04.
I can pair the keybord alone and everything works, but mouse M535 can
not be paird at all with default bluetooth settings so that it would
work after boot. However using blueman M535 can be successfully
3.28.2-0ubuntu1.1 did work fine for login logout to another user (critical
in our environment). It has been few days since it was supposed to be
coming and I figured that it is safe now to start installing 18.04, but
fresh install 18.04 and I am still getting 3.28.0-Oubuntu1 - will not work.
su
Fresh install 18.04 gdm3 did succeed occasionally, but mostly froze
completely so that power button was only way out.
There was a fix that was available in proposed repository (or something)
that made things a bit different. Failure became a rule, but it was
possible to get back with
I had similar experience yesterday after installing 3.28.2 and I reported
that it does not work. But after couple of boots I have been testing every
now and then maybe some 15 times and every time it has logged in - very
slowly but success anyway. To me that is quite clear that any kind of
success
Did you test : 3.28.2-0ubuntu1.1 ?
I thought that is The version having The fix
ke 30. toukokuuta 2018 klo 18.51 KenWilson <1766...@bugs.launchpad.net>
kirjoitti:
> All,
> My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect password
> issue; however, it creates a new issue. As such
, looks better now.
ti 29. toukok. 2018 klo 22.47 Heikki Moisander (moisan...@gmail.com)
kirjoitti:
> heikki@ThinkPad-X301:~$ apt-cache policy gdm3
> gdm3:
> Asennettu: 3.28.2-0ubuntu1.1
> Ehdokas: 3.28.2-0ubuntu1.1
> Versiotaulukko:
> *** 3.28.2-0ubuntu1.1 500
heikki@ThinkPad-X301:~$ apt-cache policy gdm3
gdm3:
Asennettu: 3.28.2-0ubuntu1.1
Ehdokas: 3.28.2-0ubuntu1.1
Versiotaulukko:
*** 3.28.2-0ubuntu1.1 500
500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
3.28.0-0ubuntu1
Mostly I don't understand this discussion and probably I should not take
part in it. There has been no progress visible to me. The bug I reported
was assigned as duplicate to this, so if this is now fixed, should I report
the bug again?
Anyhow it appears to me, that to ordinary users sharing the
2018-05-18 17:05 2018-05-18 14:05 UTC Crash gnome-session-bin
link:
https://errors.ubuntu.com/oops/d6ec2448-5aa9-11e8-8106-fa163ef911dc
ma 21. toukok. 2018 klo 10.11 Daniel van Vugt (daniel.van.v...@canonical.com)
kirjoitti:
> Bug 1766137 is not fixed in 18.04 yet. Only in 18.10. So it may
I did run "ubuntu-bug
/var/crash/_usr_lib_gnome-session_gnome-session-check-accelerated.120.crash"
Looked like it was sent.
This bug shows up differently copared to 1766137. This time login will not
progress to blank screen and probability is 100% now as bug 1766137 showed
up to me only maybe
Public bug reported:
While trying to change to another user account without boot display
manager freeze. ctr-alt-F2 return back to previous user. While trying to
log in to another user account after log out from another result to same
immediate freeze. ctr-alt-del boots and after this login
Really sorry about spamming, but I only now figured out how to get output
from relevenant time ( I hope)
getUniqueBusNameSync@
/usr/share/gnome-shell/extensions/
ubuntu-appindicat...@ubuntu.com/util.js:58:20
org.gnome.Shell.desktop[1812]: #3
0x730315f0
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #4
0x561a8f6df7a0
pe 18. toukok. 2018 klo 21.01 Heikki Moisander (moisan...@gmail.com)
kirjoitti:
> Not sure what came out but this is out come of running journalctl right
> after b
Not sure what came out but this is out come of running journalctl right
after booting after freeze.
I need clear guidance to get something else more relevant.
Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 20:56:33
EE
huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version
I installed proposed updates. Now it freeze a bit earlier and even more
often. Login screen remain visible and no cursor movement while before in
looked like progressing with blank screen with cursor movement until final
freeze.
pe 18. toukok. 2018 klo 19.20 KenWilson (1766...@bugs.launchpad.net)
Work around does not work for. It is not about nvidia driver. Lets face
it, it is a showstopper for ubuntu 18.04 until bug is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766137
Title:
Public bug reported:
Login works on start up, but when logged out and login in with another
user end up blank screen with only moving cursor. Will not make any
difference using xorg or wayland. It is failing some 15 times out of 20
tryout. Sometimes it boots by itself sometime ctrl+alt+del seem
If I log out and log in as a different user I get blank screen with mouse
cursos visible and movable, but nothing else. If I log in as same user it works
or if I boot I can log in with any user.
18.04 normal set up. I did install and purge gnome-session (to test "vanilla
gnome").
As a fix I
I am sorry, I fail to understand the discussion going on - have not been
reading it too carefully though. Why this still continues? I think it is
quite clear to development team that fix is needed and I am 100% certain
they know how to proceed. It is just matter of prioritization, which brings
me
We don't need java right now - so no hurry for me with the fix or
workaround. Thanks anyway to all.
2014-11-02 12:21 GMT+02:00 Paul Dooley 1363...@bugs.launchpad.net:
Remember when using the workaround in post #14 to change amd64 to
i386 if you are using a 32-bit installation...did this and
Thanks for confirmation,
I tried to install it several times afterward and got my system in problems
when trying too hard - though luckily was able to remove and fix everything
in the end.
I believe it is good idea to make the package unavailable as ordinary users
will get into troubles they can
Public bug reported:
Sorry, not able to add much comment - this report is originated
automatically
I tried to install java support when I needed it in the middle of
session in certain www site. As I was logged in to service requiring
relatively demanding authentication using keys provided
I tried to install it several times again after completely removing
everything java related using instructions in
http://askubuntu.com/questions/84483/how-to-completely-uninstall-java
then tried to install icedtea from sw-center.
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 768184 ***
https://bugs.launchpad.net/bugs/768184
This thing seems to appear when I leave the PC idle for a long time.
Power saving options do not seem to affect like they are being set, but
I really don't know very well what is the fact.
--
You received
29 matches
Mail list logo
