[Bug 1966819] Re: System will not suspend using HWE kernel.

2022-04-06 Thread Johan De Meersman 
[ removing comment, wrong kernel version. I'm seeing issue on .107, not
.105 ]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966819

Title:
  System will not suspend using HWE kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966819/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1533590] [NEW] X recognises no screens when external connected

2016-01-13 Thread Johan De Meersman 
Public bug reported:

Note that I'm really running Mint 17.3; but I don't believe they change
the kernel packages, so this is still relevant here.

When an external screen is connected through the dock (both displayport
and displayport-to-dvi, on different docks), I get a message during
startup that the X server has not found any screens.

Simply turning the screen off (not even disconnecting it) lets the
system boot into the single laptop screen as per normal. When I turn on
(or reconnect) the screen, it isn't recognised, and not even seen as far
as syslog is concerned.

When not docked, the onboard displayport connection works as normal.

Yesterday everything was normal, the only relevant upgrade that happened
was from kernel 3.16.0-38.52 to 3.19.0-32.37.

I've rebooted into the previous kernel, and that works normally - so I
suspect a regression in the i915 driver or similar?

I'm also noticing these lines in there, that aren't shown with the old
kernel:

[ 8.553727] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master
control interrupt lied (SDE)!

Kernel 3.19 loads i915_bpo and spews the above errors; kernel 3.16 uses
i915 and does not. I cannot rmmod i915_bpo as it is in use even when no
X is active; and simply loading i915 on top does not help.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-32-generic 3.19.0-32.37~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Wed Jan 13 11:04:01 2016
InstallationDate: Installed on 2015-09-22 (112 days ago)
InstallationMedia: Linux Mint 17.2 "Rafaela" - Release amd64 20150723
SourcePackage: linux-lts-vivid
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug rosa third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533590

Title:
  X recognises no screens when external connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1533590/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1520040] Re: [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)!

2016-01-12 Thread Johan De Meersman 
Having similar problem with kernel 3.19.0-32.37 and i915_bpo module -
when docked and external (displayport) screen attached, X finds no
screens with a usable configuration.

When the external screen is off or disconnected, startup works normally
into single (laptop) screen config; when undocked and using on-board
displayport connector dualscreen also works normally.

I have the same errors in dmesg, which did not occur on kernel
3.16.0-38.52. I've currently reverted back to that kernel as workaround.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1520040

Title:
  [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt
  lied (SDE)!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520040/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1051983] [NEW] Padre crashes on debug

2012-09-17 Thread Johan De Meersman 
Public bug reported:

I installed Padre on a fairly standard Mint/Cinnamon desktop (Maya,
based on Ubuntu Precise), from the usual repositories. It installs and
works fine, but whenever I try do debug a script, It crashes and I get
the following:

Unable to connect to remote host: localhost:12466
Compilation failed in require.
 at perlpadretest.pl line 0
main::BEGIN() called at perlpadretest.pl line 0
eval {...} called at perlpadretest.pl line 0
BEGIN failed--compilation aborted.
 at perlpadretest.pl line 0
Debugged program terminated.  Use q to quit or R to restart,
  use o inhibit_exit to avoid stopping after program termination,
  h q, h R or h o to get additional info.  
  DB1 

This is Padre 0.90.ds1-1 on 32-bit, with perl 5.14.2-6ubuntu2.1.

** Affects: padre (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051983

Title:
  Padre crashes on debug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/padre/+bug/1051983/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs