For those too impatient to wait for the updates to trickle down to the main
repository (like myself), I've created an unofficial mysql-client package
dynamically linked against libreadline6:
http://wjd.nu/files/2009/12/mysql-client-5.1_5.1.37-1ubuntu5wjd2_amd64.deb
(See more info here
I can confirm this with similar backtraces
I got the crash on `xmms2 addpls`.
The patch provided at the following url fixes it:
http://bugs.xmms2.xmms.se/view.php?id=1839
/w
--
xmms2d crashes
https://bugs.launchpad.net/bugs/212566
You received this bug notification because you are a member of
Indeed.. the patch I told that fixed it, hardly did. It made it usable
at most. With your version, I haven't got it to crash yet. Thanks.
--
xmms2d crashes
https://bugs.launchpad.net/bugs/212566
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I assume that in this fix, the following comment got added as well?
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
I'd like to disagree
I've had this issue for a while too. Indeed, pressing shift-numlock
enables/disables the feature. I don't intentionally press that, and the
only time I hit numlock is when the pad is not in number-mode.
I do however use NXclient continuously -- not VNC, but a different kind
of terminal server
Ubuntu does not fully support languages other than English.
If you experience problems with other languages, use English instead.
Okay.. so I'll have to switch to Windows whenever I want to write an
e-mail to my mom? What?
I respect the fact that a fix won't get into Hardy, but that last
For those too impatient to wait for the updates to trickle down to the main
repository (like myself), I've created an unofficial mysql-client package
dynamically linked against libreadline6:
http://wjd.nu/files/2009/12/mysql-client-5.1_5.1.37-1ubuntu5wjd2_amd64.deb
(See more info here
This, however, should be default behavior.
I concur. Same issue in Karmic over here. The fix works.
I upgraded from fresh Jaunty install, where I believe it used to work
out of the box or I think would've searched for this bug earlier.
--
Shift-alt-tab does not change to previous application
Over here, with jaunty on the desktop and jaunty on the NX server, this
issue hasn't occurred anymore. Unsubscribing.
--
mouse keys turns on randomly
https://bugs.launchpad.net/bugs/192508
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Walter Huf, in the mean time, you can add this to /var/lib/python-
support/python2.6/MySQLdb/__init__.py (put it somewhere at the top):
import warnings
warnings.filterwarnings(ignore, message=the sets module is deprecated)
Or you could add it to the project that's mailing you every day.
--
Public bug reported:
Binary package hint: qprof
On my Ubuntu/Hardy-AMD64 on a Pentium D, qprof reports invalid values
that do not map to a real location.
Example:
wal...@ananas:0:~/src/qprof-0.5.2$ /usr/bin/qprof ./tests/dumb_test
qprof: /home/walter/src/qprof-0.5.2/tests/dumb_test: 16
** Attachment added: a one line fix that works on my system
http://launchpadlibrarian.net/26047126/qprof_bug_fix.patch
--
qprof sends wrong values to addr2line on amd64
https://bugs.launchpad.net/bugs/368292
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: cat /proc/cpuinfo
http://launchpadlibrarian.net/26047130/qprof_bug_cpuinfo.txt
--
qprof sends wrong values to addr2line on amd64
https://bugs.launchpad.net/bugs/368292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: gcc -dM -E - /dev/null
http://launchpadlibrarian.net/26047137/qprof_bug_gcc_dM_E.txt
--
qprof sends wrong values to addr2line on amd64
https://bugs.launchpad.net/bugs/368292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
== Relevant config =
/etc/fail2ban/jail.conf
# backend specifies the backend used to get files modification. Available
# options are gamin, polling and auto.
# yoh: For some reason Debian shipped python-gamin didn't work as expected
#
** Project changed: uwsgi = uwsgi (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954476
Title:
uwsgi won't start when no plugins dir is found
To manage notifications about this bug go to:
The 40 makes sense now as well:
wal...@ananas:0:~/srcelf/ucontext$ gcc qprof_bug_ucontext.c -g
wal...@ananas:0:~/srcelf/ucontext$ ./a.out | addr2line
gregs is at extra + 40
/home/walter/srcelf/ucontext/main.c:18
** Attachment added: code that clarifies why si is wrong
Public bug reported:
The Ubuntu's new Enhanced Menu project[1] aims to add the option of
choosing whether you want the Global menu or not.
Due to a faulty upgrade, my Ubuntu 13.04 desktop turned out to be
missing the indicator-appmenu (and dependencies). And without those,
there was no global
Did you see the workaround on my site? Using dconf-editor to switch the
mode?
(And hit the this bug affects me to increase its visibility.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1230172
*** This bug is a duplicate of bug 1031718 ***
https://bugs.launchpad.net/bugs/1031718
** This bug is no longer a duplicate of bug 1020872
seteuid apps report perror() on trying /proc/self/auxv
** This bug has been marked a duplicate of bug 1031718
Obscure error messages caused by
Confirming: I switched to xim input method yesterday (for custom compose
combinations), and today I noticed that indeed the compose key does not
work in Chromium.
http://code.google.com/p/chromium/issues/detail?id=351230
Browser: Version 34.0.1847.116 Ubuntu 14.04 aura (260972)
@Josep: that bug report is unrelated. (Although it touches the same
cron_default_mail_charset code.)
This issue is that:
(A) The cron daemon starts with no LANG (LANG=C)
(B) The processes start with the lang environment from /etc/default/locale
(LANG=en_US.UTF-8)
Now the processes will print
** This bug is no longer a duplicate of bug 140896
Cron does send mails with wrong charset
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169160
Title:
cron: non-canonical MIME charset used in
Public bug reported:
Seeing that #140896 is closed and fixed, I'm rereporting this bug here for
Trusty (and earlier).
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/140896
This issue is that:
(A) The cron daemon starts with no LANG (LANG=C)
(B) The processes start with the lang
Ok. So this bug was really old and closed. Rereported as #1321227.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/140896
Title:
Cron does send mails with wrong charset
To manage notifications
The attached patch lp1321227-cron_does_not_read_default_locale.patch is
a workaround that loads /etc/default/locale like it should.
With upstart, this was the best I could do. And it's not great.
- expect doesn't take more than 2 forks
- there is no way to load /etc/default/locale without
Public bug reported:
See this bug:
http://www.sudo.ws/bugs/show_bug.cgi?id=649
Started on Ubuntu/Trusty since it has a sudo after 1.8.7, (precise has
1.8.3).
Steps to reproduce:
- take a local machine with a recent sudo (after 1.8.7)
- sudo vi
- ^Z (control-Z)
- fg
- repeat ^Z and fg until the
** Patch added:
SUDO-649_Patch-to-ignore-program-generated-SIGTSTP--si_pid.patch
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1322843/+attachment/4186391/+files/SUDO-649_Patch-to-ignore-program-generated-SIGTSTP--si_pid.patch
--
You received this bug notification because you are a
That last patch is the sudo author's fix for the issue. Bug is still
open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322843
Title:
foregrounding a sudo'd vim will sometimes break terminal
Nice tip MarcS. That is indeed better than the other workarounds.
Here, a quick script -- cleanup-upstart.sh -- that checks initctl list
for stalled processes and kills them:
#!/bin/sh
# vim: set ts=8 sw=4 sts=4 et ai tw=71:
upstart_spawn_and_stop() {
name=$1
pid=$2
pkill -xf
And I'm happy to say that things are moving to systemd. My cron.conf now
looks #44 just so cron gets the right locale in 14.04. I'm baffled that
that's the best I can come up with with upstart. If there is a better
way, please enlighten me.
--
You received this bug notification because you are a
Funny, but that gives me completely different broken behaviour.
im-config writes to ~/.xinputrc:
# im-config(8) generated on Thu, 07 Aug 2014 08:26:49 +0200
run_im xim
# im-config signiture: 89512b7941127eeda7d3e3ac5703f05e -
And then I indeed get the same environment variables as you.
** Summary changed:
- Chromium 34 ignores ComposeKey
+ Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309145
Title:
Chromium 34 and
I can refute it. Over here is it *not* fixed with:
Version 36.0.1985.125 Ubuntu 14.04 (283153)
I did a full restart, to be on the safe side.
My config:
$ tail -n1 .profile
export GTK_IM_MODULE=xim # Compose key stuffs
$ cat .XCompose
include %L # import the default Compose file
So. Apparently this has been fixed somewhere along the road to Ubuntu
14.04.
The patch is commented out in the debian/patches/series file in version
1.3.0-0ubuntu2.
However, the debian/changelog doesn't tell me when that happened (or when it
was added, for that matter).
--
You received this
Nope. Not fixed there either. I get exactly this:
https://code.google.com/p/chromium/issues/detail?id=351230#c64
(the gdk_window_set_user_time called on non-toplevel error)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed. No strange behaviour with 38.0.2125.111. Only expected and
working behaviour.
Good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309145
Title:
Chromium 34+ ignores ComposeKey (with
** Bug watch added: Sudo Bugzilla #649
http://www.sudo.ws/bugs/show_bug.cgi?id=649
** Also affects: sudo via
http://www.sudo.ws/bugs/show_bug.cgi?id=649
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for that detailed explanation Michael.
I'm not sure why the other apps didn't pose any problems without the
indicator-appmenu. But it's all moot now.
The desktops have been upgraded to 14.04. Let's focus on the problems of
the future!
Closing. (If I have the power to do so.)
** Changed
Public bug reported:
On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf
20150410-232623), I've had the following issue:
- both SIMs are inserted, I'm asked to unlock one SIM, and the text
above says SIM2 while in fact it wanted the pin code for SIM1 (and vice
versa): notably, the
** Summary changed:
- [greeter] strange persistant Enter SIM1 PIN dialog on Greeter
+ [greeter] strange persistent Enter SIM1 PIN dialog on Greeter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf
20150410-232623), I've noticed the following:
even though the phone is supposed to be locked, one can:
- read incoming messages from the notification (top swipe) area,
- change on/off state of bluetooth, gps,
Agreed. I tried Europe first, before I searched for Amsterdam. And when
selecting that, I saw that it had properly converted that to the
appropriate Europe/Amsterdam.
If we're configuring time, it should IMO not ask for location, but for a
timezone, which is Europe/Amsterdam. I don't want to tell
*** This bug is a duplicate of bug 1358340 ***
https://bugs.launchpad.net/bugs/1358340
Oops. Hadn't found those. Sorry.
Disabling both the Launcher and Notifications and quick settings
suits my needs.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf
20150410-232623), I've noticed the following:
- even though I've disabled GPS and Location detection, the crosshair icon is
always on.
- after playing around with *enabling* the GPS and waiting a bit, the icon
Public bug reported:
On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf
20150410-232623), I've noticed the following:
- the Rotation locked icon appears as phone which can be rotated,
which is illogical to me. If the rotation is locked, then I'd expect the
icon to cross out the
*** This bug is a duplicate of bug 1447479 ***
https://bugs.launchpad.net/bugs/1447479
** This bug has been marked a duplicate of bug 1447479
SIM Pin1 and Pin2 headings get mixed up sometimes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
100% reproducible:
- boot with dual sim,
- when it says sim 1: press X (to cancel)
- then it says sim 1, but it wants sim 2 code
- enter sim 2 code
- at this point, only sim 2 is activated,
- authenticate, go to network, unlock sim 1, now it says sim 2 but wants sim
1 code
--
You received this
My proposal is to have two icons:
orientation-lock.svg [standing + flat phone + X]
and
orientation-unlock.svg [standing + flat phone + move-arrow]
What do you think about that?
Awesome!
Right now the latter image [standing + flat phone + move-arrow] is used
for the lock case; so that would
No idea; I only noticed this when initially using the phone.
If you think it's fixed in the next version, I'll believe you. I'll
reopen if it happens again.
Thanks!
** Changed in: indicator-location (Ubuntu)
Status: New = Fix Released
** Changed in: indicator-location (Ubuntu RTM)
Same here. I had the Using GPS only since I bought the phone and GPS
never worked. Days/weeks of uptime should be enough to get a GPS lock,
right?
Now I enabled the GPS/Wifi/mobile-network (HERE), rebooted, and like
you said, within 30 seconds, the SensorsStatus tool started reporting
GPS info.
The released new icon solves this problem indeed.
I'm not fond of the new gsm-signal and wifi indicators though, but
that's another matter ;)
Thanks for the fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also on Ubuntu 14.04. This has never happened to me before, as fas as
I'm aware, and now twice in a row:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.2 LTS
Release:14.04
Codename: trusty
Versions:
compiz
void
StaticSwitchScreen::getWindowPosition (unsigned int index,
int *x,
int *y)
{
int row, column;
if (index >= windows.size ())
return;
column = (int)index % xCount;
row=
I've never had GPS location work without the HERE functions enabled. As
soon as I disable it (I have to restart for a change to take effect) I
get *no* location info whatsoever. (I have waited for weeks to get a GPS
lock, to no avail.)
The SensorsStatus tool tells me (when HERE is enabled) that I
I think so. I did a single attempt at reproducing it recently, I didn't
succeed.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465959
Title:
In phones with two SIMs, if you don't unlock
** Attachment added: "VarLogDistupgradeMainlog.txt"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1613183/+attachment/4721073/+files/VarLogDistupgradeMainlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
The GUI warned that ubuntu-minimal could not be located.
The console version showed this:
"""
After updating your package information, the essential package
'ubuntu-minimal' could not be located. This may be because you have
no official mirrors listed in your software
Public bug reported:
Versions:
python-pil:amd64 3.1.2-0ubuntu1
python-pisa3.0.32-3
Exception:
File "...", line 172, in to_pdf
context = CreatePDF(src=source, dest=destination, default_css=DEFAULT_CSS)
File
It works.
$ apt-cache policy pdns-recursor
pdns-recursor:
Installed: 4.0.0~alpha2-2
Candidate: 4.0.0~alpha2-2ubuntu0.1
Version table:
4.0.0~alpha2-2ubuntu0.1 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/universe amd64
Packages
4.0.0~alpha2-2osso1 500
Thanks for you reply. Looks like it indeed.
The only confusing bit left was the apparent "crashing" of the release-
upgrade dialog, causing the startup of apport and this bug report in the
first place.
A dialog with "we cannot properly convert your sources.list, please fix
it manually" and no
I happens every now and then as far as I can tell (xenial here, but seen
with earlier OSes):
Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report
/etc/cron.weekly )
```
/etc/cron.weekly/apt-xapian-index:
Exception ignored in: >
Traceback (most recent call last):
File
54.0.2840.100-0ubuntu0.16.10.1326 from 'ppa:canonical-chromium-
builds/stage' (on Yakkety) hasn't crashed yet. (Running for 10 minutes
now.) Beats having to switch to FF for some pages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Okay, that didn't take long. My slack windows started to "Aw snap!"
within another 10 minutes.
Both the Xenial [*1] version and the version from Haw Loeung (hloeung)
[*2] work fine though. Where the second is better because the broken
Xenial version is lower and would be auto-replaced with the
s/the broken Xenial version is lower/the fixed Xenial version is lower/
(sorry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641380
Title:
chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
The patch is present in rec-4.0.0-beta1, so if Yakkety runs >=4.0.0 (not
alpha), we should be good.
But sure:
$ grep VERSION /etc/os-release
VERSION="16.10 (Yakkety Yak)"
VERSION_ID="16.10"
VERSION_CODENAME=yakkety
$ dpkg -l pdns-recursor | grep ^ii
ii pdns-recursor 4.0.1-1build2 amd64
Public bug reported:
The pdns-recursor in Xenial returns this:
$ dig A umcg-nl.mail.protection.outlook.com. @127.0.0.1 +edns +dnssec
...
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 57895
While it should return this:
...
umcg-nl.mail.protection.outlook.com. 10
A google search turned up this as the most likely candidate for my
logrotate+gzip issues.
I'm going to try this for a workaround:
/var/log/upstart/*.log {
daily
missingok
rotate 7
compress
notifempty
nocreate
# Added by wjd 2017-03 for launchpad
That should be `; true` or ` || true`, but not ` | true`.
Reproduced on Xenial machine where I first installed uwsgi and then
uwsgi-plugin-python3 2.0.12-5ubuntu3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see it has been fixed in later versions (e.g. on Zesty):
uwsgi-2.0.14+20170111/debian$ grep BINARY_IS_UWSGI_ALTERNATIVE= -A3
uwsgi-plugin-__PLUGIN__.postinst.in*
uwsgi-plugin-__PLUGIN__.postinst.in.pri: BINARY_IS_UWSGI_ALTERNATIVE="$(\
uwsgi-plugin-__PLUGIN__.postinst.in.pri-
Update: running 4.4.0-79-generic on the original machine with issues for
24hrs (normal workload) without kernel panics thusfar. *Crosses fingers*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691741
Uptime is now 13 days. I think we can close this one as "fixed by
4.4.0-79-generic".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691741
Title:
Execute NX-protected page - 4.4.0-78-generic -
> Does the panic stop happening if you boot back into -77?
Yes. It's now running fine for more thant 3 hours now on -77.
Observe that we have upgraded more than one machine to -78, and only one
machine has trouble.
> Would it be possible for you to test the latest upstream stable kernel?
Ah,
I could be on a wild goose chase here.
But one of the prominent changes between 77 and 78 is the
backing_dev_info element of the queue turning into a pointer.
Part of the "bdi" changes in this bit:
++ * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
++
So, I tried to revert the backing_dev_info changes and dpkg-built an
updated kernel. But that didn't work out. Either because it isn't the
cause, or because I reverted too much or too little.
After several hours of normal-load uptime, a removal of the mysql data
dir quickly caused a panic. I did
Well. That did not go so well: there were no ZFS modules in the builds.
We've tried all of:
* http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-vivid/linux-
image-3.19.8-031908-generic_3.19.8-031908.201505110938_amd64.deb
* http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.68/linux-
Crash info appears the same:
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-78-generic
DUMPFILE: dump.201705191443 [PARTIAL DUMP]
CPUS: 4
DATE: Fri May 19 14:43:31 2017
UPTIME: 00:43:02
LOAD AVERAGE: 2.53, 1.81, 2.56
TASKS: 544
NODENAME:
RELEASE:
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691741
Title:
Execute NX-protected page - 4.4.0-78-generic - kernel panic
To
Okay. On a different machine with different load, we've now got the same
problem:
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-78-generic
DUMPFILE: dump.201705300948 [PARTIAL DUMP]
CPUS: 4
DATE: Tue May 30 09:48:05 2017
UPTIME: 01:47:38
LOAD AVERAGE: 0.05, 0.06, 0.04
Okay. So we've been running 4.4.70 now for 22 hours and counting on
docker1-tcn.
/var/crash# uptime
09:45:30 up 22:25, 1 user, load average: 0,01, 0,02, 0,00
/var/crash# uname -a
Linux ossoio-docker1-tcn 4.4.70-040470-generic #201705251131 SMP Thu May 25
15:34:16 UTC 2017 x86_64 x86_64
The docker1-tcn machine with vanilla kernel 4.4.70 is still up.
And on another (abmfn-staging) machine with 4.4.0-78 I've seen the
crash. According to dmesg output in the console, btrfs and other fs
modules were loaded. Probably due to an update-grub call.
After restart, I ensured that those
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691741
Title:
Execute NX-protected page - 4.4.0-78-generic - kernel panic
To
Yeap, that fixes things. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710789
Title:
chromium does not open downloaded files
To manage notifications about this bug go to:
Disabling Thunderbolt support in the BIOS (F2 during boot) worked for
me.
Suspend works.
Don't know when/if I'll need the Thunderbolt. This works for now.
Thanks!
Can I provide any additional info to help you debug/fix this properly?
Cheers,
Walter
Before disabling Thunderbolt:
[
I have the same problem, but with gpg-agent, which also reverse-depends
on graphical-session-pre.target.
Also upgraded from 17.04 (clean install) to 17.10.
I'm not sure where when the --user graphical-session-pre.target is
supposed to get started (and by whom), but it appears it never does. If
I
Hi there,
I upgraded to Ubuntu Artful the other day, and today I updated the Dell
BIOS (using the GUI tools).
Out of curiosity, I went back to check this: re-*enabling* Thunderbolt
in the BIOS *still* *breaks* *suspend*.
Again "Some devices failed to suspend, or early wake event detected".
Additional info:
- if I use pm-suspend, it just refuses to suspend (after 20secs wait)
[ma dec 25 18:33:49 2017] PM: Preparing system for sleep (mem)
...
[ma dec 25 18:33:49 2017] thunderbolt :03:00.0: Ignoring mailbox command
error (-110) in icm_suspend
[ma dec 25 18:33:49 2017] PM: Some
Yes. Also experiencing these crashes since I switched from Zesty to
Artful yesterday. A lock-screen reproduces the crash, as does turning
the monitor off.
I have a UWQHD (3440×1440) resolution, if that matters, on my Dell
monitor. I'll try to gather some more debug info.
This is highly annoying,
In my case, applying just [3] wasn't enough.
[1] https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557
[2] https://bugzilla.gnome.org/show_bug.cgi?id=788764
[3] https://bug788764.bugzilla-attachments.gnome.org/attachment.cgi?id=361654
I also had to apply [6] to fix [5]:
[4]
Perhaps this helps?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/comments/29
->
https://downloads.osso.nl/libmutter-3.26.2-ubuntu-artful/libmutter_3.26.2-0ubuntu0.1osso1/
Cheers,
Walter Doekes
OSSO B.V.
--
You received this bug notification because you are a member of
By the way, upstream appears to have a fix for this too:
https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726352
@3v1n0: I suspect that this changeset -- which should be in 3.26.3 -- does the
same:
https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've seen a crash with that exact backtrace on Artful just now.
Both on 64.0.3282.140-0ubuntu0.17.10.1 and on
64.0.3282.167-0ubuntu0.17.10.1.
For 140 I did not get a full backtrace because I could not locate the
dbgsym at the time. For 167 the backtrace ends in AsLocatedEvent() <-
No, because it won't install.
I tried "fwupdmgr install eac3961ba9bd466f6e34d9276c27d524395d7c3c-
NN1TN_NVM21.00.cab", but I got:
could not find thunderbolt device at
/sys/devices/pci:00/:00:1c.0/:01:00.0/:02:00.0/:03:00.0/domain0/0-0
So I rebooted with Thunderbolt
Ah..
$ gcc -I /usr/include/efivar 1.c -lsmbios_c
In file included from /usr/include/smbios_c/config/get_config.h:36:0,
from /usr/include/smbios_c/compat.h:27,
from /usr/include/smbios_c/smi.h:22,
from 1.c:22:
Ok, rebooted and verified that Thunderbolt was enabled. Both pm-suspend
and lid-closing now works as intended.
Dec 25 23:35:41 walter-tretton kernel: [ 53.790125] Suspended for
135.895 seconds
LGTM :okay_hand:
--
You received this bug notification because you are a member of Ubuntu
Bugs,
BIOS Setup: Settings -> System Configuration -> Thunderbolt(tm) Adapter
Configuration:
[x] Enable Thunderbolt(tm) Technology Support
[ ] Enable Thunderbolt(tm) Adapter Boot Support
[ ] Enable Thunderbolt(tm) Adapter Pre-boot Modules
(x) Security level - User Authorization
I have/had no
(And indeed, no suspend, it was waking/sleeping during the entire 1.5h it was
"suspended" just now.
$ dmesg | grep 'PM.*Preparing system for sleep' | wc -l
115)
Hi Mario, do you mean this?
$ fwupdmgr get-devices
Intel AMT (unprovisioned)
DeviceID: /dev/mei
Guid:
For the record, now that I've moved from Artful 17.10 to Bionic 18.04,
this bug is not affecting me anymore, but now bug #1724439 is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724557
Title:
I just upgraded to Ubuntu 18.04 with libmutter 3.28.0-2 and ran into
this; monitor poweroff/poweron yields a crash of gnome-shell. The good
news is that the applications are not killed like they were in 17.10
(with wayland?). But waiting for the ubuntu-bug crash file to get
generated isn't a good
1 - 100 of 139 matches
Mail list logo