[Bug 2060303] Re: ubuntu 22.04.4 lock up with nvidia driver, "NVRM: GPU 0000:01:00.0: GPU has fallen off the bus."

[LGB [Gábor Lénárt]]

Kernel log relevant part:

Apr  5 15:37:00 rygel kernel: [ 2925.004224] pcieport :00:01.0: PME: 
Spurious native interrupt!
Apr  5 15:37:25 rygel kernel: [ 2949.648804] pcieport :00:01.0: PME: 
Spurious native interrupt!
Apr  5 15:37:36 rygel kernel: [ 2960.804915] pcieport :00:01.0: PME: 
Spurious native interrupt!
Apr  5 15:37:48 rygel kernel: [ 2973.253151] pcieport :00:01.0: PME: 
Spurious native interrupt!
Apr  5 15:38:00 rygel kernel: [ 2984.989466] pcieport :00:01.0: PME: 
Spurious native interrupt!
Apr  5 15:41:38 rygel kernel: [ 3202.837449] pcieport :00:01.0: PME: 
Spurious native interrupt!
Apr  5 15:42:17 rygel kernel: [ 3241.782062] pcieport :00:01.0: PME: 
Spurious native interrupt!
Apr  5 15:42:57 rygel kernel: [ 3282.354685] NVRM: GPU at PCI::01:00: 
GPU-78091d7e-2007-c450-19a1-f764cae07b00
Apr  5 15:42:57 rygel kernel: [ 3282.354689] NVRM: Xid (PCI::01:00): 79, 
pid='', name=, GPU has fallen off the bus.
Apr  5 15:42:57 rygel kernel: [ 3282.354691] NVRM: GPU :01:00.0: GPU has 
fallen off the bus.
Apr  5 15:42:57 rygel kernel: [ 3282.354730] NVRM: A GPU crash dump has been 
created. If possible, please run
Apr  5 15:42:57 rygel kernel: [ 3282.354730] NVRM: nvidia-bug-report.sh as root 
to collect this data before
Apr  5 15:42:57 rygel kernel: [ 3282.354730] NVRM: the NVIDIA kernel module is 
unloaded.
Apr  5 15:43:02 rygel kernel: [ 3287.474709] NVRM: Error in service of callback 
Apr  5 15:48:05 rygel kernel: [ 3590.071558] Asynchronous wait on fence 
NVIDIA:nvidia.prime:11cbb timed out (hint:intel_atomic_commit_ready [i915])

Please note, that the "Spurious native interrupt" thing may or may not
be related, I see those since the very beginning all the time, when I
first used this notebook, it seems it's a constant thing. So maybe that
could be ignored though. Like that, this line:

Mar  3 10:13:07 rygel kernel: [  634.685830] workqueue: pm_runtime_work
hogged CPU for >11428us 16 times, consider switching to WQ_UNBOUND

is also a very frequent guest of mine :) since ages, no idea what it
means though, or connected to the problem or not.


lspci:


01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce MX550] (rev a1)
Subsystem: Dell Device 0b0f
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [420 v2] Advanced Error Reporting
UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- 
AdvNonFatalErr-
CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- 
AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- 
ECRCChkCap- ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog:    
Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=024 
Capabilities: [900 v1] Secondary PCI Express
LnkCtl3: LnkEquIntrruptEn- PerformEqu-
LaneErrStat: 0
Capabilities: [bb0 v1] Physical Resizable BAR
BAR 0: current size: 16MB, supported: 16MB
BAR 1: current size: 256MB, supported: 64MB 128MB 256MB
BAR 3: current size: 32MB, supported: 32MB
Capabilities: [c1c v1] Physical Layer 16.0 GT/s 
Capabilities: [d00 v1] Lane Margining at the Receiver 
Capabilities: [e00 v1] Data Link Feature 
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia

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

Title:
  ubuntu 22.04.4 lock up with nvidia driver, "NVRM: GPU :01:00.0:
  GPU has fallen off the bus."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2060303/+subscriptions


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

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11

[LGB [Gábor Lénárt]]

Probably not related, but "nvidia-driver-535" was mentioned above in a
post. I'm now using ppa:vanvugt/mutter and it seems to be fine, but apt
also upgraded nvidia driver from 525 to 535 (maybe not related at all
just the new nvidia driver was presented now?). Since then I have hard
lock-ups on my system what I've never seen before (no keyboard and mouse
works). After forced power-off I see this in the kernel log file:

Apr 5 15:42:57 rygel kernel: [ 3282.354685] NVRM: GPU at PCI::01:00: 
GPU-78091d7e-2007-c450-19a1-f764cae07b00
Apr 5 15:42:57 rygel kernel: [ 3282.354689] NVRM: Xid (PCI::01:00): 79, 
pid='', name=, GPU has fallen off the bus.
Apr 5 15:42:57 rygel kernel: [ 3282.354691] NVRM: GPU :01:00.0: GPU has 
fallen off the bus.
Apr 5 15:42:57 rygel kernel: [ 3282.354730] NVRM: A GPU crash dump has been 
created. If possible, please run
Apr 5 15:42:57 rygel kernel: [ 3282.354730] NVRM: nvidia-bug-report.sh as root 
to collect this data before
Apr 5 15:42:57 rygel kernel: [ 3282.354730] NVRM: the NVIDIA kernel module is 
unloaded.
Apr 5 15:43:02 rygel kernel: [ 3287.474709] NVRM: Error in service of callback
Apr 5 15:48:05 rygel kernel: [ 3590.071558] Asynchronous wait on fence 
NVIDIA:nvidia.prime:11cbb timed out (hint:intel_atomic_commit_ready [i915])

I've never seen anything similar before, though I have this very
system/install with nvidia's driver since more than a year or so. Since
it's probably a totally different issue (though I am not 100% sure),
I've reported here: https://bugs.launchpad.net/ubuntu/+source/nvidia-
graphics-drivers-535/+bug/2060303

