I was stung by this using the Mesa driver.
I concur that it should be a dependency of libgl1-mesa-dri instead of
recommended, unless there is some downside to it that I can't see. I'm not a 3d
drivers expert.
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You
@Kai-Heng I'm running that now it seems to be working well:
$ uname -a
Linux giacomo-awin-latitude 4.4.0-100-generic #123-Ubuntu SMP Thu Nov 2
10:16:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I see many changes in the changelog, what's the patch that fixed it?
--
You received this bug
I have the impression that this bug can be abandoned, can anyone still
reproduce it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/439926
Title:
dot crashed with SIGSEGV in cairo_set_dash()
To
This is not valid anymore, as 8.10 and 9.04 are quite ancient now, and reached
their EOL years ago.
I would mark it as "Won't fix" or "Abandoned" but apparently it's not an option.
** Changed in: graphviz (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
This bug is not valid anymore as 13.04 reached its EOL in 2014
** Changed in: graphviz (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673021
Title:
This can be closed, by the looks of it, 13.04 reached its end of life a
while ago.
Well we are still a couple of versions behind: the latest packaged version is
2.38 released in 2014, while the latest upstream is 2.40.1, released in
December 2016, and Trusty is at 2.36.
But it's probably not
@Kai-Heng thanks a lot, using the modesetting driver helped!
I just read that using the Intel driver is not recommended anymore on newer
systems, I didn't know that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Kai-Heng: the problem is fixed here using your 4.4.0-99 version on my Dell
Latitude E7470 with Skylake.
Well it's buggy like on 4.4.0-72, after loggin both screens go black, but I
have my workaround works again. If I switch to text mode (Ctrl+Alt+F1) and back
(Alt+F7) both screens work
--
Sorry for the delay, I tried:
linux-image-4.4.0-83-generic doesn't work
linux-image-4.8.0-040800-generic doesn't work
linux-image-4.10.0-041000-generic works
linux-image-4.11.0-041100-generic works
By the way, I didn't mention is that even the kernel versions that work are far
from perfect.
@Kai-Heng I use a Dell E-Port Plus.
This is my ouput of lsmod | grep i915:
i915_bpo 1302528 5
intel_ips 20480 1 i915_bpo
i2c_algo_bit 16384 1 i915_bpo
drm_kms_helper155648 1 i915_bpo
drm 364544 6 i915_bpo,drm_kms_helper
video
Version 4.4.0-72-generic seems to be the last version that works for
everyone here, on different systems. I renamed this bug to mention
Intel, but Shay Perlstein above had the same problem on NVidia.
@Kai-Heng could it be the same bug even if on different graphic drivers? Do you
know if there is
The problem is only reproducible with some Kernel versions, how can it not be
related to the Kernel?
I actually have a Sky Lake, not a Haswell like the reporter.
So maybe one of those commits for Baytrail caused a regression on other Intel
Graphics processors?
Another culprit seems to be Dell
@kaihengfeng this is my output of that command:
~ $ dpkg -l | grep linux-image
hi linux-image-4.4.0-72-generic 4.4.0-72.93
amd64Linux kernel image for version 4.4.0 on 64
bit x86 SMP
ii linux-image-4.4.0-78-generic
** Summary changed:
- External monitor connecting problem
+ External monitor connecting problem on Intel graphics card
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686189
Title:
External monitor
I have this problem since linux-image-4.4.0-75
linux-image-4.4.0-77 is also affected.
linux-image-4.4.0-72 works
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@naveenkumarmula do you mind trying to boot with the previous kernel
version and see if that fixes it for you too? You should be able to
choose the Kernel to start at boot.
Btw I'm also on Intel graphics
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry for spamming everyone, as this started happening after a kernel
upgrade is it a Kernel bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686189
Title:
External monitor connecting problem
I have the same problem on 16.04.2 Xenial since upgrading the Kernel to
4.4.0-75 yesterday.
Booting the the older kernel version 4.4.0-72-generic seems to be a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It looks like db4.6 is still in Lucid but has been removed from newer
releases, can this bug be closed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793773
Title:
Just let it die in peace...
To
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
reload php5-fpm crashes
To manage notifications about this bug go to:
Hi,
We are using Precise LTS too here.
The init script from the php-fpm package in Ondřej's php5-oldstable PPA (PHP
5.4) works on Precise.
That's using start-stop-daemon instead of upstart.
So a fix for Precise, and possibly other older distributions, is to use that
init script also on PHP
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
reload php5-fpm crashes
To manage notifications about this bug go to:
Hi,
We are using Precise LTS too here.
The init script from the php-fpm package in Ondřej's php5-oldstable PPA (PHP
5.4) works on Precise.
That's using start-stop-daemon instead of upstart.
So a fix for Precise, and possibly other older distributions, is to use that
init script also on PHP
This affected me too, but I have the impression that this is a totally
different package.
This is not Maria DB, but maria: reachability analyzer for Algebraic System
Nets.
https://launchpad.net/ubuntu/+source/maria
Here is the instructions to report a bug on Maria DB:
Actually there are already 2 bugs open, probably one is a duplicate, and a
discussion abou it.
https://mariadb.atlassian.net/browse/MDEV-4079
https://mariadb.atlassian.net/browse/MDEV-3882
https://lists.launchpad.net/maria-discuss/msg00699.html
This bug should be closed as invalid...
Thanks,
Public bug reported:
Hi there,
ldapscripts by default tries to use /etc/ldap.secret generated by libnss-ldap,
but it fails because it contains a trailing new line.
This is the error found in /var/log/ldapscripts.log:
ldap_bind: Invalid credentials (49)
That's because /etc/ldap.secret is
** Description changed:
Hi there,
ldapscripts by default tries to use /etc/ldap.secret generated by
libnss-ldap, but it fails because it contains a trailing new line.
This is the error found in /var/log/ldapscripts.log:
ldap_bind: Invalid credentials (49)
+
+ Affected version:
27 matches
Mail list logo