It seems now this hard lock up occurs several times per day :( Though
the terminal slowness/keyboard input lag/etc is gone, which is good, of
course!

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

Title:
  Input lag or freezes on Nvidia desktops with X11

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions


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

[Bug 2060303] Re: ubuntu 22.04.4 lock up with nvidia driver, "NVRM: GPU 0000:01:00.0: GPU has fallen off the bus."

[LGB [Gábor Lénárt]]

I'm sorry for the flood of comments, but it happened again two times
already, and I guess I see a pattern when it occurs: if I use the
computer to browse the web, watch some videos, or writing some C program
with vim, or whatever, it's fine. However if I let it alone for more
than 5-10 mins or so (no need to screen lock, or bother with closing the
lid of the notebook or anything!) then it happens.

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

Title:
  ubuntu 22.04.4 lock up with nvidia driver, "NVRM: GPU :01:00.0:
  GPU has fallen off the bus."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2060303/+subscriptions


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

[Bug 2060303] [NEW] ubuntu 22.04.4 lock up with nvidia driver, "NVRM: GPU 0000:01:00.0: GPU has fallen off the bus."

[LGB [Gábor Lénárt]]

Public bug reported:

I'm using Nvidia's driver on Ubuntu 22.04.4 without major issues since
about a year (or so) on this DELL Latitude 5531 notebook (01:00.0 3D
controller: NVIDIA Corporation TU117M [GeForce MX550] (rev a1)).
Yesterday, I had an ubuntu update, so I use driver 535 now, the previous
one was 525.

After some hours after going to have lunch, I found my notebook locked
up, I could not use my keyboard, mouse, and the fan of  the notebook was
almost "screaming" already. I don't remember a single event like this
before the upgrade (with 525, and older ones before).

Now, it happened again after a hour or so, and seems to be a regular
theme from now :( Which is - for sure - very problematic since I had to
hard power-off the system losing all non-saved work and workflow all the
time.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-535 535.161.07-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  5 15:52:11 2024
InstallationDate: Installed on 2022-09-23 (560 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: nvidia-graphics-drivers-535
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-535 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy third-party-packages wayland-session

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

Title:
  ubuntu 22.04.4 lock up with nvidia driver, "NVRM: GPU :01:00.0:
  GPU has fallen off the bus."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2060303/+subscriptions


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

[Bug 2060303] Re: ubuntu 22.04.4 lock up with nvidia driver, "NVRM: GPU 0000:01:00.0: GPU has fallen off the bus."

[LGB [Gábor Lénárt]]

** Attachment added: "Not sure if it helps, it's the reported gathered with 
nvidia-bug-report.sh"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2060303/+attachment/5761734/+files/nvidia-bug-report.log.gz

** Description changed:

  I'm using Nvidia's driver on Ubuntu 22.04.4 without major issues since
  about a year (or so) on this DELL Latitude 5531 notebook (01:00.0 3D
  controller: NVIDIA Corporation TU117M [GeForce MX550] (rev a1)).
  Yesterday, I had an ubuntu update, so I use driver 535 now, the previous
  one was 525.
  
  After some hours after going to have lunch, I found my notebook locked
  up, I could not use my keyboard, mouse, and the fan of  the notebook was
  almost "screaming" already. I don't remember a single event like this
  before the upgrade (with 525, and older ones before).
  
  Now, it happened again after a hour or so, and seems to be a regular
  theme from now :( Which is - for sure - very problematic since I had to
  hard power-off the system losing all non-saved work and workflow all the
  time.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nvidia-driver-535 535.161.07-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 15:52:11 2024
  InstallationDate: Installed on 2022-09-23 (560 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: nvidia-graphics-drivers-535
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ 
+ I've encountered this issue with this one: 
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2059847 please see my 
comment: 
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2059847/comments/37

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

Title:
  ubuntu 22.04.4 lock up with nvidia driver, "NVRM: GPU :01:00.0:
  GPU has fallen off the bus."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2060303/+subscriptions


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

[Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11

[LGB [Gábor Lénárt]]

I've fetched some older versions (again, I am running 22.04.4) of
packages gir1.2-mutter-10 libmutter-10-0 and mutter-common and made them
into hold status. After a very ugly and dangerous move, namely editing
/var/lib/dpkg/status by hand (to comply the dependencies of gnome-shell
which was broken by forcing older versions of packages ... maybe I
should have simply installed also older version of gnome-shell, hmm
...), now everything works perfectly again.

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

Title:
  Input lag in native terminal on Nvidia desktops with X11

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions


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

[Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11

[LGB [Gábor Lénárt]]

I have similar problem. I'm currently using Ubuntu 22.04.4 LTS (x86_64).
Since some days (maybe three?) I see very odd behaviour from programs
running in gnome-terminal (or xfce4-terminal if it does not matter, I
guess the problem is not the terminal itself but VTE probably or
similar? - no problem when using KDE's Konsole for example!). I also
have nvidia's driver.

Some programs "only" have very significant input delay, sometimes like 1
sec or so. However interestingly some programs (most notably neomutt)
has "infinite" delay, ie, it lags behind exactly one key. For example if
I move upwards in the email list, then pressing down still moves up
once. And so on, it seems to be true for all keys. Other applications
running in terminal seems to "only" have more significant delay, but
it's not always consistent. Especially ssh'ing to a remote machine is a
very bad experience now, but even on the local host, without any ssh
involved just the shell, it's very notable.


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.4 LTS
Release:22.04
Codename:   jammy
$ dpkg -l | grep mutter
ii  gir1.2-mutter-10:amd6442.9-0ubuntu7 
  amd64GObject introspection data for Mutter
ii  libmutter-10-0:amd64  42.9-0ubuntu7 
  amd64window manager library from the Mutter window manager
ii  mutter-common 42.9-0ubuntu7 
  all  shared files for the Mutter window manager

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

Title:
  Input lag in native terminal on Nvidia desktops with X11

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions


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

[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height

[LGB [Gábor Lénárt]]

I'm using 20.04.2 LTS (focal), I can also confirm the problem exists
there with Xorg and gnome-shell (no idea about 20.10 and/or Wayland
though).

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

Title:
  Terminal height shrinks - repeatedly restored shorter than the
  previous height

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions

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

[Bug 1888617] Re: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build

[LGB [Gábor Lénárt]]

It seems update 435.21-0ubuntu0.18.04.3 of nvidia-kernel-source-435
fixed the problem for me, at least!

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

Title:
  nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module
  failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1888617/+subscriptions

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

[Bug 1888617] [NEW] nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build

[LGB [Gábor Lénárt]]

Public bug reported:

After a "usual" upgrade, my system did not give any sign of life on the
monitor. I tried to boot an older kernel, it worked. Then I discovered,
that the problem that nvidia drivers cannot be built against kernel
linux-image-5.4.0-42-generic, which could be the problem.

from /var/crash/nvidia-kernel-source-435.0.crash :

 /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: 
‘DRIVER_PRIME’ undeclared here (not in a function); did you mean 
‘DRIVER_PCI_DMA’?
  .driver_features= DRIVER_GEM | DRIVER_PRIME | DRIVER_RENDER,
 ^~~~
 DRIVER_PCI_DMA
 scripts/Makefile.build:273: recipe for target 
'/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o' failed
 make[2]: *** [/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o] 
Error 1
 make[2]: *** Waiting for unfinished jobs
./tools/objtool/objtool check  --module --retpoline --uaccess 
/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm.o
./tools/objtool/objtool check  --module --retpoline --uaccess 
/var/lib/dkms/nvidia/435.21/build/nvidia-uvm/uvm8_range_group_tree_test.o
./tools/objtool/objtool check  --module --retpoline --uaccess 
/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-utils.o
./tools/objtool/objtool check  --module --retpoline --uaccess 
/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-encoder.o
./tools/objtool/objtool check  --module --retpoline --uaccess 
/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-gem.o
./tools/objtool/objtool check  --module --retpoline --uaccess 
/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-connector.o
./tools/objtool/objtool check  --module --retpoline --uaccess 
/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-crtc.o
 Makefile:1731: recipe for target '/var/lib/dkms/nvidia/435.21/build' failed
 make[1]: *** [/var/lib/dkms/nvidia/435.21/build] Error 2
 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-42-generic'
 Makefile:81: recipe for target 'modules' failed
 make: *** [modules] Error 2
DKMSKernelVersion: 5.4.0-42-generic
Date: Wed Jul 22 08:08:55 2020
DuplicateSignature: 
dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44:
 error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean 
‘DRIVER_PCI_DMA’?
Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2
PackageVersion: 435.21-0ubuntu0.18.04.2
SourcePackage: nvidia-graphics-drivers-435
Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module 
failed to build

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-62-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
DKMSKernelVersion: 5.4.0-42-generic
Date: Wed Jul 22 08:08:55 2020
Dependencies:
 
DuplicateSignature: 
dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44:
 error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean 
‘DRIVER_PCI_DMA’?
InstallationDate: Installed on 2020-01-06 (198 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageVersion: 435.21-0ubuntu0.18.04.2
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12ubuntu0.1
SourcePackage: nvidia-graphics-drivers-435
Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-435 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module
  failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1888617/+subscriptions

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

[Bug 1881038] [NEW] when trying to lock my screen I always get: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()

[LGB [Gábor Lénárt]]

Public bug reported:

When I try to lock the screen, gnome-shell seems to crash, always since
two days or so (I update daily basis). crash file is attached. x86_64
Ubuntu 20.04 LTS

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 28 01:38:46 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-03-06 (82 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "crash file"
   
https://bugs.launchpad.net/bugs/1881038/+attachment/5377584/+files/_usr_bin_gnome-shell.1000.crash

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

Title:
  when trying to lock my screen I always get: gnome-shell crashed with
  SIGSEGV in _st_theme_node_ensure_background()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881038/+subscriptions

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

[Bug 1833878] Re: pressing key TAB after ipset gives syntax error in bash interactive session

[LGB [Gábor Lénárt]]

** Description changed:

  After typing ipset (and a space of course) I always get various syntax
  error messages if I press key TAB for completion. Interestingly I get
  different errors on different machines, for example:
  
  18.04 server:
  
  # ipset
  So I typed "ipset" and a space, and when I press TAB, I see this:
  # ipset bash: syntax error near unexpected token `;;'
  
  18.04 xubuntu install:
  
  # ipset
  again, I typed "ipset" and space, and I pressed TAB:
  # ipset bash: syntax error in conditional expression
  
  18.04 ubuntu install:
  
  (the same as before, when I press tab)
  # ipset bash: syntax error in conditional expression
  bash: syntax error near `213_stat'
  
  (213_stat is maybe a file name by the way, since I have a file named
  213_stat in the current working directory)
  
  By the way, this also applies when I'm different context of the command,
  ie:
  
  # ipset save
- "ipset save" and a space, pressing space:
+ "ipset save" and a space, pressing TAB:
  # ipset save bash: syntax error near unexpected token `;;'
  
  It seems, if the current command line is anything to do with ipset, it
  causes errors on trying completion
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bash-completion 1:2.8-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18
  Uname: Linux 4.15.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jun 24 00:49:44 2019
  Dependencies:
-  
+ 
  InstallationDate: Installed on 2015-07-10 (1444 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: Upgraded to bionic on 2017-06-20 (733 days ago)

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

Title:
  pressing key TAB after ipset gives syntax error in bash interactive
  session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1833878/+subscriptions

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

[Bug 1833878] [NEW] pressing key TAB after ipset gives syntax error in bash interactive session

[LGB [Gábor Lénárt]]

Public bug reported:

After typing ipset (and a space of course) I always get various syntax
error messages if I press key TAB for completion. Interestingly I get
different errors on different machines, for example:

18.04 server:

# ipset
So I typed "ipset" and a space, and when I press TAB, I see this:
# ipset bash: syntax error near unexpected token `;;'

18.04 xubuntu install:

# ipset
again, I typed "ipset" and space, and I pressed TAB:
# ipset bash: syntax error in conditional expression

18.04 ubuntu install:

(the same as before, when I press tab)
# ipset bash: syntax error in conditional expression
bash: syntax error near `213_stat'

(213_stat is maybe a file name by the way, since I have a file named
213_stat in the current working directory)

By the way, this also applies when I'm different context of the command,
ie:

# ipset save
"ipset save" and a space, pressing space:
# ipset save bash: syntax error near unexpected token `;;'

It seems, if the current command line is anything to do with ipset, it
causes errors on trying completion

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bash-completion 1:2.8-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18
Uname: Linux 4.15.0-53-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Jun 24 00:49:44 2019
Dependencies:
 
InstallationDate: Installed on 2015-07-10 (1444 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
PackageArchitecture: all
SourcePackage: bash-completion
UpgradeStatus: Upgraded to bionic on 2017-06-20 (733 days ago)

** Affects: bash-completion (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  pressing key TAB after ipset gives syntax error in bash interactive
  session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1833878/+subscriptions

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

[Bug 1825559] [NEW] Upgrading 18.10 to 19.04: cannot leave overview mode, computer needs to be restarted

[LGB [Gábor Lénárt]]

Public bug reported:

I've upgraded my Ubuntu 18.10 to 19.04. Everything looked okey, however
if I enter gnome shell "overview mode" I cannot leave it anymore, I
can't select any window, type to search etc, and all my windows are in
the foreground, covering the search bar etc, but not possible to select
them. Simply I can't do anything. I can launch applications from the
dock but cannot see and access them anymore. So basically I stuck in
overview mode which does not work too much.

What I can do, is to use the top panel to log out. If I do that, and
login again, I only get a black screen and nothing more. I have to press
the power button at that point to shut the computer off, so I can turn
on again.

It seems everything works, just entering into that "overview mode" kills
everything then and only reboot helps from that point.

Sorry, I am not sure what the official name of the gnome3 shell
"overview mode" possibly I used the wrong terminology. Also, my bad
English cannot help either to express the problem well enough, I guess.

** Affects: gnome-shell (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/1825559

Title:
  Upgrading 18.10 to 19.04: cannot leave overview mode, computer needs
  to be restarted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825559/+subscriptions

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

[Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"

[LGB [Gábor Lénárt]]

I also see these on 18.04 bionic server installs ...

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

Title:
  Annoying log message "DIGEST-MD5 common mech free"

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+subscriptions

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

[Bug 965921] Re: gnome-shell most keyboard shortcuts not working

[LGB [Gábor Lénárt]]

Still happens time to time, even with fresh 18.10 install. It's a
"miracle" that it's such an old bug, but still hits us :(

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

Title:
  gnome-shell most keyboard shortcuts not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+subscriptions

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

[Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04

[LGB [Gábor Lénárt]]

Lenovo ThinkPad L580:

$ cat /sys/bus/serio/devices/serio1/firmware_id
PNP: LEN2037 PNP0f13

$ dmesg | fgrep -i elan
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=8ee3c188-2063-45de-b270-2db3df928e18 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=1
[0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=8ee3c188-2063-45de-b270-2db3df928e18 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=1
[2.432975] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x5f3001)
[2.449022] psmouse serio1: elantech: Synaptics capabilities query result 
0x90, 0x18, 0x10.
[2.464414] psmouse serio1: elantech: Elan sample query result 00, 22, c8
[2.526860] input: ETPS/2 Elantech TrackPoint as 
/devices/platform/i8042/serio1/input/input6
[2.545342] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input5

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

Title:
  Elantech - Touchpad not working after upgrading to 18.10 from 18.04

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

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

[Bug 1804027] Re: dbus-daemon sigsegv, apport cannot report it: expected core size ...

[LGB [Gábor Lénárt]]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804027

Title:
  dbus-daemon sigsegv, apport cannot report it: expected core size ...

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

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

[Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 (ThinkPad L480)

[LGB [Gábor Lénárt]]

@Kai-Heng Feng : Wow, it fixed the issue for me at least, on Lenovo
Thinkpad L580. :) :)

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

Title:
  Elantech - Touchpad not working after upgrading to 18.10 from 18.04
  (ThinkPad L480)

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

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

[Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 (ThinkPad L480)

[LGB [Gábor Lénárt]]

I have Lenovo L580. And a similar issue. The install image written to
the USB drive worked fine, but after installation touchpad simply did
not work. I've tried everything suggested (utilizing some google
searches ...), including kernel parameters, blacklisting various i2c hid
modules, and all the combinations, but nothing. It's a fresh 18.10
install, I have no idea if it would work with previous versions, but I
rather wouldn't downgrade, if this bug is expected to be fixed.

In my case, I see this in dmesg:

[2.418397] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x5f3001)
[2.440307] psmouse serio1: elantech: Synaptics capabilities query result 
0x90, 0x18, 0x10.
[2.456358] psmouse serio1: elantech: Elan sample query result 00, 22, c8
[2.471110] psmouse serio1: elantech: Trying to set up SMBus access
[3.054187] elan_i2c 2-0015: 2-0015 supply vcc not found, using dummy 
regulator
[3.066012] elan_i2c 2-0015: failed to get resolution: -71
[3.066039] elan_i2c: probe of 2-0015 failed with error -71

Interestingly, sometimes the four first lines lines (grep'ing all lines
from dmesg containing strig 'elan'), and not the rest. But it can be,
because I tried to disable/enable touchpad in BIOS to see there is a
difference.

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

Title:
  Elantech - Touchpad not working after upgrading to 18.10 from 18.04
  (ThinkPad L480)

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

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

[Bug 1804027] Re: dbus-daemon sigsegv, apport cannot report it: expected core size ...

[LGB [Gábor Lénárt]]

** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804027

Title:
  dbus-daemon sigsegv, apport cannot report it: expected core size ...

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

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

[Bug 1804027] Re: dbus-daemon sigsegv, apport cannot report it: expected core size ...

[LGB [Gábor Lénárt]]

** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804027

Title:
  dbus-daemon sigsegv, apport cannot report it: expected core size ...

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

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

[Bug 1804027] [NEW] dbus-daemon sigsegv, apport cannot report it: expected core size ...

[LGB [Gábor Lénárt]]

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. This is a fresh 18.10 install on this new Lenovo
L580 notebook, live version of ubuntu worked fine with touchpad and
there was no window on dbus like that. However after the install it
worked only once, then not anymore, regardless of reboot, powering off
and on etc, and usually the mentioned internal error window is shown.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: dbus 1.12.10-1ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 19 17:24:50 2018
InstallationDate: Installed on 2018-11-15 (3 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1804027/+attachment/5214223/+files/Screenshot%20from%202018-11-19%2017-32-17.png

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

Title:
  dbus-daemon sigsegv, apport cannot report it: expected core size ...

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

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

[Bug 1803690] [NEW] syslog-ng crashes with assertion in Ubuntu 18.04 server, seems to be a fixed issue in up-stream

[LGB [Gábor Lénárt]]

Public bug reported:

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic
# journalctl | fgrep assertion
Nov 11 01:34:14 logserver syslog-ng[11733]: 
ERROR:../../lib/logpipe.h:314:log_pipe_queue: assertion failed: ((s->flags & 
PIF_INITIALIZED) != 0)
Nov 12 15:09:06 logserver syslog-ng[15136]: 
ERROR:../../lib/logpipe.h:314:log_pipe_queue: assertion failed: ((s->flags & 
PIF_INITIALIZED) != 0)
Nov 14 02:15:32 logserver syslog-ng[18020]: 
ERROR:../../lib/logpipe.h:314:log_pipe_queue: assertion failed: ((s->flags & 
PIF_INITIALIZED) != 0)
Nov 15 00:21:03 logserver syslog-ng[13852]: 
ERROR:../../lib/logpipe.h:314:log_pipe_queue: assertion failed: ((s->flags & 
PIF_INITIALIZED) != 0)
Nov 16 05:00:04 logserver syslog-ng[28124]: 
ERROR:../../lib/logpipe.h:314:log_pipe_queue: assertion failed: ((s->flags & 
PIF_INITIALIZED) != 0)
# dpkg -s syslog-ng | grep -i versi
Version: 3.13.2-3

I have the following assertion from syslog-ng almost every day once.
Since it's a log server for many  other servers, it's not so great to
have this problem. I've tried to google a bit, and found this:

https://github.com/balabit/syslog-ng/pull/1858

So it seems the upstream's patch against exactly this problem, just a
small quote:

"File destination (time-reap) crash under immense load. The race is in
the file destination between our queueing mechanism (affile_dd_queue())
and time-reap() (affile_dd_reap_writer()). Basically, time-reap() could
deinitialize the writer while the queue (and the writer) was being
used."

A bug report of the syslog-ng team:

https://github.com/balabit/syslog-ng/issues/1557

So, they seems to suggest to upgrade to 3.16.1 version of syslog-ng.

However, in Ubuntu 18.04 LTS, the syslog-ng is only version 3.13.2.
Since it's an LTS version, I would suggest, to backport this patch, or
better upgrade to newer syslog-ng version.

It seems to be a race condition bug, affecting any users with greater
load on logging, it seems, according to their descriptions.

Thanks!

** Affects: syslog-ng (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/1803690

Title:
  syslog-ng crashes with assertion in Ubuntu 18.04 server, seems to be a
  fixed issue in up-stream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1803690/+subscriptions

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

[Bug 1791139] Re: postfix-mysql package upgrade results in server configuration error

[LGB [Gábor Lénárt]]

Maybe it's something to do with dynamicmaps.cf, since it seems that file
always changes throughout the upgrade of postfix related packages?

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

Title:
  postfix-mysql package upgrade results in server configuration error

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

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

[Bug 1791139] Re: postfix-mysql package upgrade results in server configuration error

[LGB [Gábor Lénárt]]

By the way, I still have the suspect that something other is problematic
here as well!!

Now, I tried to upgrade a test server, where those alias maps are NOT
empty, by will. So no error messages shown with the postinst script of
the package or anything, everything seems to be ok.

Still, after upgrade postfix reports "Server configuration error" for
SMTP peers, and its log file is full of "unsupported map type" ldap or
mysql ... Again, stopping postfix then restarting cures the problem then
without any further action. But I have never seen a problem like this.

Since my reported problem here is mainly about that "if" statement in
the postinst script, what hasn't affected my second test here, and still
problem, I have the suspect that there should be another problem here as
well ..

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

Title:
  postfix-mysql package upgrade results in server configuration error

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

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

[Bug 1791139] Re: postfix-mysql package upgrade results in server configuration error

[LGB [Gábor Lénárt]]

I don't know too much about Debian bug reporting, but anyway I've tried
here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908221

** Bug watch added: Debian Bug tracker #908221
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908221

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

Title:
  postfix-mysql package upgrade results in server configuration error

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

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

[Bug 1791139] Re: postfix-mysql package upgrade results in server configuration error

[LGB [Gábor Lénárt]]

Btw, maybe an even better solution for that "if":

if postconf -h alias_database | grep -q '^mysql:' ; then

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

Title:
  postfix-mysql package upgrade results in server configuration error

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

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

[Bug 1791139] [NEW] postfix-mysql package upgrade results in server configuration error

[LGB [Gábor Lénárt]]

Public bug reported:

I wanted to upgrade my bionic system. Some postfix related packages has
been upgraded:

# apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  base-files postfix postfix-ldap postfix-mysql postfix-pcre
  python3-problem-report qemu-guest-agent
7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

# ls  /var/cache/apt/archives/postfix*deb
/var/cache/apt/archives/postfix_3.3.0-1ubuntu0.1_amd64.deb  
/var/cache/apt/archives/postfix-ldap_3.3.0-1ubuntu0.1_amd64.deb   
/var/cache/apt/archives/postfix-pcre_3.3.0-1ubuntu0.1_amd64.deb
/var/cache/apt/archives/postfix-cdb_3.3.0-1ubuntu0.1_amd64.deb  
/var/cache/apt/archives/postfix-mysql_3.3.0-1ubuntu0.1_amd64.deb

After the installation, I saw this error message:

Setting up postfix-mysql (3.3.0-1ubuntu0.1) ...
Adding mysql map entry to /etc/postfix/dynamicmaps.cf
/var/lib/dpkg/info/postfix-mysql.postinst: 33: [: =: unexpected operator

But anyway, installation seemed to be succeeded. However, I noticed,
that according to my mail logs, all mysql based postfix tables does not
work at all with "unsupported map type". Just noticed, that even with
ldap tables, not only mysql tables ...

restarting postfix seems to cured the problem, but I think, it shouldn't
work this way ...

What I found: in /var/lib/dpkg/info/postfix-mysql.postinst the
corresponding context, where the problem is (line 33):

configure)
addmap mysql
   if [ $(postconf |grep alias_database | awk '{print $3}'|awk -F \: \
   '{print $1}') = 'mysql' ]; then
   runnewaliases
   fi
;;

I guess, the problem is the following: I have the main.cf with empty
alias_database directive, since I don't use aliases at all, so in
main.cf, I have:

# grep ^alias /etc/postfix/main.cf
alias_maps = 
alias_database = 
# postconf |grep alias_database
alias_database =
# postconf |grep alias_database | awk '{print $3}'|awk -F \: '{print $1}'
#

So you see, because of my config, I get empty string ... And it seems
the postinst script is not prepared to have this, as the empty string is
represented in the script this way then:

if [ = 'mysql' ]; then

So it is understandable now, that I get this error:

/var/lib/dpkg/info/postfix-mysql.postinst: 33: [: =: unexpected operator

Because of the postinst script runs with "set -e", this error is
"fatal". Surely, I guess the same issue happens with postfix-ldap
package as well, I guess, maybe with others, I am not sure (postfix-
pcre, etc?).

I think, this should be fixed, since it can break things for everyone
using empty value for alias_database directive in main.cf

Though I am still not sure, why postfix thought these are unsupported
map types after the upgrade, and postfix restart cured the problem,
shouldn't the upgrade restart postfix anyway?

As a workaround, I put an empty hash map file into main.cf for with
option, now there is no error message in postinst script, but still,
it's a strange situation ...

Also, the logic in the script to "extract" table type is a bit
complicated I guess, I would use something like this:

if [ "$(postconf -h alias_database | cut -f1 -d:)" = "mysql" ]; then


Maybe there are better solutions than mine above, still, it's just a
quick idea (rather than multiple awk's and a grep) 

Thanks for your attention.

** Affects: postfix (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/1791139

Title:
  postfix-mysql package upgrade results in server configuration error

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

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

[Bug 1777449] Re: [18.04] unneeded gui components in dependency

[LGB [Gábor Lénárt]]

Surely, it's still a question for me, that ovirt-guest-agent really can
work without the GUI-oriented usermode package. I've created a "fake"
usermode package just to provide the dependency and everything seems to
work OK though there are minor odd things (ie, check-new-release always
hogs the CPU I guess run by some guest agent routine here but I am not
so much sure ...). I really wish an expert in this area can review how
this problem can be solved nicely, ie using ovirt-guest-agent without
any X11 related thing installed otherwise. Thanks.

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

Title:
  [18.04] unneeded gui components in dependency

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ovirt-guest-agent/+bug/1777449/+subscriptions

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

[Bug 1777449] [NEW] [18.04] unneeded gui components in dependency

[LGB [Gábor Lénárt]]

Public bug reported:

We use servers as servers, ie no libx11, libgtk or anything GUI related
can be installed as per policy. However we uses virtualisation and we
need install ovirt-guest-agent. Now, it seems, with 18.04 if I want to
install ovirt-guest-agent it has a dependency on usermode package which
states:

"Install the usermode package if you would like to provide users with
 graphical tools for certain account management tasks."

However since we don't need this, and in general, in many cases servers
don't need any X11 related stuff, why it's compulsory to install
usermode package as well? Especially it's annoying that even the
description of the usermode packages states "_IF_ you would like 
graphical tools". But we don't need, so the if statement is false :)

Now, if I try to install ovirt-guest-agent, apt wants to
download+install 65 packages with icons, fonts, etc, which is simply
insane for a server, never ever wants to run anything X11 based
application.

root@isp-mx1:~# apt-cache show ovirt-guest-agent
Package: ovirt-guest-agent
Architecture: all
Version: 1.0.13.dfsg-2
Priority: extra
Section: universe/utils
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Laszlo Boszormenyi (GCS) 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 164
Depends: python:any (>= 2.7.5-5~), udev, lsb-base, python-apt, python-dbus, 
python-ethtool, usermode, qemu-guest-agent
Filename: 
pool/universe/o/ovirt-guest-agent/ovirt-guest-agent_1.0.13.dfsg-2_all.deb
Size: 25696
MD5sum: ea3ebb62bb23a70822a7dc409e1eac36
SHA1: 31b0aacbef8434fb139a26c723db31c89659a7e8
SHA256: f2b9b71f1ee0f74c8b42f03c8d49a0b8043c393d352cb3dc06649c1b70d01947
Homepage: http://www.ovirt.org/Ovirt_guest_agent

** Affects: ovirt-guest-agent (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/1777449

Title:
  [18.04] unneeded gui components in dependency

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ovirt-guest-agent/+bug/1777449/+subscriptions

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

[Bug 1762450] Re: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command

[LGB [Gábor Lénárt]]

Removing the scsi_mod.use_blk_mq=1 from /etc/default/grub and the
mentioned udev rule file, and regenerating initial ramdisk + reboot
seems to do the trick, now everything works with default (cfq) I/O
scheduler.

Before this comment, and the problem:

# cat /sys/block/sda/queue/scheduler 
[bfq] none
# cat /sys/block/sdb/queue/scheduler 
[none] bfq 

After I removed the BFQ specific stuffs and everything worked again:

# cat /sys/block/sda/queue/scheduler 
noop deadline [cfq] 
# cat /sys/block/sdb/queue/scheduler 
noop deadline [cfq] 

So, sorry about the noise, maybe it was my fault ... Interestingly, this
setup of mine with BFQ worked in 17.10 on other machines with that
kernel parameter and udev rule I mentioned in the previous comment.

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

Title:
  [18.04] writing on thumb drives causes hang for write op, shutdown and
  'sync' command

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

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

[Bug 1762450] Re: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command

[LGB [Gábor Lénárt]]

Ok, I will investigate as soon as I have time. By the way, I am
wondering if using BFQ as I/O scheduler can be the problem, ie:

# cat /etc/udev/rules.d/60-schedulers.rules 
## set noop scheduler for non-rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="0", 
ATTR{queue/scheduler}="noop"
## set bfq scheduler for rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1", 
ATTR{queue/scheduler}="bfq"

# cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash 
scsi_mod.use_blk_mq=1 vt.handoff=1

I guess, I try to remove BFQ specific stuffs as well to see if this
fixes the problem.

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

Title:
  [18.04] writing on thumb drives causes hang for write op, shutdown and
  'sync' command

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

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

[Bug 1762450] Re: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command

[LGB [Gábor Lénárt]]

[22596.884250] sysrq: SysRq : This sysrq operation is disabled.

I got this, if I try to trigger those sysreq events by echoing t/m into
that procfs file. I'm anyway curious how sysreq stuffs can be
enabled/disabled, since I seldom use ALT-SYSREQ- combos as well, and
many of them just reports the same as with this procfs trigger:
operation is disabled.

One thing though:

If I attach the thumb drive, everything is fine, lsblk shows it, etc, I
can remove it, lsblk does not show it, no problem. The problem seems to
have after the first event when I try to write onto the device, then
whatever I try even remove thumb drive physically, lsblk still shows it,
all the "sync" commands (and anything which tries to write onto) stuck
and cannot be killed. So even shutdown of system is problematic at this
point. Now I've tried fdisk (btw, no partition on the thumb drive). Just
displaying, everything is OK. However after the "w" command the problems
begins. By checking the /proc entry for the PID of the fdisk, I see:

# cat /proc/11283/status 
Name:   fdisk
Umask:  0022
State:  D (disk sleep)
[...]


# cat /proc/11283/stat
11283 (fdisk) D 11084 11283 10324 34827 11283 4194560 673 0 4 0 0 1 0 0 20 0 1 
0 2254524 21024768 877 18446744073709551615 94293651558400 94293651671008 
140732927217664 0 0 0 0 0 0 1 0 0 17 1 0 0 16 0 0 94293653771504 94293653778500 
94293676326912 140732927223610 140732927223625 140732927223625 140732927225836 0

Full output of status file:

# cat /proc/11283/status 
Name:   fdisk
Umask:  0022
State:  D (disk sleep)
Tgid:   11283
Ngid:   0
Pid:11283
PPid:   11084
TracerPid:  0
Uid:0   0   0   0
Gid:0   0   0   0
FDSize: 256
Groups: 0 
NStgid: 11283
NSpid:  11283
NSpgid: 11283
NSsid:  10324
VmPeak:21568 kB
VmSize:20532 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM:  4176 kB
VmRSS:  3508 kB
RssAnon: 372 kB
RssFile:3136 kB
RssShmem:  0 kB
VmData:  284 kB
VmStk:   132 kB
VmExe:   112 kB
VmLib:  3144 kB
VmPTE:80 kB
VmSwap:0 kB
HugetlbPages:  0 kB
CoreDumping:0
Threads:1
SigQ:   0/13289
SigPnd: 
ShdPnd: 
SigBlk: 
SigIgn: 
SigCgt: 
CapInh: 
CapPrm: 003f
CapEff: 003f
CapBnd: 003f
CapAmb: 
NoNewPrivs: 0
Seccomp:0
Cpus_allowed:   f
Cpus_allowed_list:  0-3
Mems_allowed:   
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0001
Mems_allowed_list:  0
voluntary_ctxt_switches:73
nonvoluntary_ctxt_switches: 0

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

Title:
  [18.04] writing on thumb drives causes hang for write op, shutdown and
  'sync' command

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

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

[Bug 1762450] [NEW] [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command

[LGB [Gábor Lénárt]]

Public bug reported:

I've upgraded to 18.04. Since then, it's impossible to use thumb-drives.
If I try, on the first write operation, that operation hangs. Trying to
issue a 'sync' command that hangs too. After a while (some minutes or
so?) I see the following in kernel log / dmesg (see later). It's not
even possible to cleanly shut the computer down, as it also hangs then.

kernel is:

4.15.0-15-generic
Linux oxygene 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
$ dpkg -S /boot/vmlinuz-4.15.0-15-generic 
linux-image-4.15.0-15-generic: /boot/vmlinuz-4.15.0-15-generic
$ dpkg -l linux-image-4.15.0-15-generic
ii  linux-image-4.15.0-15-generic4.15.0-15.16  amd64
 Linux kernel image for version 4.15.0 on 64 bit x86 SMP

dmesg:


[  110.931501] usb 6-1: new high-speed USB device number 2 using xhci_hcd
[  111.083432] usb 6-1: New USB device found, idVendor=13fe, idProduct=1d00
[  111.083438] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  111.083441] usb 6-1: Product: DataTraveler 2.0
[  111.083444] usb 6-1: Manufacturer: Kingston
[  111.083447] usb 6-1: SerialNumber: 5B7402949950
[  111.157729] usb-storage 6-1:1.0: USB Mass Storage device detected
[  111.157882] scsi host6: usb-storage 6-1:1.0
[  111.158826] usbcore: registered new interface driver usb-storage
[  111.174387] usbcore: registered new interface driver uas
[  112.172295] scsi 6:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP 
PQ: 0 ANSI: 0 CCS
[  112.203451] sd 6:0:0:0: Attached scsi generic sg1 type 0
[  112.443337] sd 6:0:0:0: [sdb] 4030464 512-byte logical blocks: (2.06 GB/1.92 
GiB)
[  112.443462] sd 6:0:0:0: [sdb] Write Protect is off
[  112.443464] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
[  112.443586] sd 6:0:0:0: [sdb] No Caching mode page found
[  112.443591] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[  112.447045] sd 6:0:0:0: [sdb] Attached SCSI removable disk

this was ok, the problem is from here:

[  363.231738] INFO: task fdisk:1798 blocked for more than 120 seconds.
[  363.231745]   Tainted: G   OE4.15.0-15-generic #16-Ubuntu
[  363.231747] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  363.231750] fdisk   D0  1798   1728 0x
[  363.231754] Call Trace:
[  363.231764]  __schedule+0x297/0x8b0
[  363.231768]  ? fdatawait_one_bdev+0x20/0x20
[  363.231771]  schedule+0x2c/0x80
[  363.231775]  io_schedule+0x16/0x40
[  363.231779]  wait_on_page_bit_common+0xd8/0x160
[  363.231782]  ? page_cache_tree_insert+0xe0/0xe0
[  363.231785]  __filemap_fdatawait_range+0xfa/0x160
[  363.231788]  ? __filemap_fdatawrite_range+0xc1/0x100
[  363.231791]  ? __filemap_fdatawrite_range+0xcd/0x100
[  363.231794]  ? __sync_filesystem+0x60/0x60
[  363.231797]  filemap_fdatawait_keep_errors+0x1e/0x40
[  363.231799]  fdatawait_one_bdev+0x16/0x20
[  363.231802]  iterate_bdevs+0xb7/0x160
[  363.231805]  sys_sync+0x7e/0xb0
[  363.231809]  do_syscall_64+0x73/0x130
[  363.231813]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[  363.231816] RIP: 0033:0x7f2fcff17287
[  363.231817] RSP: 002b:7fffbbea61a8 EFLAGS: 0202 ORIG_RAX: 
00a2
[  363.231820] RAX: ffda RBX: 56096b767400 RCX: 7f2fcff17287
[  363.231821] RDX:  RSI: 56096b766018 RDI: 56096b767400
[  363.231823] RBP: 7fffbbea82d8 R08: 000a R09: 7472617020656854
[  363.231824] R10: 0008 R11: 0202 R12: 56096a25b198
[  363.231825] R13:  R14: 56096a25b198 R15: 
[  484.045928] INFO: task fdisk:1798 blocked for more than 120 seconds.
[  484.045934]   Tainted: G   OE4.15.0-15-generic #16-Ubuntu
[  484.045936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  484.045939] fdisk   D0  1798   1728 0x
[  484.045942] Call Trace:
[  484.045950]  __schedule+0x297/0x8b0
[  484.045954]  ? fdatawait_one_bdev+0x20/0x20
[  484.045956]  schedule+0x2c/0x80
[  484.045959]  io_schedule+0x16/0x40
[  484.045962]  wait_on_page_bit_common+0xd8/0x160
[  484.045965]  ? page_cache_tree_insert+0xe0/0xe0
[  484.045967]  __filemap_fdatawait_range+0xfa/0x160
[  484.045970]  ? __filemap_fdatawrite_range+0xc1/0x100
[  484.045972]  ? __filemap_fdatawrite_range+0xcd/0x100
[  484.045975]  ? __sync_filesystem+0x60/0x60
[  484.045977]  filemap_fdatawait_keep_errors+0x1e/0x40
[  484.045979]  fdatawait_one_bdev+0x16/0x20
[  484.045981]  iterate_bdevs+0xb7/0x160
[  484.045984]  sys_sync+0x7e/0xb0
[  484.045987]  do_syscall_64+0x73/0x130
[  484.045990]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[  484.045992] RIP: 0033:0x7f2fcff17287
[  484.045994] RSP: 002b:7fffbbea61a8 EFLAGS: 0202 ORIG_RAX: 
00a2
[  484.045996] RAX: ffda RBX: 56096b767400 RCX: 7f2fcff17287
[  484.045997] RDX:  RSI: 56096b766018 RDI: 

[Bug 1727875] Re: All the binaries in the vice package crashes with SIGSEGV at XQueryExtension()

[LGB [Gábor Lénárt]]

It seems, the problem does not shows up if some compiles vice without
gtk3 UI.

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

Title:
  All the binaries in the vice package crashes with SIGSEGV at
  XQueryExtension()

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

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

[Bug 1727875] Re: All the binaries in the vice package crashes with SIGSEGV at XQueryExtension()

[LGB [Gábor Lénárt]]

It seems there is something wrong with GLEW. At least I reported to the
issue to the VICE team, and:

https://sourceforge.net/p/vice-emu/bugs/964/

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

Title:
  All the binaries in the vice package crashes with SIGSEGV at
  XQueryExtension()

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

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

[Bug 1727875] Re: All the emulations in the VICE package crashes with SIGSEGV at XQueryExtension()

[LGB [Gábor Lénárt]]

Now I've compiled VICE from source ("manually", with tarball from the
official site etc), and the same result, crashing, with gdb reports
things like this one (note, it was tested on two different machines
running 17.10 both with official vice package and my own compiled one,
always things like this I get):

[New Thread 0x7fffc7bc9700 (LWP 5936)]
[New Thread 0x7fffc6c60700 (LWP 5937)]

Thread 1 "x64" received signal SIGSEGV, Segmentation fault.
0x71e80add in XQueryExtension ()
   from /usr/lib/x86_64-linux-gnu/libX11.so.6
(gdb) bt
#0  0x71e80add in XQueryExtension ()
at /usr/lib/x86_64-linux-gnu/libX11.so.6
#1  0x71e74692 in XInitExtension ()
at /usr/lib/x86_64-linux-gnu/libX11.so.6
#2  0x744c551c in  () at /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
#3  0x744c0e51 in glXQueryVersion ()
at /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
#4  0x74270cfc in glxewInit ()
at /usr/lib/x86_64-linux-gnu/libGLEW.so.2.0
#5  0x74279043 in glewInit ()
at /usr/lib/x86_64-linux-gnu/libGLEW.so.2.0
#6  0x55770bd4 in realize_opengl_cb (area=, 
user_data=0x57f2b1d0) at opengl_renderer.c:170
#7  0x74a3cf9d in g_closure_invoke ()
at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x74a4fcde in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x74a584b5 in g_signal_emit_valist ()
at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x74a58ecf in g_signal_emit ()
at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x7584de76 in gtk_widget_realize ()
at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#12 0x7584e178 in gtk_widget_map ()
at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
---Type  to continue, or q  to quit---
#13 0x756af0c0 in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#14 0x7562aaef in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#15 0x74a3d0e0 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x74a5879f in g_signal_emit_valist ()
at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x74a58ecf in g_signal_emit ()
at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x7584e122 in gtk_widget_map ()
at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#19 0x7586441f in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#20 0x74a3d1d6 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x74a5879f in g_signal_emit_valist ()
at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x74a58ecf in g_signal_emit ()
at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#23 0x7584e122 in gtk_widget_map ()
at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#24 0x7585bf9d in  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#25 0x74a3cf9d in g_closure_invoke ()
at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#26 0x74a4fdae in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#27 0x74a584b5 in g_signal_emit_valist ()
at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#28 0x74a58ecf in g_signal_emit ()
---Type  to continue, or q  to quit---
at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#29 0x75847ee6 in gtk_widget_show ()
at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#30 0x55769f67 in video_canvas_create 
(canvas=canvas@entry=0x57f2b1d0, width=0x57f3d71c, 
height=0x57f3d720, mapped=mapped@entry=1)
at video.c:217
#31 0x55742abe in realize_canvas (raster=0x57b4f248 )
at raster.c:159
#32 0x55742abe in raster_realize (raster=raster@entry=0x57b4f248 
) at raster.c:416
#33 0x55736c8d in init_raster () at vicii.c:365
#34 0x55736c8d in vicii_init (flag=flag@entry=0) at vicii.c:411
#35 0x555d37ab in machine_specific_init () at c64.c:1020
#36 0x555b7b2b in machine_init () at machine.c:239
#37 0x555ac3d0 in init_main () at init.c:241
#38 0x555b810c in main_program (argc=, argv=) at main.c:279
#39 0x72eb31c1 in __libc_start_main (main=
0x5559a260 , argc=1, argv=0x7fffe098, init=, 
fini=, rtld_fini=, stack_end=0x7fffe088)
at ../csu/libc-start.c:308
#40 0x5559a29a in _start ()
(gdb) 


** Summary changed:

- All the emulations in the VICE package crashes with SIGSEGV at 
XQueryExtension()
+ All the binaries in the vice package crashes with SIGSEGV at XQueryExtension()

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

Title:
  All the binaries in the vice package crashes with SIGSEGV at
  XQueryExtension()

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

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

[Bug 1727875] [NEW] All the emulations in the VICE package crashes with SIGSEGV at XQueryExtension()

[LGB [Gábor Lénárt]]

Public bug reported:

It seems, with Ubuntu 17.10/Wayland/64 bit at least, _all_ of the
emulators within the VICE package (emulators for various Commodore 8 bit
systems) crashes. All of them seems to be connected with
XQueryExtension() somehow. I've tried x64 (Commodore 64 emulator), xvic
(Commodore VIC-20 emulator) and xplus4 (Commodore Plus/4 emulator). With
gdb, I got the followings (I didn't marked vice package as the bug
"source", since it can be some other library as well or so):

Thread 1 "x64" received signal SIGSEGV, Segmentation fault.
0x776c83ce in _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6
(gdb) bt
#0  0x776c83ce in _XSend () at /usr/lib/x86_64-linux-gnu/libX11.so.6
#1  0x776beb34 in XQueryExtension ()
at /usr/lib/x86_64-linux-gnu/libX11.so.6
#2  0x776b2692 in XInitExtension ()
at /usr/lib/x86_64-linux-gnu/libX11.so.6
#3  0x73c38fdf in XextAddDisplay ()
at /usr/lib/x86_64-linux-gnu/libXext.so.6
#4  0x77bcbd56 in  () at /usr/lib/x86_64-linux-gnu/libXrandr.so.2
#5  0x77bcc381 in XRRQueryExtension ()
at /usr/lib/x86_64-linux-gnu/libXrandr.so.2
#6  0x5572bc65 in  ()
#7  0x5572a79f in  ()
#8  0x55726e78 in  ()
#9  0x555bb405 in  ()
#10 0x73e5f1c1 in __libc_start_main (main=
0x555a88b0 , argc=1, argv=0x7fffe0c8, init=, 
fini=, rtld_fini=, stack_end=0x7fffe0b8)
at ../csu/libc-start.c:308
#11 0x555a88ea in  ()


Thread 1 "xplus4" received signal SIGSEGV, Segmentation fault.
0x776beae9 in XQueryExtension ()
   from /usr/lib/x86_64-linux-gnu/libX11.so.6
(gdb) bt
#0  0x776beae9 in XQueryExtension ()
at /usr/lib/x86_64-linux-gnu/libX11.so.6
#1  0x776b2692 in XInitExtension ()
at /usr/lib/x86_64-linux-gnu/libX11.so.6
#2  0x73c38fdf in XextAddDisplay ()
at /usr/lib/x86_64-linux-gnu/libXext.so.6
#3  0x77bcbd56 in  () at /usr/lib/x86_64-linux-gnu/libXrandr.so.2
#4  0x77bcc381 in XRRQueryExtension ()
at /usr/lib/x86_64-linux-gnu/libXrandr.so.2
#5  0x55687235 in  ()
#6  0x55685d6f in  ()
#7  0x55682448 in  ()
#8  0x555a1a95 in  ()
#9  0x73e5f1c1 in __libc_start_main (main=
0x5558ef40 , argc=1, argv=0x7fffe0b8, init=, 
fini=, rtld_fini=, stack_end=0x7fffe0a8)
at ../csu/libc-start.c:308
#10 0x5558ef7a in  ()


Thread 1 "xvic" received signal SIGSEGV, Segmentation fault.
0x776beae9 in XQueryExtension ()
   from /usr/lib/x86_64-linux-gnu/libX11.so.6
(gdb) bt
#0  0x776beae9 in XQueryExtension ()
at /usr/lib/x86_64-linux-gnu/libX11.so.6
#1  0x776b2692 in XInitExtension ()
at /usr/lib/x86_64-linux-gnu/libX11.so.6
#2  0x73c38fdf in XextAddDisplay ()
at /usr/lib/x86_64-linux-gnu/libXext.so.6
#3  0x77bcbd56 in  () at /usr/lib/x86_64-linux-gnu/libXrandr.so.2
#4  0x77bcc381 in XRRQueryExtension ()
at /usr/lib/x86_64-linux-gnu/libXrandr.so.2
#5  0x5569a105 in  ()
#6  0x55698c3f in  ()
#7  0x55695318 in  ()
#8  0x555a5de5 in  ()
#9  0x73e5f1c1 in __libc_start_main (main=
0x55593290 , argc=1, argv=0x7fffe0b8, init=, 
fini=, rtld_fini=, stack_end=0x7fffe0a8)
at ../csu/libc-start.c:308
#10 0x555932ca in  ()

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: vice 3.1.0.dfsg-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 27 00:22:43 2017
InstallationDate: Installed on 2015-07-10 (839 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
SourcePackage: vice
UpgradeStatus: Upgraded to artful on 2017-06-20 (128 days ago)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  All the emulations in the VICE package crashes with SIGSEGV at
  XQueryExtension()

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

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

[Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle

[LGB [Gábor Lénárt]]

*** This bug is a duplicate of bug 1288655 ***
https://bugs.launchpad.net/bugs/1288655

So, as thinking on this, I must say, maybe this is my mis-interpretation
of the problem. Maybe not the colour prompt causes this, but if I use a
newer (or ssh into a newer) ubuntu box versus ssh into an older version
(in both cases ssh in the window only changes the situation of
"shrinking" if the window title is modified to reflect this, ie like
username@machine1:~ changes into username@machine2:~ because of the
ssh). I really feel bad not to be able to express this in a sane way,
but it's kind of odd issue for me at least. Just changing PS1 does not
change the situation for me either.

Ok, now it's even more odd, just trying to test it ... Now window
shrinks by TWO lines not only one, and the behaviour I tried to describe
above seems not to apply at all :-O I don't know what I can say, maybe
this is a more complex issue and my assumption was only true for the
given case when I last tested it ...Sorry about that.

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

Title:
  gnome-terminal window becomes one line shorter after every
  fullscreen/windowed cycle

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions

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

[Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle

[LGB [Gábor Lénárt]]

*** This bug is a duplicate of bug 1288655 ***
https://bugs.launchpad.net/bugs/1288655

I don't know how to tell, but it seems the bug happens when the prompt
has effect on the title of the window. What I mean here: opening a
gnome-terminal with a colourful PS1 causes this. However if I ssh into
another machine which does update the title of the window and the prompt
does not use colour, the shrinking stops if I try fullscreen/back cycles
again ... If I ssh into a machine which does have this "new" colour
prompt then it continues ... If I ssh into a machine which does not
effect the title bar, it does not effect the strange behaviour though.
So, what I can think about there is some connection about the window bar
title updating by the prompt (???) sorry, I have really no idea hot it
happens :-O

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

Title:
  gnome-terminal window becomes one line shorter after every
  fullscreen/windowed cycle

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions

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

[Bug 1724335] [NEW] Keyboard 'alternative switch to next source' layout option is not honoured by X applications run by XWayland

[LGB [Gábor Lénárt]]

Public bug reported:

I have "Alternative switch to next source" option set to "Right Alt
(while pressed)" in "Input source options" within "Region & Language" in
settings. I use US kbd layout, but often I need my national characters,
so I use the "while pressed" solution since years, it's much faster than
always changing KBD layouts. Now, in Ubuntu 17.10 this still works
perfectly in applications like gnome-terminal. However I have the
suspect it never works now in any X applications (like: firefox, xterm,
and few of them what I've tried). So I have the feeling that "legacy" X
apps run by Xwayland does not honour the input settings properly, which
is a problem for me to using the desktop now in this form. Surely, it is
only my guess that it's the problem of Xwayland now, what runs the X
apps on "top of" wayland.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xwayland 2:1.19.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 20:12:31 2017
DistUpgraded: 2017-06-20 12:44:34,135 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.28, 4.13.0-15-generic, x86_64: installed
 virtualbox, 5.1.28, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] [1002:9996] 
(prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Richland [Radeon HD 8470D] [1849:9996]
InstallationDate: Installed on 2015-07-10 (829 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash 
scsi_mod.use_blk_mq=1 vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: Upgraded to artful on 2017-06-20 (119 days ago)
dmi.bios.date: 02/05/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.90
dmi.board.name: FM2A88M Extreme4+
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd02/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Jun 21 14:44:53 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: radeon

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  Keyboard 'alternative switch to next source' layout option is not
  honoured by X applications run by XWayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1724335/+subscriptions

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

[Bug 965921] Re: gnome-shell most keyboard shortcuts not working

[LGB [Gábor Lénárt]]

Oh, by the way, it's often happens after locking then unlocking the
screen though! It often fixes the problem too (if it was before). But
not always ...

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

Title:
  gnome-shell most keyboard shortcuts not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+subscriptions

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

[Bug 965921] Re: gnome-shell most keyboard shortcuts not working

[LGB [Gábor Lénárt]]

This bug still affects me now, upgraded to the to-be-released 17.10
(artful). I was a die hard text only user of Linux systems for a while,
so I still configure system to "emulate" something like this, ie
ALT+F1...F8 to switch between workspaces. However, ALT-F5 does not
_always_ works. Sometimes it does sometimes it doesn't and even it
changes behaviour from time to time without reboot, logout or anything,
which is strange. I can't find how I tell that alt-f5 is _my_ shortcut.
It's very annoying that system randomly 'forgets' it, and then somehow
remembers it again after some time :-O

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

Title:
  gnome-shell most keyboard shortcuts not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+subscriptions

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

[Bug 1721907] [NEW] SDL 2.0.6 fixed a dbus related problem, please include it

[LGB [Gábor Lénárt]]

Public bug reported:

It seems every SDL2 based software has problem now with 2.0.6 release of
libsdl. In my case it's only an annoying message, but as far as I see,
it can be more serious as well. I've reported the problem and they noted
it has been fixed recently. Please - if possible - make this patch into
the ubuntu package as well. Reference:

https://hg.libsdl.org/SDL/rev/dc7245e3d1f2

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libsdl2-2.0-0 2.0.6+dfsg1-2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Oct  7 04:43:54 2017
InstallationDate: Installed on 2015-07-10 (819 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
SourcePackage: libsdl2
UpgradeStatus: Upgraded to artful on 2017-06-20 (108 days ago)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  SDL 2.0.6 fixed a dbus related problem, please include it

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

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

[Bug 1373070] Re: full fix for disconnected path (paths)

[LGB [Gábor Lénárt]]

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"
fsuid=0 ouid=0

I am not an expert, but I tried to put run/systemd/journal/dev-log into
the profile, but it is not accepted as it does not start with / ... But
this is what kernel log suggest, so what can I do otherwise?

Note: I have: /usr/sbin/pdns_server flags=(complain,attach_disconnected)

But still ... (now I have only complain mode).

If I exclude pdns from systemd it works btw, and no wonder as it seems
the problem somehow connected to systemd's journal, so it's better not
to use systemd if possible since it renders apparmor unusable in my
experience :( But for sure, I would be more than happy to have a better
option, rather than deleting systemd's unit file each time after upgrade
pdns ... Or so.

this is up-to-date Ubuntu 16.04.3 LTS 64 bit, fresh install, but I have
about a dozen of servers with this problem with different daemons as
well, not only powerdns.

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

Title:
  full fix for disconnected path (paths)

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

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

[Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle

[LGB [Gábor Lénárt]]

I've just noticed: it seems it only happens if the shell prompt is
colourfull. if it's not, there is no shrinking of the gnome-terminal
window height when cycling between fullscreen and windowed mode ...
Interesting!!

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

Title:
  gnome-terminal window becomes one line shorter after every
  fullscreen/windowed cycle

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions

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

[Bug 1706008] [NEW] gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle

[LGB [Gábor Lénárt]]

Public bug reported:

It's 17.04 64 bit Ubuntu, wayland+gnome-shell. I have key F11 configured
to toggle between fullscreen and windowed mode. Just noticed, that every
time I press F11 to get full screen, then F11 to get back windowed mode,
the window becomes one line shorter ... Continuing this I can hit the
situation to have only a one line tall window. It's kinda annoying,
since during my work I use tons of terminal windows, and I often use
full screen / windowed mode switching. Now, I have to resize the window
again and again before it becomes too shallow ...

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jul 24 11:14:01 2017
InstallationDate: Installed on 2015-07-10 (744 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to zesty on 2017-06-20 (33 days ago)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wayland-session zesty

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

Title:
  gnome-terminal window becomes one line shorter after every
  fullscreen/windowed cycle

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions

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

[Bug 1704360] Re: Cannot resize gnome-terminal window in gnome wayland session with mouse

[LGB [Gábor Lénárt]]

Nice to hear, that is fixed in 17.10 already. Well, I've just read many
discussion on this topic. For example MPV issue: https://github.com/mpv-
player/mpv/issues/139  windows has no border. It seems for me, projects
like mpv waiting for some server side window decoration to be done,
instead of implementing in client side for every possible application
(and for being realistic, I feel it's a better option anyway, or well
"more realistic"), thus the issue is "wontfix". Surely, gnome-terminal
may be different being a gtk3 app, may be handled at gtk3 level for this
issue? As far as I know at least, wayland makes it possible to provide
'server side decorations' more like the classic X11 window manager
scenario. And the last comment on that issue is funny: "In two years,
every compositor will be able to draw server-side decorations."  (so
"wontfix" ...). Ok, I was kinda off-topic now, sorry about that. Now I
am more involved with gnome-terminal at least ... Thanks for the info,
that 17.10 seems to solve this issue at least!

** Bug watch added: github.com/mpv-player/mpv/issues #139
   https://github.com/mpv-player/mpv/issues/139

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

Title:
  Cannot resize gnome-terminal window in gnome wayland session with
  mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1704360/+subscriptions

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

[Bug 1704360] [NEW] Cannot resize window in gnome wayland session with mouse

[LGB [Gábor Lénárt]]

Public bug reported:

Running gnome-shell + wayland on ubuntu 17.04 here. If I have a "legacy"
(X11) application, like firefox or xterm (running with Xwayland, I
guess) I can resize its window normally, ie mouse shape changes into
resize-signaling shape near the window borders and I can do the job.
However pure-wayland clients, like gnome-terminal it simply does not
work, which is very annoying no need to say. I can do the resize with eg
ALT+right click and select "resize" but it's kinda more work to do a
very simple task (and also it seems there is only horizontal OR vertical
resize, not the both what I used to if I move the mouse near to the
corner of the window).

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-shell 3.24.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jul 14 11:43:52 2017
DisplayManager: gdm3
InstallationDate: Installed on 2015-07-10 (734 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to zesty on 2017-06-20 (23 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wayland-session zesty

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

Title:
  Cannot resize window in gnome wayland session with mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1704360/+subscriptions

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

[Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04

[LGB [Gábor Lénárt]]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688253

Title:
  Wrong resolution, and "unknown monitor" since upgraded to 17.04

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

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

[Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04

[LGB [Gábor Lénárt]]

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 much other solution I could find :(

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

Title:
  Wrong resolution, and "unknown monitor" since upgraded to 17.04

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

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

[Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04

[LGB [Gábor Lénárt]]

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 much other solution I could find :(

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

Title:
  Wrong resolution, and "unknown monitor" since upgraded to 17.04

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

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

[Bug 1700465] Re: gnome-shell --replace does not work: Can't initialize KMS backend: Could not get session ID: No such file or directory

[LGB [Gábor Lénárt]]

I don't know anything about gnome internals, but with trying to strace,
I see this:

getpeername(2, 0x7ffec62742e0, 0x7ffec62742dc) = -1 ENOTSOCK (Socket
operation on non-socket)

which is odd, since stderr is not a socket usually, indeed ...

Other than that, the mentioned error message can be found here, after
trying to "apt source" some gnome specific packages:

mutter-3.24.1/src/backends/native/meta-launcher.c

in function get_session_proxy()

Though for sure, I have exactly zero knowledge about these :-/

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

Title:
  gnome-shell --replace does not work: Can't initialize KMS backend:
  Could not get session ID: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1700465/+subscriptions

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

[Bug 1700465] [NEW] gnome-shell --replace does not work: Can't initialize KMS backend: Could not get session ID: No such file or directory

[LGB [Gábor Lénárt]]

Public bug reported:

gnome-shell --replace does not work and reports:

(gnome-shell:15848): mutter-WARNING **: Can't initialize KMS backend:
Could not get session ID: No such file or directory


(gnome-shell:16495): mutter-WARNING **: Can't initialize KMS backend: Could not 
get session ID: No such file or directory


(gnome-shell:4910): mutter-WARNING **: Can't initialize KMS backend: Could not 
get session ID: No such file or directory

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-shell 3.24.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.10.0-25.29-generic 4.10.17
Uname: Linux 4.10.0-25-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jun 26 09:03:06 2017
DisplayManager: gdm3
InstallationDate: Installed on 2015-07-10 (716 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to zesty on 2017-06-20 (5 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wayland-session zesty

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

Title:
  gnome-shell --replace does not work: Can't initialize KMS backend:
  Could not get session ID: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1700465/+subscriptions

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

[Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04

[LGB [Gábor Lénárt]]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688253

Title:
  Wrong resolution, and "unknown monitor" since upgraded to 17.04

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

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

[Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04

[LGB [Gábor Lénárt]]

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

log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /run/u-d-c-fglrx-was-loaded file
Looking for fglrx modules in /lib/modules/4.10.0-21-generic/updates/dkms
Looking for nvidia modules in /lib/modules/4.10.0-21-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is fglrx loaded? no
Was fglrx unloaded? no
Is fglrx blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is nouveau loaded? no
Is nouveau blacklisted? no
Is fglrx kernel module available? no
Is nvidia kernel module available? no
Vendor/Device Id: 8086:152
BusID "PCI:0@0:2:0"
Is boot vga? yes
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Found "/dev/dri/card0", driven by "i915"
output 0:
card0-VGA-1
Number of connected outputs for /dev/dri/card0: 1
Does it require offloading? yes
last cards number = 1
Has amd? no
Has intel? yes
Has nvidia? no
How many cards? 1
Has the system changed? No
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
Current alternative: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
Current core alternative: (null)
Current egl alternative: /usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf
Is nvidia enabled? no
Is nvidia egl enabled? no
Is fglrx enabled? no
Is mesa enabled? yes
Is mesa egl enabled? yes
Is pxpress enabled? no
Is prime enabled? no
Is prime egl enabled? no
Is nvidia available? no
Is nvidia egl available? no
Is fglrx available? no
Is fglrx-core available? no
Is mesa available? yes
Is mesa egl available? yes
Is pxpress available? no
Is prime available? no
Is prime egl available? no
Single card detected
Nothing to do
No change - nothing to do

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

Title:
  Wrong resolution, and "unknown monitor" since upgraded to 17.04

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

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

[Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04

[LGB [Gábor Lénárt]]

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 monitor section
[25.037] (II) modeset(0): EDID for output VGA-1
[25.037] (II) modeset(0): Printing probed modes for output VGA-1
[25.037] (II) modeset(0): Output VGA-1 connected
[25.037] (II) modeset(0): Output VGA-1 using initial mode 1024x768 +0+0

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

Title:
  Wrong resolution, and "unknown monitor" since upgraded to 17.04

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

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

[Bug 1688253] [NEW] Wrong resolution, and "unknown monitor" since upgraded to 17.04

[LGB [Gábor Lénárt]]

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 reports "Unknown
Display". System settings -> Software & updates  -> Additional drivers
shows title "Unknown: Unknown" though after that "Using Processor
microcode firmware for Intel CPUs from intel-microcode" is active. I
could "work the problem around" (see the end of this writing) but it's
really ugly that I need to run a script every time, when it always
worked well on the same machine before this Ubuntu release.

According to xrandr:

lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm
   1024x768  60.00* 
   800x600   60.3256.25  
   848x480   60.00  
   640x480   59.94  

My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)

Monitor is Samsung SyncMaster E2220, standard VGA-cable connection (this
monitor hasn't got any other connector like HDMI or DVI).

My workaround was to create this script and run:

DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 
-hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080

After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my script
(I played with adding some modes, that is the _60.00 stuff):

root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
   1024x768  60.00  
   800x600   60.3256.25  
   848x480   60.00  
   640x480   59.94  
   1920x1080 59.96* 
  1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width  1920 start 2048 end 2248 total 2576 skew0 clock  67.16KHz
v: height 1080 start 1083 end 1088 total 1120   clock  59.96Hz

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu May  4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Bug 1649203] [NEW] ttf-mscorefonts-installer always complains about cannot download data because http is not support by libcurl?

[LGB [Gábor Lénárt]]

Public bug reported:

I always get this:

Preparing to unpack .../ttf-mscorefonts-installer_3.4+nmu1ubuntu2_all.deb ...
mscorefonts-eula license has already been accepted
Unpacking ttf-mscorefonts-installer (3.4+nmu1ubuntu2) over (3.4+nmu1ubuntu2) ...
Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
Processing triggers for update-notifier-common (3.168.3) ...
ttf-mscorefonts-installer: processing...
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/andale32.exe
Err:1 http://downloads.sourceforge.net/corefonts/andale32.exe
  Protocol "http" not supported or disabled in libcurl
W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/andale32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
E: Failed to fetch https://kent.dl.sourceforge.net/project/corefonts/the 
fonts/final/andale32.exe  Protocol "http" not supported or disabled in libcurl

E: Download Failed

Moveover it's quite annoying that I got a window time from time to try
to download but always fails and window remains ... (surely it can be
closed manually till the next update)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ttf-mscorefonts-installer 3.4+nmu1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.2
Architecture: amd64
Date: Mon Dec 12 08:04:54 2016
InstallationDate: Installed on 2015-07-10 (520 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
PackageArchitecture: all
SourcePackage: msttcorefonts
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  ttf-mscorefonts-installer always complains about cannot download data
  because http is not support by libcurl?

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

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

[Bug 1629661] Re: Hissing sound in headphones

[LGB [Gábor Lénárt]]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: linux (Ubuntu)
   Status: Opinion => Confirmed

** Description changed:

  Ubuntu 16.04 on 64 bit produces hissing sound (just by my - far from
  being 'musical' - ear, it sounds like a sinus wave with frequency about
  1KHz or so) on headphones. Interestingly, after boot this does not
  happen and usually can be hear only after the first application which
  makes any sound (but not always, sometimes it starts later). But if any
  time it starts, it remains, whatever I do, exiting the application
  (which makes the sound) even by killing pulseaudio process, etc. I've
  read a lot on this issue but usually - it seems - always notebook
  problems mentioned, however it's a desktop machine (Asrock FM2A88M
  extreme4+ motherboard, AMD A6-6400K CPU, integrated audio). It seems it
  uses snd_hda_intel kernel module though. I've tried advices mentioned by
  various resources throughout the net, disabling powersave problems,
  using hdajackretask from alsa-tools-gui, etc, but they didn't help.
  
  Ubuntu 4.4.0-36.55-generic 4.4.16
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-41-generic 4.4.0-41.61
  ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21
  Uname: Linux 4.4.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  lgb2128 F pulseaudio
-  /dev/snd/controlC0:  lgb2128 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  lgb2128 F pulseaudio
+  /dev/snd/controlC0:  lgb2128 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct  2 14:24:21 2016
  HibernationDevice: RESUME=UUID=c92777cb-b700-4a8e-b937-1ed4983fecb1
  InstallationDate: Installed on 2015-07-10 (449 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-41-generic 
root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-41-generic N/A
-  linux-backports-modules-4.4.0-41-generic  N/A
-  linux-firmware1.157.4
+  linux-restricted-modules-4.4.0-41-generic N/A
+  linux-backports-modules-4.4.0-41-generic  N/A
+  linux-firmware1.157.4
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: FM2A88M Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd01/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

** Tags added: kernel-bug-exists-upstream

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

Title:
  Hissing sound in headphones

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

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

[Bug 1629661] Re: Hissing sound in headphones

[LGB [Gábor Lénárt]]

Sorry about my English, so I meant that I didn't own the machine itself,
so I have no experience just since I use that PC, and it's only two
weeks or so. Also, I've just discovered that the annoying sound is there
even right after switching the machine on, without any OS loaded too.

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

Title:
  Hissing sound in headphones

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

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

[Bug 1629661] Re: Hissing sound in headphones

[LGB [Gábor Lénárt]]

$ uname -a
Linux oxygene 4.8.0-040800-generic #201610022031 SMP Mon Oct 3 00:32:57 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

The really same. Moreover, this hissing sound can be heard with BIOS/etc
too, without any OS, it's even more louder then.

The issue started with this machine, I didn't have it with previous
ubuntu versions ...

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

Title:
  Hissing sound in headphones

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

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

[Bug 1629661] Re: Hissing sound in headphones

[LGB [Gábor Lénárt]]

Quite odd ... But it seems there is sometimes a louder hissing sound,
but the other one is more frequent issue: a not so loud but annoying
one. This second _seems_ to be cause (I have no idea about the reason!!)
by an XBox 360 controller. If it's plugged to the USB port, the sound
can be heard in sync with the blinking "circular green LED" on the
controller. After it stops blinking, the sound remains. If I unplug from
the USB port, the annoying noise is stopped. Maybe it's not even a
software issue, but some kind of hardware, interference, or whatever?

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

Title:
  Hissing sound in headphones

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

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

[Bug 1629661] [NEW] Hissing sound in headphones

[LGB [Gábor Lénárt]]

Public bug reported:

Ubuntu 16.04 on 64 bit produces hissing sound (just by my - far from
being 'musical' - ear, it sounds like a sinus wave with frequency about
1KHz or so) on headphones. Interestingly, after boot this does not
happen and usually can be hear only after the first application which
makes any sound (but not always, sometimes it starts later). But if any
time it starts, it remains, whatever I do, exiting the application
(which makes the sound) even by killing pulseaudio process, etc. I've
read a lot on this issue but usually - it seems - always notebook
problems mentioned, however it's a desktop machine (Asrock FM2A88M
extreme4+ motherboard, AMD A6-6400K CPU, integrated audio). It seems it
uses snd_hda_intel kernel module though. I've tried advices mentioned by
various resources throughout the net, disabling powersave problems,
using hdajackretask from alsa-tools-gui, etc, but they didn't help.

Ubuntu 4.4.0-36.55-generic 4.4.16

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-41-generic 4.4.0-41.61
ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21
Uname: Linux 4.4.0-41-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lgb2128 F pulseaudio
 /dev/snd/controlC0:  lgb2128 F pulseaudio
CurrentDesktop: Unity
Date: Sun Oct  2 14:24:21 2016
HibernationDevice: RESUME=UUID=c92777cb-b700-4a8e-b937-1ed4983fecb1
InstallationDate: Installed on 2015-07-10 (449 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-41-generic 
root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-41-generic N/A
 linux-backports-modules-4.4.0-41-generic  N/A
 linux-firmware1.157.4
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/17/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.00
dmi.board.name: FM2A88M Extreme4+
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd01/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug package-from-proposed third-party-packages xenial

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1629661/+attachment/4752825/+files/lspci-vnvn.log

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

Title:
  Hissing sound in headphones

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

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

[Bug 1615082] Re: kernel NULL pointer dereference on apparmor profile update

[LGB [Gábor Lénárt]]

It's a problem that it's a production server, I cannot play too much
with it :-/ It was a freshly installed 16.04LTS according to the
operators who did the install. According to the logs, the problematic
kernel was:

Linux version 4.4.0-34-generic (buildd@lgw01-20) (gcc version 5.3.1
20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #53-Ubuntu SMP Wed Jul 27 16:06:39
UTC 2016 (Ubuntu 4.4.0-34.53-generic 4.4.15)

It was installed with:

Linux version 4.4.0-31-generic (buildd@lgw01-16) (gcc version 5.3.1 20160413 
(Ubuntu 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 
(Ubuntu 4.4.0-
31.50-generic 4.4.13)

The -34- was already a kernel since upgrade packages. Now I have -36-, I
haven't experienced with the bug yet since then at least.

Additionaly, after the panic msg, every processes was stuck in 'D' state
trying to do anything with apparmor (etc profile reload) including the
postinst script of lxd which seems does that. After a reboot with -36-
kernel, I could finish the upgrade with "dpkg --configure -a" though.

If I again experience the bug, I'll try to test with latest upstream as
you suggested (unfortunately, as I've told, I cannot "play" with this
machine if it seems to be OK ...)

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

Title:
  kernel NULL pointer dereference on apparmor profile update

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

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

[Bug 1615082] Re: kernel NULL pointer dereference on apparmor profile update

[LGB [Gábor Lénárt]]

I've also attached some files, with full dmesg output, uname -a, lspci,
version info, and the apparmor profile for apache2.

** Attachment added: "Logs"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615082/+attachment/4724162/+files/bug-info.tgz

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

Title:
  kernel NULL pointer dereference on apparmor profile update

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

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

[Bug 1615082] [NEW] kernel NULL pointer dereference on apparmor profile update

[LGB [Gábor Lénárt]]

Public bug reported:

I've used aa-logprof to find more things out to be added to my custom
apache2 apparmor file. Since PHP created tons of files in /tmp in the
form of /tmp/php* I've decided to add this:

/tmp/php* rw,

I'm not sure if it caused the problem, but after this
/etc/init.d/apparmor reload froze and there was the following in the
output of dmesg command:


[13838.909880] audit: type=1400 audit(1471631019.426:1488): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/apache2" 
pid=23590 comm="apparmor_parser"
[13838.920067] [ cut here ]
[13838.920079] WARNING: CPU: 0 PID: 23590 at 
/build/linux-5vkMGy/linux-4.4.0/security/apparmor/label.c:142 
profile_cmp+0xed/0x180()
[13838.920083] AppArmor WARN profile_cmp: ((!b)): 
[13838.920085] Modules linked in:
[13838.920088]  binfmt_misc nf_conntrack_ftp nf_conntrack_irc ip6t_REJECT 
nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables 
ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp xt_pkttype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter 
ip_tables x_tables gpio_ich ipmi_devintf coretemp ipmi_ssif kvm dcdbas 
irqbypass i5000_edac serio_raw edac_core lpc_ich joydev input_leds i5k_amb 
ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser rdma_cm iw_cm ib_cm 
ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm 
drm_kms_helper
[13838.920166]  syscopyarea sysfillrect sysimgblt hid_generic fb_sys_fops 
usbhid uas e1000e ptp hid usb_storage psmouse drm megaraid_sas bnx2 pps_core 
pata_acpi fjes
[13838.920188] CPU: 0 PID: 23590 Comm: apparmor_parser Not tainted 
4.4.0-34-generic #53-Ubuntu
[13838.920192] Hardware name: Dell Inc. PowerEdge 1950/0DT097, BIOS 2.7.0 
10/30/2010
[13838.920195]  0086 88f44738 880128bffc00 
813f11b3
[13838.920199]  880128bffc48 81cf08e8 880128bffc38 
81081102
[13838.920204]  8800c8d7d400  000a 

[13838.920208] Call Trace:
[13838.920218]  [] dump_stack+0x63/0x90
[13838.920224]  [] warn_slowpath_common+0x82/0xc0
[13838.920228]  [] warn_slowpath_fmt+0x5c/0x80
[13838.920232]  [] ? u32_swap+0x10/0x10
[13838.920236]  [] profile_cmp+0xed/0x180
[13838.920239]  [] aa_vec_unique+0x163/0x240
[13838.920244]  [] __aa_labelset_update_subtree+0x687/0x820
[13838.920249]  [] ? kzfree+0x2d/0x40
[13838.920254]  [] aa_replace_profiles+0x59b/0xb70
[13838.920259]  [] ? __kmalloc+0x22e/0x250
[13838.920263]  [] policy_update+0x9f/0x1f0
[13838.920267]  [] profile_replace+0x13/0x20
[13838.920272]  [] __vfs_write+0x18/0x40
[13838.920275]  [] vfs_write+0xa9/0x1a0
[13838.920279]  [] ? do_sys_open+0x1bf/0x2a0
[13838.920282]  [] SyS_write+0x55/0xc0
[13838.920288]  [] entry_SYSCALL_64_fastpath+0x16/0x71
[13838.920291] ---[ end trace a19473a0fd8d9556 ]---
[13838.920305] BUG: unable to handle kernel NULL pointer dereference at 
0038
[13838.920475] IP: [] profile_cmp+0x2f/0x180
[13838.920582] PGD 128a7d067 PUD 12a6be067 PMD 0 
[13838.920684] Oops:  [#1] SMP 
[13838.920755] Modules linked in: binfmt_misc nf_conntrack_ftp nf_conntrack_irc 
ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter 
ip6_tables ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp 
xt_pkttype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
iptable_filter ip_tables x_tables gpio_ich ipmi_devintf coretemp ipmi_ssif kvm 
dcdbas irqbypass i5000_edac serio_raw edac_core lpc_ich joydev input_leds 
i5k_amb ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit
[13838.922791]  ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
hid_generic fb_sys_fops usbhid uas e1000e ptp hid usb_storage psmouse drm 
megaraid_sas bnx2 pps_core pata_acpi fjes
[13838.923223] CPU: 0 PID: 23590 Comm: apparmor_parser Tainted: GW  
 4.4.0-34-generic #53-Ubuntu
[13838.923369] Hardware name: Dell Inc. PowerEdge 1950/0DT097, BIOS 2.7.0 
10/30/2010
[13838.923485] task: 880035b86400 ti: 880128bfc000 task.ti: 
880128bfc000
[13838.923599] RIP: 0010:[]  [] 
profile_cmp+0x2f/0x180
[13838.923734] RSP: 0018:880128bffcb0  EFLAGS: 00010086
[13838.923816] RAX:  RBX: 8800c8d7d400 RCX: 0006
[13838.923916] RDX:  RSI:  RDI: 0009
[13838.924017] RBP: 880128bffcc0 R08: 000a R09: 0562

[Bug 1589816] [NEW] DNS name resolving does not work with VPNC connection

[LGB [Gábor Lénárt]]

Public bug reported:

I've configured (with network manager) a VPNC connection, address only,
ie "split tunnel" mode. However, after connecting, though everything
works, I am unable to resolve "internal" domains having "pseudo" TLD as
.intra in names. Note, that I set up a single DNS server for the VPN
connection, and indeed that DNS server after VPN connections answers
(tested with "host something.intra. 172.21.0.1" command, the same
172.21.0.1 is given for the VPN configuration), just there should be a
bug here in vpnc/ubuntu that name server is not asked for the given
name, I guess ...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: vpnc 0.5.3r550-2build1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jun  7 08:28:58 2016
InstallationDate: Installed on 2015-07-10 (332 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
SourcePackage: vpnc
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.vpnc.default.conf: [deleted]

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


** Tags: amd64 apport-bug xenial

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

Title:
  DNS name resolving does not work with VPNC connection

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

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

[Bug 1521302] Re: gnome-terminal maximize than un-maximize behaves odd

[LGB [Gábor Lénárt]]

Indeed, I use tons of terminals in my work, and I often need 
maximize/unmaximize operations, now it makes my life quite hard :(
This was my original bug-report, which is now considered as duplication of this 
bug: #1573563

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

Title:
  gnome-terminal maximize than un-maximize behaves odd

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1521302/+subscriptions

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

[Bug 1573563] Re: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10

[LGB [Gábor Lénárt]]

I've attached some screen shots, if it's more understandable than my
not-so-perfect English, sorry about that.

Moreover, I had the suspect that it can be a generic window manager
issue more, rather than gnome-terminal specific problem, but starting
the KDE console (konsole) its fullscreen toggle functionality seems to
be OK, just I have problem with the gnome-terminal, it seems.

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

Title:
  Toggling full screen mode does not work well after upgrading to Ubuntu
  16.04 from 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+subscriptions

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

[Bug 1573563] Re: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10

[LGB [Gábor Lénárt]]

** Attachment added: "Screenshot after pressing F11 again, not OK!"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+attachment/4642825/+files/Screenshot%20from%202016-04-22%2014-10-13.png

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

Title:
  Toggling full screen mode does not work well after upgrading to Ubuntu
  16.04 from 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+subscriptions

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

[Bug 1573563] [NEW] Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10

[LGB [Gábor Lénárt]]

Public bug reported:

I use tons of terminal windows (gnome-terminal) all the time for various
tasks. Thus, it's important for me to be able to go into full screen
mode (F11) - if I need more attention or space and switch back later.

I haven't got any problem with this in previous Ubuntu versions, after
"switching back" from fullscreen mode, I got the terminal window at its
original place and size. However, after upgrading to Ubuntu 16.04
recently, if I press F11 to switch back, the terminal window is enlarged
to cover almost the full desktop, it's not "full screen" anymore (that's
OK), ie I can see panel, borders, etc, but still it's not the original
size and position of the window. So I have to manually resize the window
all the time.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-terminal 3.18.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
CurrentDesktop: Unity
Date: Fri Apr 22 13:48:12 2016
InstallationDate: Installed on 2014-05-08 (715 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to xenial on 2015-10-08 (196 days ago)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 xenial

** Attachment added: "Screenshot before pressing F11"
   
https://bugs.launchpad.net/bugs/1573563/+attachment/4642820/+files/Screenshot%20from%202016-04-22%2014-09-39.png

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

Title:
  Toggling full screen mode does not work well after upgrading to Ubuntu
  16.04 from 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+subscriptions

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

[Bug 1573563] Re: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10

[LGB [Gábor Lénárt]]

** Attachment added: "Screenshot after pressing F11 (fullscreen, OK)"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+attachment/4642824/+files/Screenshot%20from%202016-04-22%2014-09-59.png

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

Title:
  Toggling full screen mode does not work well after upgrading to Ubuntu
  16.04 from 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+subscriptions

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

[Bug 1562398] [NEW] Xorg freeze on SDL2 using full screen with wine with windows program

[LGB [Gábor Lénárt]]

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 mode.
When I try to switch full screen off, I get back my desktop, and mouse
can be moved, however I can't simply do anything with keyboard and
neither with mouse anymore. If I press power-off button of my notebook,
system seems to shuts down though, but I need to do that, as it's not
possible to use my desktop anymore.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Mar 26 22:03:58 2016
DistUpgraded: 2015-10-18 23:18:25,282 INFO cache.commit()
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.14, 4.2.0-30-generic, i686: installed
 virtualbox, 5.0.14, 4.2.0-34-generic, i686: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21dd]
InstallationDate: Installed on 2012-03-03 (1484 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: LENOVO 5016NW6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to wily on 2015-10-18 (159 days ago)
dmi.bios.date: 11/04/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8GET38WW (1.15 )
dmi.board.name: 5016NW6
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 5016NW6
dmi.product.version: ThinkPad L520
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sat Mar 26 20:31:35 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id9196 
 vendor AUO
xserver.version: 2:1.17.2-1ubuntu9.1

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


** Tags: apport-bug compiz-0.9 freeze i386 ubuntu wily

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

Title:
  Xorg freeze on SDL2 using full screen with wine with windows program

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

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

[Bug 1322751] Re: Compiz running on Intel Haswell GPU has 100% CPU usage when computer is locked

[LGB [Gábor Lénárt]]

I  have this bug (also as bug 1508219 which is now marked as duplication
of this report) on three different machines, each of them were verified
via ssh, that indeed, compiz uses 100% CPU when screen is locked. All of
them is up-to-date 15.10, one notebook (intel), one desktop (also
integrated intel stuff onboard), and one another desktop but with
AMD/APU configuration.  I also see wild memory leaking like happenings
on one of the machines at least (others are not used with long enough
uptime to be able to notice, maybe?), eg, according to top, memory usage
of compiz starts from something like 4% but it's 14% after three days of
being locked, it was also 41% after a week or so once ... And yes, CPU
is always at 100% at the momemnt I lock the screen even without power
saving of monitor, etc. On all of those machines. Quite annoying,
because of fan noise, and especially on the notebook, it's not so great
for the battery to have long on battery usage, as you can imagine :(

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

Title:
  Compiz running on Intel Haswell GPU has 100% CPU usage when computer
  is locked

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1322751/+subscriptions

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

[Bug 1516308] Re: Compiz uses 100% CPU when desktop is locked

[LGB [Gábor Lénárt]]

I am not sure if it's related, but another interesting fact: I left my
Ubuntu box switched on at my workplace, though I can access it via ssh
(and sshfs to mount my home from there). It was more than a week, not to
go to work, more than usual. Screen is locked of course. One thing, the
usual: with utilizing ssh I see that compiz process uses about 100% of
the CPU all the time. Other thing: when I went back to work, I realized
that compiz used 41% of the memory ... So there is some memory leak as
well somewhere. Now I see, that I often have to use "nohup compiz
--replace &" from a terminal (since I don't want to lose the state of my
desktop) every several days, since compiz starts to eat simply too much
memory. After such a compiz replacement, it goes back to the "normal"
and usual memory consumption.  As far as I can tell, compiz seems a
disaster for me, both of CPU and memory usage problems all the time, at
total of three different machines I use, so I don't think it's just a
problem at a given setup too much :(

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

Title:
  Compiz uses 100% CPU when desktop is locked

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

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

[Bug 1516308] Re: Compiz uses 100% CPU when desktop is locked

[LGB [Gábor Lénárt]]

Sorry, one more important thing to note: the 100% CPU usage goes almost
instantly after locking screen regardless of "freshly booted" system or
switched on since a week, the memory leaking (what I talked about in my
previous comment) is just another interesting fact which may or may not
be related, I don't know.

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

Title:
  Compiz uses 100% CPU when desktop is locked

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

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

[Bug 1434396] Re: Xserver does not start or freezes with systemd + lightdm

[LGB [Gábor Lénárt]]

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 behaviour if I try to boot multiple times.

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

Title:
  Xserver does not start or freezes with systemd + lightdm

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions

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

[Bug 1516308] [NEW] Compiz uses 100% CPU when desktop is locked

[LGB [Gábor Lénárt]]

Public bug reported:

Tested on three different machines upgraded to Ubuntu 15.10 recently.
All of them are 32 bit systems, two of them are intel based integrated
GPU (on of them is notebook) with intel CPU, and one is AMD APU equipped
machine with the binary driver (so because of this, I don't think it's a
video driver related issue). The problem: I've noticed that after
locking the screen the fan of the notebook starts to produce a louder
noise, typical sign of high CPU usage. After logging in into the machine
via ssh from another one, I found that compiz uses 100% CPU, but after
unlock the CPU usage drops below 1%. Then I noticed the same with two
desktop machines, the same: 100% used CPU by compiz when locked. It's
really annoying since it didn't happen with the previous Ubuntu release,
and it creates significant noise by the fans, and of course - I guess -
using more energy than it should.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Nov 14 21:53:55 2015
DistUpgraded: 2015-10-18 23:18:25,282 INFO cache.commit()
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.4, 4.2.0-17-generic, i686: installed
 virtualbox, 5.0.4, 4.2.0-18-generic, i686: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21dd]
InstallationDate: Installed on 2012-03-03 (1351 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: LENOVO 5016NW6
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet 
splash vt.handoff=7
SourcePackage: compiz
UpgradeStatus: Upgraded to wily on 2015-10-18 (26 days ago)
dmi.bios.date: 11/04/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8GET38WW (1.15 )
dmi.board.name: 5016NW6
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 5016NW6
dmi.product.version: ThinkPad L520
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Fri Nov 13 17:02:38 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id9196 
 vendor AUO
xserver.version: 2:1.17.2-1ubuntu9

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


** Tags: apport-bug compiz-0.9 i386 ubuntu wily

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

Title:
  Compiz uses 100% CPU when desktop is locked

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

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

[Bug 1508219] Re: Possible high CPU usage by firefox while screen is locked

[LGB [Gábor Lénárt]]

I'm sorry but now it *seems* for me, that it's not firefox, but maybe
compiz related (hmmm, or both?), please read the newer bug report of
mine: bug 1516308

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

Title:
  Possible high CPU usage by firefox while screen is locked

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

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

[Bug 1501250] Re: double clicking on a URL drops the protocol from the URL

[LGB [Gábor Lénárt]]

Quite ugly "bug" :( I had the habit "since ages" (ehhh) to work in
terminal windows, and copy URLs etc. It worked nicely with a quick
double click on the URL which does not work anymore after upgrade to
Wily :( I understand that it was not meant to select URLs anyway (and
not a perfect solution either), but in practice it worked reasonably
well.  I've just wanted to write a bug report about this, however
launchpad was intelligent enough to find me a similar already existing
bug report, this one ;)

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

Title:
  double clicking on a URL drops the protocol from the URL

To manage notifications about this bug go to:
https://bugs.launchpad.net/vte/+bug/1501250/+subscriptions

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

[Bug 1508219] [NEW] Possible high CPU usage by firefox while screen is locked

[LGB [Gábor Lénárt]]

Public bug reported:

It's a bit fuzzy report, I have to admit, and more like a feeling, as I
can't check it out too well, but I haven't experienced that in previous
Ubuntu versions before upgrading to Wily.

I have firefox running with many tabs open. The CPU usage (without too
much active pages, ie no videos etc) is about 10-30% at max. If I lock
my computer I always hear the fan of the notebook switches onto a higher
speed, which disappears if I unlock the screen. It's a bit hard to check
it out, if it's really because of firefox, as I can only use "top" if my
desktop is unlocked of course, but I can still notice that CPU usage of
firefox is still about decreasing after unlocking.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: firefox 41.0.2+build2-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic i686
AddonCompatCheckDisabled: False
ApportVersion: 2.19.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lgb2439 F pulseaudio
BuildID: 20151016093451
Channel: Unavailable
CurrentDesktop: Unity
Date: Tue Oct 20 23:48:56 2015
DefaultProfilePlugins:
 IcedTea-Web Plugin (using IcedTea-Web 1.5.2 (1.5.2-1ubuntu2)) - 
/usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so 
(icedtea-7-plugin)
 Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so 
(google-talkplugin)
 iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
 Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
 Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-03-03 (1326 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MostRecentCrashID: bp-c1602958-abcf-49cb-af9c-c95172151003
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1Plugins:
 IcedTea-Web Plugin (using IcedTea-Web 1.5.2 (1.5.2-1ubuntu2)) - 
/usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so 
(icedtea-7-plugin)
 Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
 iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile0 (Default) - LastVersion=41.0.2/20151016093451 (In use)
 Profile1 - LastVersion=39.0a2/20150414004003 (Out of date)
RelatedPackageVersions:
 icedtea-7-plugin  1.5.2-1ubuntu2
 google-talkplugin 5.41.0.0-1
 rhythmbox-mozilla 3.2.1-1ubuntu3
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to wily on 2015-10-18 (2 days ago)
dmi.bios.date: 11/04/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8GET38WW (1.15 )
dmi.board.name: 5016NW6
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 5016NW6
dmi.product.version: ThinkPad L520
dmi.sys.vendor: LENOVO

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


** Tags: apport-bug i386 wily

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

Title:
  Possible high CPU usage by firefox while screen is locked

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

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

[Bug 1504435] Re: Cisco VPN does not work (connection hangs through vpnc) after upgaded to wily

[LGB [Gábor Lénárt]]

Some tests:

Part of the output of command "ip link" :

On a 15.04 system, after connecting to the VPNC, it works nicely,
without any workaround:

tun0:  mtu 1412 qdisc
pfifo_fast state UNKNOWN mode DEFAULT group default qlen 500

After connecting to VPNC on a machine upgraded to wily, it does NOT
work:

tun0:  mtu 1500 qdisc
pfifo_fast state UNKNOWN mode DEFAULT group default qlen 500

Entering command "ip li set mtu 1412 dev tun0" after the VPNC connection
on a machine upgraded to wily, now it works:

tun0:  mtu 1412 qdisc
pfifo_fast state UNKNOWN mode DEFAULT group default qlen 500

Thus, it seems, for some reason, 1412 MTU is set in pre-wily systems
when connected to vpnc, while it's not the case with wily, and needs a
manual workaround?

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

Title:
  Cisco VPN does not work (connection hangs through vpnc) after upgaded
  to wily

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

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

[Bug 1504435] [NEW] Cisco VPN does not work (connection hangs through vpnc) after upgaded to wily

[LGB [Gábor Lénárt]]

Public bug reported:

I've used the same vpnc config (set up with network manager) since
years, without issues. After upgraded to wily, it does not work anymore
though. The VPN connection itself is established, however opening a web
page just stalls. Using ssh through the VPN connection also work, but eg
givin an 'ls' command hangs after some lines and the connection freezes.
It seems, more than a few bytes sent through a connection over VPN
hangs. I've tried to turn TCP ECN and window scaling (through the /proc
interface) off, since in my experience, it caused problems with old
firewalls etc. However it did not helped either with my current issue.

Using tcpdump to capture the network traffic (on interface tun0, I
inspected the cap file with wireshark then) indicated "TCP Dup  ACK" and
"Server: TCP Previous segment not captured" and similar messages. The
firewall behind the vpn termination is also Linux, it reported invalid
state packets (so the connection tracking information is not NEW,
ESTABLISHED or RELATED, but INVALID, which is dropped by the global
policy, and I can't change that because of company level firewall
policy).

>From my experience I have the suspect that it can be some kind of MTU
issue (my usual "hang on traffic" reaction is the checklist: TCP ecn,
window scaling, banned related icmp messages, and the MTU issues),
though it didn't required any "manual tuning" before previous ubuntu
versions, and also I am not sure where I should modify something, what
what it is ...

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: vpnc 0.5.3r550-2
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic i686
ApportVersion: 2.19.1-0ubuntu2
Architecture: i386
CurrentDesktop: Unity
Date: Fri Oct  9 10:03:21 2015
InstallationDate: Installed on 2014-05-08 (519 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
SourcePackage: vpnc
UpgradeStatus: Upgraded to wily on 2015-10-08 (0 days ago)
modified.conffile..etc.vpnc.default.conf: [deleted]

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


** Tags: apport-bug i386 wily

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

Title:
  Cisco VPN does not work (connection hangs through vpnc) after upgaded
  to wily

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

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

[Bug 1504435] Re: Cisco VPN does not work (connection hangs through vpnc) after upgaded to wily

[LGB [Gábor Lénárt]]

It seems to be an MTU problem, indeed, as after this command:

ip li set mtu 1200 dev tun0

everything works again! I am just curious now: no modification on the
VPN terminator/network/everything, the change was only at my side to
upgrade to wily, and it worked out-of-the-box, without any workaround
(like the command above) before the upgrade.

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

Title:
  Cisco VPN does not work (connection hangs through vpnc) after upgaded
  to wily

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

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

[Bug 1488336] Re: authentication failed

[LGB [Gábor Lénárt]]

The mentioned patch by Joe Clifford (joeclifford) seems to be OK. I've
downloaded source of pidgin-sipe (with apt-get source), also I applied
the patch. After building a deb package and installing everything worked
again with Ubuntu 15.04 (32 bit).

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

Title:
  authentication failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pidgin-sipe/+bug/1488336/+subscriptions

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

[Bug 1488336] Re: authentication failed

[LGB [Gábor Lénárt]]

Indeed, I have the same problem with Ubuntu 15.04

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

Title:
  authentication failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pidgin-sipe/+bug/1488336/+subscriptions

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

[Bug 1434396] Re: Xserver does not start on freezes with systemd + lightdm

[LGB [Gábor Lénárt]]

** 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 bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434396

Title:
  Xserver does not start or freezes with systemd + lightdm

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions

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

[Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)

[LGB [Gábor Lénárt]]

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 be used (ie to type my password to be able to log
in). I use the system with upstart to work the problem around, but of
course it would be better to forget those workarounds ...

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

Title:
  Xserver does not start on boot (low-graphics mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions

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

[Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)

[LGB [Gábor Lénárt]]

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 is about some
kind of VT activation problem, can it be because some race condition on
using VTs or such? Since systemd may do deeper parallelism on the boot
process than upstart (I am not sure just guessing) or at least it did it
not the very same way, it can explain why it works with upstart but not
with systemd.

But really, I am just guessing, and trying to give hints, as release
data for vivid is coming and this bug still exists rendering ubuntu
totally unusable for normal users on some hardware like some thinkpad
notebooks which are not so rare, I think.

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

Title:
  Xserver does not start on boot (low-graphics mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions

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

[Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)

[LGB [Gábor Lénárt]]

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 don't. I'll check both cases out soon.

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

Title:
  Xserver does not start on boot (low-graphics mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions

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

[Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)

[LGB [Gábor Lénárt]]

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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434396

Title:
  Xserver does not start on boot (low-graphics mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions

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

[Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)

[LGB [Gábor Lénárt]]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434396

Title:
  Xserver does not start on boot (low-graphics mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions

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

[Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)

[LGB [Gábor Lénárt]]

@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 ...

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

Title:
  Xserver does not start on boot (low-graphics mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions

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

[Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)

[LGB [Gábor Lénárt]]

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 the system is simply not usable with systemd).

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

Title:
  Xserver does not start on boot (low-graphics mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions

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

[Bug 1340964] Re: Xorg crashed with SIGABRT in _XSERVTransClose()

[LGB [Gábor Lénárt]]

I have this bug only with systemd, choosing upstart everything is OK,
again please read my comment at bug 1434396

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

Title:
  Xorg crashed with SIGABRT in _XSERVTransClose()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1340964/+subscriptions

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

[Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)

[LGB [Gábor Lénárt]]

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 num lock led etc). Though sysreq magic key combos
seem to work. The only option now is to choose upstart from grub. Then
system boots without any problem (not even need to exit console etc) as
it should be. Again apport wanted to report Xorg crash after a reboot
with upstart, but again, bug 1340964 is referenced. It seems nothing bad
happens with upstart, only systemd though.

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

Title:
  Xserver does not start on boot (low-graphics mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions

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

[Bug 1340964] Re: Xorg crashed with SIGABRT in _XSERVTransClose()

[LGB [Gábor Lénárt]]

I have a problem described in bug 1434396 that is: Xserver does not
start on boot, and the low graphics mode dialog is presented instead,
though if I exit to console and start lightdm service by hand it
works. After logging in, bug report dialog on X crash appears and that
brings me to this report.

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

Title:
  Xorg crashed with SIGABRT in _XSERVTransClose()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1340964/+subscriptions

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

[Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)

[LGB [Gábor Lénárt]]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434396

Title:
  Xserver does not start on boot (low-graphics mode)

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

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