[Bug 1750146] Re: Xbox (One) Wireless Controller won't connect

[Alexis Salin]

Hello, can you add drivers for the Xbox controller? It's one of the most
used controllers on PC and it's annoying because xpadneo disables secure
boot.

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

Title:
  Xbox (One) Wireless Controller won't connect

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


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

[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen

[Alexis Scheuer]

Hi!
After all, I am lucky: my Dell Latitude 5480 succeeds sometimes to start 
XUbuntu 18.04.6 LTS normally, but often freezes on boot because "A start job is 
running for ..." (several messages of this type), both with 
linux-image-4.15.0-177-generic and linux-image-4.15.0-180-generic, while 
everything goes fine with linux-image-4.15.0-166-generic (which I installed 
back).
I will give a try with 176.

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

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

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


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

[Bug 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570

[Alexis Scheuer]

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

Hi!
After all, I am lucky: my Dell Latitude 5480 succeeds sometimes to start 
XUbuntu 18.04.6 LTS normally, but often freezes on boot because "A start job is 
running for ..." (several messages of this type), both with 
linux-image-4.15.0-177-generic and linux-image-4.15.0-180-generic, while 
everything goes fine with linux-image-4.15.0-166-generic (which I installed 
back).
I will give a try with 176.

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

Title:
  kernel 4.15.0.177 break everything on Dell XPS 15 9570

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


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

[Bug 1953224] Re: Please sync auto-multiple-choice from Debian sid main (1.5.2-1)

[Alexis Bienvenüe]

Thanks for heading me to the right direction!

** Summary changed:

- Ubuntu patch can be dropped
+ Please sync auto-multiple-choice from Debian sid main (1.5.2-1)

** Description changed:

  Dear Maintainers,
  
- This is not really a bug but a simplification suggestion.
+ I think the package auto-multiple-choice can be synced from Debian sid.
  
- As far as I understand the Ubuntu patch for auto-multiple-choice in 
auto-multiple-choice 1.5.1-2ubuntu1, it can be dropped since debian version 
1.5.1-2.
+ There is only one Ubuntu patch for this package, that adds a dependency to 
+ adwaita-icon-theme-full
+ 
+ As far as I understand this patch, it can be dropped since debian version 
1.5.1-2.
  Indeed, the dependency to gnome-icon-theme-symbolic has been added, that is 
provided by adwaita-icon-theme-full in Ubuntu.
  See 
https://salsa.debian.org/georgesk/auto-multiple-choice/-/commit/6dc909f87e55449e
  
  Regards,
  Alexis Bienvenüe.

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

Title:
  Please sync auto-multiple-choice from Debian sid main (1.5.2-1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/auto-multiple-choice/+bug/1953224/+subscriptions


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

[Bug 1953224] [NEW] Ubuntu patch can be dropped

[Alexis Bienvenüe]

Public bug reported:

Dear Maintainers,

This is not really a bug but a simplification suggestion.

As far as I understand the Ubuntu patch for auto-multiple-choice in 
auto-multiple-choice 1.5.1-2ubuntu1, it can be dropped since debian version 
1.5.1-2.
Indeed, the dependency to gnome-icon-theme-symbolic has been added, that is 
provided by adwaita-icon-theme-full in Ubuntu.
See 
https://salsa.debian.org/georgesk/auto-multiple-choice/-/commit/6dc909f87e55449e

Regards,
Alexis Bienvenüe.

** Affects: auto-multiple-choice (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/1953224

Title:
  Ubuntu patch can be dropped

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/auto-multiple-choice/+bug/1953224/+subscriptions


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

[Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault

[Alexis Lecocq]

Hello,

I also found my Nginx server down after several hours. Nowadays
certificates have short life time, their issuance is automated and the
reloading of the servers is mandatory to update the certificates. In
short, an automated action is making the web server crash. In my
opinion, the importance of this bug is very high. This seems to be a
patch for 5.30.2
https://github.com/Perl/perl5/issues/17154#issuecomment-638452287

Kind regards,

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

Title:
  libperl.so.5.30.0 causes nginx to segfault

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


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

[Bug 1928332] Re: updated to 1.5.0~rc2-2ubuntu1 after updating to ubuntu 21.04. Getting error "command \csvloop already defined". Works on previous versions (1.4.0-5ubuntu1).

[Alexis Bienvenüe]

** Changed in: auto-multiple-choice (Ubuntu)
   Status: New => Incomplete

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

Title:
  updated to 1.5.0~rc2-2ubuntu1 after updating to ubuntu 21.04. Getting
  error "command \csvloop already defined". Works on previous versions
  (1.4.0-5ubuntu1).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/auto-multiple-choice/+bug/1928332/+subscriptions


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

[Bug 1944737] [NEW] package linux-modules-extra-5.11.0-36-generic (not installed) failed to install/upgrade: no se puede abrir `/lib/modules/5.11.0-36-generic/kernel/drivers/net/wireless/intel/iwlwifi

[Alexis]

Public bug reported:

no arranca el sistema operativo

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-modules-extra-5.11.0-36-generic (not installed)
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.11-0ubuntu27.20
AptOrdering:
 linux-modules-extra-5.11.0-36-generic:amd64: Install
 linux-hwe-5.11-headers-5.11.0-36:amd64: Install
 linux-headers-5.11.0-36-generic:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Sep 22 14:56:39 2021
DpkgTerminalLog:
 Preparando para desempaquetar 
.../linux-modules-extra-5.11.0-36-generic_5.11.0-36.40~20.04.1_amd64.deb ...
 Desempaquetando linux-modules-extra-5.11.0-36-generic (5.11.0-36.40~20.04.1) 
...
 dpkg: error al procesar el archivo 
/var/cache/apt/archives/linux-modules-extra-5.11.0-36-generic_5.11.0-36.40~20.04.1_amd64.deb
 (--unpack):
  no se puede abrir 
`/lib/modules/5.11.0-36-generic/kernel/drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko.dpkg-new':
 Operación no permitida
ErrorMessage: no se puede abrir 
`/lib/modules/5.11.0-36-generic/kernel/drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko.dpkg-new':
 Operación no permitida
InstallationDate: Installed on 2021-09-16 (7 days ago)
InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: linux-hwe-5.11
Title: package linux-modules-extra-5.11.0-36-generic (not installed) failed to 
install/upgrade: no se puede abrir 
`/lib/modules/5.11.0-36-generic/kernel/drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko.dpkg-new':
 Operación no permitida
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-hwe-5.11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package linux-modules-extra-5.11.0-36-generic (not installed) failed
  to install/upgrade: no se puede abrir
  
`/lib/modules/5.11.0-36-generic/kernel/drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko.dpkg-
  new': Operación no permitida

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


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

[Bug 1928332] Re: updated to 1.5.0~rc2-2ubuntu1 after updating to ubuntu 21.04. Getting error "command \csvloop already defined". Works on previous versions (1.4.0-5ubuntu1).

[Alexis Bienvenüe]

Thank you for your report. Can you explain in detail which tex file you
tried to compile? Can you post the whole log file that shows the errors?
Thanks!

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

Title:
  updated to 1.5.0~rc2-2ubuntu1 after updating to ubuntu 21.04. Getting
  error "command \csvloop already defined". Works on previous versions
  (1.4.0-5ubuntu1).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/auto-multiple-choice/+bug/1928332/+subscriptions


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

[Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[RICARDO ALEXIS RESTREPO RENGIFO]

Hello I am richard618921. I need to solve the error message debconf:
DbDriver "config": /var/cache/debconf/config.dat is locked by another
process: Resource temporarily unavailable. What can I do ???

** Changed in: aptdaemon
 Assignee: (unassigned) => RICARDO ALEXIS RESTREPO RENGIFO (richard618921)

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Bug 1915833] [NEW] package libnvidia-common-450 450.102.04-0ubuntu0.20.04.1 failed to install/upgrade: intentando sobreescribir `/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documenta

[Alexis Neira G]

Public bug reported:

Nividia integrated card GeForce 6150 SE

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libnvidia-common-450 450.102.04-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Feb 15 14:16:34 2021
Dependencies:
 
ErrorMessage: intentando sobreescribir 
`/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', 
que está también en el paquete libnvidia-common-450-server 
450.102.04-0ubuntu0.20.04.1
InstallationDate: Installed on 2021-02-07 (8 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: nvidia-graphics-drivers-450
Title: package libnvidia-common-450 450.102.04-0ubuntu0.20.04.1 failed to 
install/upgrade: intentando sobreescribir 
`/usr/share/nvidia/nvidia-application-profiles-450.102.04-key-documentation', 
que está también en el paquete libnvidia-common-450-server 
450.102.04-0ubuntu0.20.04.1
UpgradeStatus: Upgraded to focal on 2021-02-15 (1 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package libnvidia-common-450 450.102.04-0ubuntu0.20.04.1 failed to
  install/upgrade: intentando sobreescribir `/usr/share/nvidia/nvidia-
  application-profiles-450.102.04-key-documentation', que está también
  en el paquete libnvidia-common-450-server 450.102.04-0ubuntu0.20.04.1

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

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

[Bug 1902385] [NEW] At times I have an app. menu that opens and never closes

[Alexis Wilke]

Public bug reported:

It has happened twice in the last little bit where I opened a menu on an
icon in the dock and the menu remains opened "forever" (until next
reboot).

Opening other menus from other icons in the dock works as expected.

In most cases, the menu that's stuck is "transparent" to clicks, that
is, when I try to click a menu item, the thing behind the menu gets
clicked.

When I'm able to click on an item in the menu (it turns orange when I do
that successfully) then the mouse pointer is stuck over that item and
that's it... nothing happens. Using Cmd-Tab to switch between windows
waken the mouse up so I could use it again.

I tried to restart the GDM3, the dock & menu came back as it was before
the restart.

sudo systemctl restart display-manager

I tried once to Log Out (instead of rebooting) and the graphical
interface didn't come back. I tried to restart the GDM from another
computer (remotely through SSH) and the screen flashed a bit but it went
right back to the boot console. So in other words the Log Out failed.
Probably waiting on something that has a deadlock?

The only way I've found to fix the issue is to reboot the computer
(which I do not like to do too much... plus it takes about 3 min. with
my monster server).

See also: https://askubuntu.com/questions/1288577/ubuntu-18-04-icon-
menu-gets-stuck-open-any-way-to-fix-that-without-having-to

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3
ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
Uname: Linux 4.15.0-122-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 31 12:09:43 2020
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic uec-images

** Attachment added: "Sample of menu that was stuck earlier."
   
https://bugs.launchpad.net/bugs/1902385/+attachment/5429843/+files/menu-stuck.png

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

Title:
  At times I have an app. menu that opens and never closes

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

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

[Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[Alexis Clairet]

Yep, I know that... the fact is the "bug" is here for a long time and
apparently it's not going to be resolved soon without the help of Asus.
This thread is linked every time someone on the internet ask for help
with there laptop so my idea was to investigate the hack/software
solution instead of waiting for a proper hardware one.

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

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

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

[Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[Alexis Clairet]

Hi, I've got a vivobook X412D and I found this on stackoverflow:
https://gitlab.com/Thraen/gx735_touchpad_numpad/ .
It's not a driver but with a little tweaks in a minute, I managed to get numpad 
inputs (without leds on and by plugin a usb keyboard). 
When "Num lock" on the usb keyboard is enabled I get correct values.

So my plan is to trigger "num lock" with a keyboard shortcut or special
hot key (i don't know how) and find a way to enable the backlight
leds... (I don't know how)

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

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

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

[Bug 1883295] [NEW] Xorg freeze

[Alexis]

Public bug reported:

freeze on show applications menu.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 12 11:34:08 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 605 [17aa:39fd]
InstallationDate: Installed on 2020-06-12 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:112b Acer, Inc EasyCamera
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81J2
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=8dc8d3e5-254c-4aea-8f07-294a527b810c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: 9HCN26WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32823WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad S130-14IGM
dmi.modalias: 
dmi:bvnLENOVO:bvr9HCN26WW:bd07/09/2019:svnLENOVO:pn81J2:pvrLenovoideapadS130-14IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32823WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-14IGM:
dmi.product.family: ideapad S130-14IGM
dmi.product.name: 81J2
dmi.product.sku: LENOVO_MT_81J2_BU_idea_FM_ideapad S130-14IGM
dmi.product.version: Lenovo ideapad S130-14IGM
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze ubuntu

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

Title:
  Xorg freeze

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

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

[Bug 1815060] Re: Traceback closing tab with changes

[Alexis Wilke]

For those interested in 18.04, the file to replace is:

/usr/lib/python3/dist-packages/meld/filediff.py

and you can replace it with the version:

https://gitlab.gnome.org/GNOME/meld/-/blob/3.18.2/meld/filediff.py

Then saving when closing the tab works as expected.

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

Title:
  Traceback closing tab with changes

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

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

[Bug 1768369] Re: Tabs don't close after saving changes

[Alexis Wilke]

For those interested in 18.04, the file to replace is:

/usr/lib/python3/dist-packages/meld/filediff.py

and you can replace it with the version:

https://gitlab.gnome.org/GNOME/meld/-/blob/3.18.2/meld/filediff.py

Then saving when closing the tab works as expected.

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

Title:
  Tabs don't close after saving changes

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

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

[Bug 1768369] Re: Tabs don't close after saving changes

[Alexis Wilke]

For those interested in 18.04, the file to replace is:

/usr/lib/python3/dist-packages/meld/filediff.py

and you can replace it with the version:

https://gitlab.gnome.org/GNOME/meld/-/blob/3.18.2/meld/filediff.py

Then saving when closing the tab works as expected.

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

Title:
  Tabs don't close after saving changes

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

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

[Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04

[Alexis Dinno]

I had the on Ubuntu 19.10 (and have it still on Ubuntu 20.04). I agree
that I see it more frequently in LibreOffice Writer, but I see it
elsewhere. Unstable clipboard behavior is unhappy making.

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Bug 1860446] [NEW] man gives wrong information in case of undocumented

[Alexis]

Public bug reported:

When trying to access an undocumented help, the help proposes to use
"man 7 undocumented". Yet this page does not exist on my machine. Base
installation of Ubuntu 18.04.


```
alexis@Oreo:~$ man 2 printf
No manual entry for printf in section 2
See 'man 7 undocumented' for help when manual pages are not available.
alexis@Oreo:~$ man 7 undocumented
No manual entry for undocumented in section 7
```

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: manpages 4.15-1
ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 21 15:59:19 2020
Dependencies:
 
InstallationDate: Installed on 2019-08-22 (152 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
SourcePackage: manpages
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug bionic manpage

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

Title:
  man gives wrong information in case of undocumented

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

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

[Bug 1856867] [NEW] When i update my linux kernel my touch pad doesn't work

[hermes alexis]

Public bug reported:

I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0003 Version=
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=4000 0 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
U: Uniq=
H: Handlers=kbd event3 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input4
U: Uniq=
H: Handlers=sysrq kbd event4 leds 
B: PROP=0
B: EV=120013
B: KEY=1100f02902000 8380307cf910f001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0018 Vendor=06cb Product=78f1 Version=0100
N: Name="Synaptics TM3096-001"
P: Phys=i2c-DLL06B0:00
S: 
Sysfs=/devices/pci:00/INT3433:00/i2c-1/i2c-DLL06B0:00/0018:06CB:78F1.0001/input/input7
U: Uniq=
H: Handlers=mouse0 event5 
B: PROP=5
B: EV=b
B: KEY=e520 1 0 0 0 0
B: ABS=6f38103

I: Bus=0019 Vendor= Product= Version=
N: Name="DELL Wireless hotkeys"
P: Phys=dellabce/input0
S: Sysfs=/devices/virtual/input/input8
U: Uniq=
H: Handlers=rfkill kbd event6 
B: PROP=0
B: EV=3
B: KEY=80 0 0 0

I: Bus=0003 Vendor=0c45 Product=6710 Version=5504
N: Name="Integrated_Webcam_HD: Integrate"
P: Phys=usb-:00:14.0-5/button
S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-5/2-5:1.0/input/input9
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus=0019 Vendor= Product= Version=
N: Name="Dell WMI hotkeys"
P: Phys=
S: 
Sysfs=/devices/platform/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input10
U: Uniq=
H: Handlers=rfkill kbd event8 
B: PROP=0
B: EV=13
B: KEY=8000 0 0 101500b0c00 20030 e 0
B: MSC=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Headphone Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input11
U: Uniq=
H: Handlers=event9 
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0019 Vendor= Product=0006 Version=
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
U: Uniq=
H: Handlers=kbd event10 
B: PROP=0
B: EV=3
B: KEY=3e000b 0 0 0

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel HDMI HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input13
U: Uniq=
H: Handlers=event11 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel HDMI HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input14
U: Uniq=
H: Handlers=event12 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel HDMI HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input15
U: Uniq=
H: Handlers=event13 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel HDMI HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input16
U: Uniq=
H: Handlers=event14 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel HDMI HDMI/DP,pcm=10"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input17
U: Uniq=
H: Handlers=event15 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0003 Vendor=1c4f Product=0034 Version=0110
N: Name="SIGMACHIP Usb Mouse"
P: Phys=usb-:00:14.0-2/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/0003:1C4F:0034.0003/input/input23
U: Uniq=
H: Handlers=mouse1 event16 
B: PROP=0
B: EV=17
B: KEY=7 0 0 0 0
B: REL=103
B: MSC=10

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-72-generic 4.15.0-72.81
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hermes 3066 F pulseaudio
 /dev/snd/controlC1:  hermes 3066 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 18 11:45:58 2019
HibernationDevice: RESUME=UUID=8ebd4080-f73f-4eee-8e6b-5d3837e0f977
InstallationDate: Installed on 2018-12-27 (356 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - 

[Bug 1855489] Re: Chromium auto-restart feature breaks many features

[Alexis Wilke]

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

Okay, another updated happened today (version 79.0.3945.79) and I can
confirm that it creates the issue where I lose the dot under the Gnome
icon. So bug $1616650 definitely looks like the solution to this
problem. Thank you.

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

Title:
  Chromium auto-restart feature breaks many features

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855489/+subscriptions

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

[Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME

[Alexis Dinno]

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

Me too.

CPU: Intel(R) Xeon(R) E-2176M  2.70GHz
Ubuntu 19.10
GPU: Nvidi Quadro P4200

|===+==+==|
|   0  Quadro P4200 wi...  Off  | :01:00.0 Off |  N/A |
| N/A   52CP029W /  N/A |   1206MiB /  8119MiB |  4%  Default |
+---+--+--+
   
+-+
| Processes:   GPU Memory |
|  GPU   PID   Type   Process name Usage  |
|=|
|0  1240  G   /usr/lib/xorg/Xorg   142MiB |
|0  1974  G   /usr/lib/xorg/Xorg   416MiB |
|0  2225  G   /usr/bin/gnome-shell 514MiB |
|0  2477  G   evolution 75MiB |
+-+

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

Title:
  Resuming from sleep breaks desktop and lock screen background in GNOME

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

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

[Bug 1855489] Re: Chromium auto-restart feature breaks many features

[Alexis Wilke]

Well, I can't really confirm whether it is a refresh (which I called
auto-restart) after an auto-update or a an actual crash... but for sure
the window does not change yet it gets disconnected from the Gnome
Desktop (and that has happened many times now). At least I'll post to
confirm that the history fails next time that happens and I'll check the
versions to see whether it happens when an upgrade happens.

However, the problem doesn't look like bug #1616650 in terms of
functionality, the tabs all remain in place and work just fine without
having to restart for many days after it gets disconnected from Gnome.
That being said, the read-only folder (point 2) sounds like that could
be part of the issue. I'm also not so sure that there was an update.
I'll now pay attention to the exact version and see whether it changes
next time the dot under the icon disappear.

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

Title:
  Chromium auto-restart feature breaks many features

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855489/+subscriptions

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

[Bug 1855489] [NEW] Chromium auto-restart feature breaks many features

[Alexis Wilke]

Public bug reported:

Once in a while, Chromium "auto-restarts" to take advantage of new
features and especially apply security patches. This sounds like a great
feature only it currently has very bad repercussions (as in, it's
terribly bogus).

Steps to reproduce:

1. start Chromium
2. browse to various pages
3. let the app. sit there until it auto-restarts
4. from this point on, the app. is bogus, it's not able to save many different 
things
5. restarting the app. will not see all changes you make between step 3 and 5 
(see below)

Note that the duration of the session is probably not an issue in
itself. I think only the auto-restart feature is what causes all the
other issues.

The features I've noticed that broke completely after such a restart:

(1) Gnome Icon

The small arrow in the Chromium Icon from my Gnome toolbar (the bar
which by default is on the left side of the screen) disappears. That in
itself is not the end of the world except that this means I can't click
the icon to go back to my window. Clicking the icon opens a new
instance.

To fix this problem, you would have to run an additional binary. The
first binary has to remain in place to hold the icon as expected.
Without doing that, you lose the connection to Gnome. There may be other
methods to do that. It may also be because you close the old connection
to X-Windows and Gnome views that as "now you're gone". Either way, this
is not too important to me and it's not a big bad bug in itself.

(2) Trying to Install Extensions generates: "Could not create download
directory"

As such, this error doesn't sound too bad. You should be able to tweak
your directory and make sure that it's writable. The fact is that my
download directory was just fine. However, it looks like Chrome doesn't
think it is.

My take is that Chrome has a form of lock and the old lock is still in
place making it impossible for new version to access the folders that
are locked.

This is rather bad since many functionalities may be affected by this.
I've only noticed the problem with downloading extensions, but it is not
unlikely that other features are also affected in a similar manner.

(3) Changing Settings

As I was in that situation, I thought I would change my "On Startup"
settings so that I could get my windows back on a restart. That way the
restart is mostly transparent. Oh but...

The changes to the settings did not take; while still using Chromium it
looked like it was properly changed, but it was not auto-saved as it
ought to be. I am thinking that a similar lock (as mentioned in the
previous section) is still in place and it prevents the settings from
being saved.

(4) Non-Existent History

After my restart, the windows did not come back. That is, I only got two
windows from a while back... Not the newest windows as I would expect.
(i.e. all the windows at the time I last closed the browser).

So I decided to check out the history. Nothing. I could only see history
from many days ago. Again, my take is that when we had that background
auto-restart of Chromium, it was not able to access the history file. It
kept the history in memory and never told anyone it couldn't save it
anywhere. (Maybe the logs are also affected... I've not checked. But
that could explain why developers did not notice and I would imagine
that developers open/close the app. all the time).

I think this is the worst one. I like to have my history so I can go
back to pages where I have been in the past. I don't always use it, but
in this very situation I was interested by one specific page and the
link is gone.

-

Note 1: I'm on Ubuntu 18.04 using the Chromium snap version
78.0.3904.108 (64 bit).

Note 2: I insist that changing the Download folder had no effects.
That's not the issue in this case. Also, I could download files and they
would go in my ~/Downloads folder as expected. No problem on that one.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: auto-restart

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

Title:
  Chromium auto-restart feature breaks many features

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855489/+subscriptions

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

[Bug 1079190] Re: gnome-control-center keyboard shortcuts does not manage keyboard power button keybindings properly

[Alexis Wilke]

I got here because of a question asked on the Ubuntu stack here:

https://askubuntu.com/questions/115333/how-do-i-disable-the-sleep-
button-on-my-keyboard

My keyboard Sleep button is right next to the Esc key. It's just too
close and way to easy to end up clicking on it. It would be nicer to
have the keys in the usual Keyboard Shortcuts window. It sounds like
this should be an easy one since it's very much the same as the other
keys... right?

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

Title:
  gnome-control-center keyboard shortcuts does not manage keyboard power
  button keybindings properly

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

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

[Bug 1281758] Re: re-installing maas-region-controller fails

[Alexis Rodriguez]

I ran into this issue today as well.  Performing the following can
recreate the issue on Ubuntu 18.04.3 LTS:

$ sudo apt remove maas
$ sudo apt remove autoremove
$ sudo apt install maas

This was fixed by the previous suggestion:

$ sudo apt autoremove --purge maas
$ sudo apt install maas

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

Title:
  re-installing maas-region-controller fails

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

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

[Bug 1829735] Re: Fresh install of 18.10 stuck at initializing ramdisk after sudo apt upgrade

[Alexis Trinquet]

I ran into the same issue on a fresh install of 18.04. Before
downloading the updates I could boot just fine but now I always get
stuck on a purple screen.

However there is a catch, my system uses a AMD CPU (Athlon II X2 245)

If I boot into recovery mode, a bunch of text passes by (so fast that I
can't read it) before getting stuck on [SDG] Attached SCSI disk

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

Title:
  Fresh install of 18.10 stuck at initializing ramdisk after sudo apt
  upgrade

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

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

[Bug 1814261] Re: gpm prevents loging to the console: spurious “Enter” events seems inserted

[Alexis Wilke]

I rebooted on Ubuntu 16.04 (4.4.0-142-generic) and it worked as expected
once gpm was turned off.

I used the following command to prevent gpm from starting on a reboot
and messing up the login screen:

sudo systemctl mask gpm

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

Title:
  gpm prevents loging to the console: spurious “Enter” events seems
  inserted

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

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

[Bug 1814261] Re: gpm prevents loging to the console: spurious “Enter” events seems inserted

[Alexis Wilke]

I have the exact same problem on Ubuntu 16.04
(vmlinuz-4.4.0-142-generic).

I will try to turn off GPM and see how my console functions without it.

What a surprise though! Not being able to log in the simplest console.
Not something I've seen in ages...

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

Title:
  gpm prevents loging to the console: spurious “Enter” events seems
  inserted

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

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

[Bug 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

[Alexis Dinno]

** Attachment added: "Output of cat /sys/bus/serio/devices/serio1/firmware_id"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+attachment/5226759/+files/output.txt

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

Title:
  Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

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

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

[Bug 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

[Alexis Dinno]

@kaihengfeng Your suggestion did the trick! I had tried a similar
parameter I found elsewhere on the web (I *think* it was something like
'psmouse.elantech=0') to no avail.

Thank you Kai-Heng Feng!

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

Title:
  Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

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

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

[Bug 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

[Alexis Dinno]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+attachment/5222375/+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/1808588

Title:
  Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

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

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

[Bug 1808588] [NEW] Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

[Alexis Dinno]

Public bug reported:

I upgraded my Ubuntu from Bionic Beaver to Cosmic Cuttlefish on my
laptop. The installation process seemed to go well, but on reboot my
trackpad and trackpoint no longer move the pointer, register taps or
click buttons, and are seemingly unrecognized by the system.

General information:
Laptop make/model: Lenovo Thinkpad P72 TYPE 20MB-CT01WW 18/11  (that might be a 
'O' rather than an '0' on the sticker)
Touchpad maufacturer: (Lenovo?) UltraNav TrackPoint
When symptoms first appeared: On first reboot after the change to Cosmic. Also 
on subsequent reboots and waking from sleep and suspend.


No trackpad device is listed in /proc/bus/input/devices.


The trackpad and trackpoint and buttons work if I boot into another OS.

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


** Tags: cosmic

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/1808588/+attachment/5222374/+files/version.log

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

Title:
  Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

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

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

[Bug 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

[Alexis Dinno]

** Attachment added: "devices"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+attachment/5222377/+files/devices

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

Title:
  Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

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

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

[Bug 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

[Alexis Dinno]

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+attachment/5222376/+files/dmesg

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

Title:
  Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

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

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

[Bug 1799859] Re: "pbuilder-dist create xenial" fails (Unutu 16.04) since Oct 17, 2018

[Alexis Wilke]

As Pete mentioned, the "wrong" version comes from the proposed version.
We can see the list is here:

https://www.ubuntuupdates.org/package/core/xenial/main/proposed/gcc-5

The following is the table with the versions.

- Other versions of "gcc-5" in Xenial

RepositoryAreaVersion
=====
base  universe5.3.1-14ubuntu2
base  main5.3.1-14ubuntu2
security  main5.4.0-6ubuntu1~16.04.10
security  universe5.4.0-6ubuntu1~16.04.10
updates   universe5.4.0-6ubuntu1~16.04.10
updates   main5.4.0-6ubuntu1~16.04.10
proposed  universe5.4.0-6ubuntu1~16.04.11
PPA: Canonical Kernel Team5.4.0-6ubuntu1~16.04.9

What I don't understand is why that error still happens even though the
list of sources does not even include the "proposed" archive.

root@build:/# cat /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu xenial-security main
deb http://archive.ubuntu.com/ubuntu xenial-updates main
deb http://archive.ubuntu.com/ubuntu xenial main restricted
#deb-src http://archive.ubuntu.com/ubuntu xenial main restricted
root@build:/# ls /etc/apt/sources.list.d/
root@build:/# 

Looking at the policy for gcc-5 I get the following:

root@build:/# apt policy gcc-5
gcc-5:
  Installed: 5.4.0-6ubuntu1~16.04.11
  Candidate: 5.4.0-6ubuntu1~16.04.11
  Version table:
 *** 5.4.0-6ubuntu1~16.04.11 100
100 /var/lib/dpkg/status
 5.4.0-6ubuntu1~16.04.10 500
500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 5.3.1-14ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

And effectively when I look at the list of installed gcc-5 packages I
see that it's the proposed  version...

root@build:/# dpkg -l | grep gcc-5
ii  gcc-5  5.4.0-6ubuntu1~16.04.11   amd64  
  GNU C compiler
ii  gcc-5-base:amd64   5.4.0-6ubuntu1~16.04.11   amd64  
  GCC, the GNU Compiler Collection (base package)
ii  libgcc-5-dev:amd64 5.4.0-6ubuntu1~16.04.11   amd64  
  GCC support library (development files)

Forcing the installation of version 5.4.0-6ubuntu1~16.04.10 doesn't
help. Next time I try a build, I get the same version errors (as shown
above.)

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

Title:
  "pbuilder-dist create xenial" fails (Unutu 16.04) since Oct 17, 2018

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1799859/+subscriptions

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

[Bug 1799859] Re: "pbuilder-dist create xenial" fails (Unutu 16.04) since Oct 17, 2018

[Alexis Wilke]

Well... the creation of the environment worked with "--updates-only".

However, my build requires a few things, one of which is libexpart1-dev
and that still fails:

The following packages have unmet dependencies:
 libexpat1-dev : Depends: libexpat1 (= 2.1.0-7) but 2.1.0-7ubuntu0.16.04.3 is 
to be installed
E: Unable to correct problems, you have held broken packages.

So it's not a work around as far as my build is concerned.

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

Title:
  "pbuilder-dist create xenial" fails (Unutu 16.04) since Oct 17, 2018

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1799859/+subscriptions

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

[Bug 1799859] Re: "pbuilder-dist create xenial" fails (Unutu 16.04) since Oct 17, 2018

[Alexis Wilke]

Just in case, I tried again after commenting my .pbuilderrc and I also
have a hook.

I get the same results, the build-essential package is not happy.

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

Title:
  "pbuilder-dist create xenial" fails (Unutu 16.04) since Oct 17, 2018

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1799859/+subscriptions

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

[Bug 1799859] [NEW] "pbuilder-dist create xenial" fails (Unutu 16.04) since Oct 17, 2018

[Alexis Wilke]

Public bug reported:

I have a build environment which I can't use anymore. I get some
dependency errors as follow:

The following packages have unmet dependencies:
 libexpat1-dev : Depends: libexpat1 (= 2.1.0-7) but 2.1.0-7ubuntu0.16.04.3 is 
to be installed
E: Unable to correct problems, you have held broken packages.

Thinking that something may be wrong with my existing pbuilder/xenial-
base.tgz file, I tried to create a new version with:

pbuilder-dist create xenial

That fails too. I get the following error:

The following packages have unmet dependencies:
 build-essential : Depends: gcc (>= 4:5.2) but it is not going to be installed
   Depends: g++ (>= 4:5.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

IMPORTANT NOTE: I also tried after deleting the "pbuilder" folder, so
starting from scratch.

Another (possibly) relevant section from the attached logs:

Setting up dpkg (1.18.4ubuntu1.5) ...
(Reading database ... 12084 files and directories currently installed.)
Removing build-essential (12.1ubuntu2) ...
Removing g++ (4:5.3.1-1ubuntu1) ...
Removing g++-5 (5.3.1-14ubuntu2) ...
Removing gcc (4:5.3.1-1ubuntu1) ...
Removing gcc-5 (5.3.1-14ubuntu2) ...
(Reading database ... 11977 files and directories currently installed.)
Preparing to unpack .../cpp-5_5.4.0-6ubuntu1~16.04.11_amd64.deb ...

Here is a copy of my .pbuilderrc file which could have an effect on the
build?

# ccache
sudo mkdir -p /var/cache/pbuilder/ccache
sudo chmod a+w /var/cache/pbuilder/ccache
export CCACHE_DIR="/var/cache/pbuilder/ccache"
export PATH="/usr/lib/ccache:${PATH}"
HOOKDIR="/home/build/.pbuilder-hooks"
OTHERMIRROR="deb [trusted=yes] file:///home/build/pbuilder/${DIST}_result ./"
BINDMOUNTS="/home/build/pbuilder/${DIST}_result ${CCACHE_DIR}"
APTCACHEHARDLINK=no

My existing xenial-base.tgz has been working for a solid 2 years so I'm
not too sure what would have happened.

I found an interesting here: https://askubuntu.com/questions/937254
/cannot-install-build-essential-gcc-g-after-upgrade-to-17-04

Although it has not helped me with my pbuilder issues.

The very first error I get is this one:

pbuilder-dist: Warning: Distribution data outdated. Please check for an
update for distro-info-data. See /usr/share/doc/distro-info-
data/README.Debian for details.

However, I'm not too sure how I could update the distro-info-data more
that by getting the latest available in Ubuntu 16.04. My computer is
definitely up to date.

I found this other bug: https://bugs.launchpad.net/ubuntu/+source
/ubuntu-dev-tools/+bug/1068390 but it does not look like anything there
would help me.

** Affects: ubuntu-dev-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: packaging

** Attachment added: "Logs from pbuilder-dist create on Ubuntu 16.04"
   https://bugs.launchpad.net/bugs/1799859/+attachment/5205165/+files/create.log

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

Title:
  "pbuilder-dist create xenial" fails (Unutu 16.04) since Oct 17, 2018

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1799859/+subscriptions

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

[Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS

[Alexis Lecocq]

Same problem with ASUS S406 (no graphic card, CPU i5-8250U)

The most awkward thing is sometimes it is working, sometimes it's not. I
can't figure out why. When not working, even a restart does not re-
enable it but xrandr can enable mirroring laptop display.

Any advice?

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

Title:
  Secondary monitor not connecting in 18.04 LTS

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

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

[Bug 1797498] Re: ubuntu 18.04 crashes

[ALEXIS]

/var/cache/apt/archives/libumfpack5_1%3a5.1.2-2_i386.deb

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

Title:
  ubuntu 18.04 crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1797498/+subscriptions

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

[Bug 1797498] [NEW] ubuntu 18.04 crashes

[ALEXIS]

Public bug reported:

file corrupt. Dependences?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.26
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic i686
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: i386
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 11 23:20:25 2018
InstallationDate: Installed on 2017-05-20 (510 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
 Log time: 2018-10-11 20:01:16.908540
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done
 Log time: 2018-10-11 20:03:16.273815

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug bionic dist-upgrade i386

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

Title:
  ubuntu 18.04 crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1797498/+subscriptions

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

[Bug 1795150] Re: Canon PIXMA MG4250 unhandled by system-config-printer

[Alexis Scheuer]

I also had the same problems (and same solution) with a Dell laptop
Latitude E6430s, with the same system (fresh install, as upgrade from
16.04 did not work).

lsb_release -rd:
Description:Ubuntu 18.04.1 LTS
Release:18.04

apt-cache policy system-config-printer:
system-config-printer:
  Installé : 1.5.11-1ubuntu2
  Candidat : 1.5.11-1ubuntu2
 Table de version :
 *** 1.5.11-1ubuntu2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://fr.archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status

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

Title:
  Canon PIXMA MG4250 unhandled by system-config-printer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1795150/+subscriptions

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

[Bug 1795150] Re: Canon PIXMA MG4250 unhandled by system-config-printer

[Alexis Scheuer]

I left a message on Canon site, in a survey, about the obsolete
dependencies in their Debian package.

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

Title:
  Canon PIXMA MG4250 unhandled by system-config-printer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1795150/+subscriptions

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

[Bug 1795150] Re: Canon PIXMA MG4250 unhandled by system-config-printer

[Alexis Scheuer]

Once the turnaround applied, 'lpstat -v' returns "matériel pour 
Maison-Canon_MG4250 : cnijnet:/00-BB-C1-90-A8-B4".
The computer is a HP Laptop 14-cf0013nf.

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

Title:
  Canon PIXMA MG4250 unhandled by system-config-printer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1795150/+subscriptions

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

[Bug 1795150] [NEW] Canon PIXMA MG4250 unhandled by system-config-printer

[Alexis Scheuer]

Public bug reported:

Let us start by the beginning, and describe my printer’s configuration:
it is a Canon Pixma MG4250, connected by Wi-Fi to my internet box, and
thus available on my local network.

On XUbuntu 18.04.1 LTS (as returned by 'lsb_release -rd'), it is
detected by system-config-printer (1.5.11-1ubuntu2, from
http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages, as said
by 'apt-cache policy system-config-printer'), which by default chooses
automatically the corresponding driver, by fails at last step to define
the new printer and returns cups-error-internal-error. My first reaction
was of course to check the Web for others having a similar problem, and
the way they solved it if any did, but I did not find anything relevant.

I then tried something else: instead of choosing the automatically
detected printer, I gave the URI found on XUbuntu 16.04, which is
cnijnet:/ followed by (what I think to be) the MAC address of the
printer. I then have to choose a driver (where system-config-printer
automatically did it in previous method), but adding the printer still
fails at last step, this time with cups-error-not-possible.

I found a turnaround, but it is not straightforward: I applied the
method which worked on XUbuntu 16.04, which is to use Canon driver (from
https://www.canon.fr/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg4250.aspx?type=drivers).
I choose the Debian archive from their page
(https://www.canon.fr/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg4250.aspx?type=drivers==Linux%20(64-bit)),
and tried to install it. However, it needed three packages (libpango1.0,
libpng12 and libtiff14) while only the first is still available on 18.04
(the two others are obsolete). A web search indicated that older
packages can be used, I thus got those of the previous LTS (xenius) on
the Ubuntu archive site (https://packages.ubuntu.com - but the last one,
libtiff14, needs a direct access to tiff directory of the French archive
site (http://fr.archive.ubuntu.com/ubuntu/pool/main/t/tiff), as the
library is not referenced, only its dev part). Once those package are
saved and installed (with a sudo dpkg -i ...), Canon’s installation
script works fine, and adds the printer. I still have to verify whether
printing works (but it should be OK). I applied the method which worked
on XUbuntu 16.04, which is to use Canon driver. I choose the Debian
archive from their page, and tried to install it. However, it needed
three packages (libpango1.0, libpng12 and libtiff14) while only the
first is still available on 18.04 (the two others are obsolete). A web
search indicated that older packages can be used, I thus got those of
the previous LTS (xenius) on the Ubuntu archive site (but the last one,
libtiff14, needs a direct access to tiff directory of the French archive
site, as the library is not referenced, only its dev part). Once those
package are saved and installed (with a sudo dpkg -i ...), Canon’s
installation script works fine, and adds the printer. Everything then
works fine.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: system-config-printer 1.5.11-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
NonfreeKernelModules: 8723de
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Sep 29 17:23:26 2018
InstallationDate: Installed on 2018-08-10 (50 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 04ca:707e Lite-On Technology Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Laptop 14-cf0xxx
PackageArchitecture: all
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=72197e8c-0319-4e27-a20b-00aab768871f ro quiet splash vt.handoff=1
SourcePackage: system-config-printer
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/27/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.14
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 84B2
dmi.board.vendor: HP
dmi.board.version: KBC Version 74.22
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/27/2018:svnHP:pnHPLaptop14-cf0xxx:pvrType1ProductConfigId:rvnHP:rn84B2:rvrKBCVersion74.22:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 14-cf0xxx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: system-config-printer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification 

[Bug 1778362] Re: thymiovpl and asebastudio are missing from aseba package

[Alexis Scheuer]

OK, it works: I have been able to compile from github repository.
Everything needed (the 3 archives = master + dashel + enki, a building
script and a read-me) can be downloaded on my web pages:
http://homepages.loria.fr/AScheuer/Robots/Thymio/build_Aseba_Debian.tbz
(19.4 Mo, TarBzip file).

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

Title:
  thymiovpl and asebastudio are missing from aseba package

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

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

[Bug 1778362] Re: thymiovpl and asebastudio are missing from aseba package

[Alexis Scheuer]

It was difficult to ask apt and Synaptic to install a artful package
under bionic, but I managed to succeed.  To get as result that it was
not able to install this package (aseba_1.6.0-2) on bionic, as the QT4
dependencies cannot be installed - Stéphane mentioned it in #2.

I will probably (but not too soon) reinstall on the 1.6.0-3.1~build1
package (to get QT5 dependencies), and compile (I was hopping to avoid
that) the missing binaries...  This may help to understand why they are
missing.  If the development team does not answer until then, I will
give you a feedback.

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

Title:
  thymiovpl and asebastudio are missing from aseba package

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

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

[Bug 1762314] Re: Sound output too low

[Pierre-Alexis Ciavaldini]

Same issue here on T570 running Manjaro, this is the only bug report talking 
about the problem which seems not related to Ubuntu but to alsa. All sliders 
are up in alsamixer, sound is around half-volume compared to the Windows 
install. ALSA Driver Version: k4.14.67-1-MANJARO.
these did not help: 
https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture/Troubleshooting#Volume_is_too_low

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

Title:
  Sound output too low

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1762314/+subscriptions

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

[Bug 1779829] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build [error: implicit declaration of function ‘init_timer’]

[Alexis Mendoza]

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

I forgot maybe the bug was because I was playing while updating
something. Now it is working fine.

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

Title:
  nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed
  to build [error: implicit declaration of function ‘init_timer’]

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

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

[Bug 1779829] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build [error: implicit declaration of function ‘init_timer’]

[Alexis Mendoza]

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

Hello, how are you, some problems with my nvidia gforce 210, EVGA. that
my problem with linux. Now let`s see how is going. Because it is working
yet. But it reported an bug rigth now

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

Title:
  nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed
  to build [error: implicit declaration of function ‘init_timer’]

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

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

[Bug 1779583] Re: cron do_command.c attempts a fork() without testing for errors

[Alexis Wilke]

** Tags removed: trusty
** Tags added: xenial

** Description changed:

  The do_command.c file calls fork() twice.
  
  For the first fork(), the possibility for an error is checked properly
  and an error emitted (see
  https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
  example when that happens: message is "can't fork".) This first fork()
  makes use of a switch() statement as expected.
  
  The second fork(), however, is used inside an if() statement like this:
  
  if (*input_data && fork() == 0) { ... }
  
  Here we can see a couple of problems. After the if block, we have this
  statement:
  
  children++;
  
  which means that we will have to wait on TWO children. However, (1) the
  *input_data could return false and thus the second child may not be
  created at all. (2) the fork() could return -1 meaning that no other
  child is created.
  
  I suppose that the child_process() probably always or nearly always has
  some input_data. Otherwise it would block waiting for a child that was
  never started. And of course, it is relatively rare that fork() fails,
  unless you are running our of RAM (heap or stack can't be allocated) or
  process space (too many processes running concurrently.)
  
  I have a proposed patch to fix the problem. It uses a switch() which
  emits an error in case the fork() fails, but let the program go on as
  before (instead of an immediate exit as in the first fork()).
  
  The children variable gets incremented only when the fork() happens and
  succeeds (default: block in the new switch().)
  
- The do_command.c file did not change between 16.04 (trusty) and 18.04
+ The do_command.c file did not change between 16.04 (xenial) and 18.04
  (bionic beaver), so the patch will work for either version.

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

Title:
  cron do_command.c attempts a fork() without testing for errors

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

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

[Bug 675673] Re: One junk email repeat thousand of times (until thunderbird is stopped)

[Alexis Wilke]

Sure, I don't think anyone has ever looked in this problem,
unfortunately. Although "it works for me" now, doesn't mean it's fixed.
That's all I'm saying. The code of Thunderbird is huge so I was never
able to look enough through it and understand where the problem could
be.

Anyway, it can be closed since I'm good with the current version and now
I make sure I keep compacting my folders...

Thank you,
Alexis

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

Title:
  One junk email repeat thousand of times (until thunderbird is stopped)

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

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

[Bug 675673] Re: One junk email repeat thousand of times (until thunderbird is stopped)

[Alexis Wilke]

I don't recall having that bug happen to me for some time.

However, it stops only because I understood what was causing some other
problem. You have a feature called "Compact Folders" which is bogus and
I think that when that other problem occurs, this very bug happens. I
have had it with Thunderbird about 2 years ago (when I finally
understood that I really had to compact folders.)

The problem with compacting folders was that if a local file grows
beyond 2Gb, its size is (most certain) viewed as being negative, which
then prevents the auto-compaction from happen.

As a result, the file continues to grow "forever"--or more precisely
until it reaches 4Gb or whatever the limit is on your OS/Filesystem.
Once that limit is reached, then you start seeing this very bug
appearing. I guess something doesn't know how to get rid of that email
and it the code generates an error on the save which tells another piece
of code to try again and hence loops forever and adds new emails all the
time.

I'm pretty such that the file that caused the problem was the one
representing the Junk folder on my Local Folders. When I deleted that
file, the problems stopped and by making sure I run the compact folders
once in a while, the size is kept in check.

So, it's not fixed if that file size / compact test is not fixed.
Actually, compact should become mandatory once the file is over 1Gb. Who
needs that much data in emails?!

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

Title:
  One junk email repeat thousand of times (until thunderbird is stopped)

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

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

[Bug 1779583] Re: cron do_command.c attempts a fork() without testing for errors

[Alexis Wilke]

I guess I should attempt to compile before submitting a patch. Some
brackets were required in one of the cases.

** Patch added: "Compiling fix to second fork() in child_process()"
   
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+attachment/5158458/+files/do_command-2.patch

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

Title:
  cron do_command.c attempts a fork() without testing for errors

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

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

[Bug 1779583] Re: cron do_command.c attempts a fork() without testing for errors

[Alexis Wilke]

** Description changed:

  The do_command.c file calls fork() twice.
  
- For the first for(), the possibility for an error is checked properly
+ For the first fork(), the possibility for an error is checked properly
  and an error emitted (see
  https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
  example when that happens: message is "can't fork".) This first fork()
  makes use of a switch() statement as expected.
  
  The second fork(), however, is used inside an if() statement like this:
  
  if (*input_data && fork() == 0) { ... }
  
  Here we can see a couple of problems. After the if block, we have this
  statement:
  
  children++;
  
  which means that we will have to wait on TWO children. However, (1) the
  *input_data could return false and thus the second child may not be
  created at all. (2) the fork() could return -1 meaning that no other
  child is created.
  
  I suppose that the child_process() probably always or nearly always has
  some input_data. Otherwise it would block waiting for a child that was
  never started. And of course, it is relatively rare that fork() fails,
  unless you are running our of RAM (heap or stack can't be allocated) or
  process space (too many processes running concurrently.)
  
  I have a proposed patch to fix the problem. It uses a switch() which
  emits an error in case the fork() fails, but let the program go on as
  before (instead of an immediate exit as in the first fork()).
  
  The children variable gets incremented only when the fork() happens and
  succeeds (default: block in the new switch().)
  
  The do_command.c file did not change between 16.04 (trusty) and 18.04
  (bionic beaver), so the patch will work for either version.

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

Title:
  cron do_command.c attempts a fork() without testing for errors

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

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

[Bug 1702785] Re: High memory and "can't fork" on heavy long-lived cron daemon

[Alexis Wilke]

Actually, an immediate fix for you guys may be to make sure that there
is some *input_data. I have no clue what that means in terms of
administrative setup, though. But maybe someone else can help in that
area. The really bad statement looks like this:

if (*input_data && fork() == 0) {
... // handle input_data
exit(0);
}

children++;

The children variable counts the number of successful fork()'s. Only in
this case (1) the fork() is never checked for failure and (2) if
*input_data is false, then the fork() does not even happen. Yet, either
way, children is always increment! Ouch! As an administrator, it may not
be possible to always make sure there is something in input_data. But it
is not unlikely that this is what makes many cron fork() wait forever
and thus increase memory. I have not had that problem on my end, I was
just reading the code for fun...

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

Title:
  High memory and "can't fork" on heavy long-lived cron daemon

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

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

[Bug 1779583] [NEW] cron do_command.c attempts a fork() without testing for errors

[Alexis Wilke]

Public bug reported:

The do_command.c file calls fork() twice.

For the first for(), the possibility for an error is checked properly
and an error emitted (see
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
example when that happens: message is "can't fork".) This first fork()
makes use of a switch() statement as expected.

The second fork(), however, is used inside an if() statement like this:

if (*input_data && fork() == 0) { ... }

Here we can see a couple of problems. After the if block, we have this
statement:

children++;

which means that we will have to wait on TWO children. However, (1) the
*input_data could return false and thus the second child may not be
created at all. (2) the fork() could return -1 meaning that no other
child is created.

I suppose that the child_process() probably always or nearly always has
some input_data. Otherwise it would block waiting for a child that was
never started. And of course, it is relatively rare that fork() fails,
unless you are running our of RAM (heap or stack can't be allocated) or
process space (too many processes running concurrently.)

I have a proposed patch to fix the problem. It uses a switch() which
emits an error in case the fork() fails, but let the program go on as
before (instead of an immediate exit as in the first fork()).

The children variable gets incremented only when the fork() happens and
succeeds (default: block in the new switch().)

The do_command.c file did not change between 16.04 (trusty) and 18.04
(bionic beaver), so the patch will work for either version.

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


** Tags: bionic patch trusty

** Patch added: "Fix to second fork() in child_process()"
   
https://bugs.launchpad.net/bugs/1779583/+attachment/5158449/+files/do_command.patch

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

Title:
  cron do_command.c attempts a fork() without testing for errors

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

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

[Bug 1702785] Re: High memory and "can't fork" on heavy long-lived cron daemon

[Alexis Wilke]

I found a bug in the code as described in this issue:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583

The bug would not prevent the error you're seeing, however, there is a
second fork() which, if it fails, will block that part of cron, which
would therefore leak. So if it happens "on the wrong fork()", (1) you
won't see any logs and (2) you get a cron "process" which gets stuck
waiting for a second child that was never created.

I included a patch too.

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

Title:
  High memory and "can't fork" on heavy long-lived cron daemon

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

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

[Bug 1779583] Re: cron do_command.c attempts a fork() without testing for errors

[Alexis Wilke]

This may be one solution to the problem reported here:

https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785

Because when the second fork() fails, the cron process waits for 2
children, one of which doesn't even exist and thus cron is stuck with "a
ton" of memory allocated. This would also happen if *input_data is
false. So not just because the fork() fails... but it could be because
it does not even happen.

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

Title:
  cron do_command.c attempts a fork() without testing for errors

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

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

[Bug 1512120]

[Yves-Alexis Perez]

(In reply to pgkos.bugzilla from comment #167)
> Created attachment 6976 [details]
> Fix crash and hang while renaming
> 
> A new version of my patch. This fixes both:
> - the crash when renaming a file through the popup dialog
> - the hang when renaming many files at once (e.g. using mv)
> 
> For the remaining crashes (while using mv command), please apply
> https://github.com/jlindgren90/thunar/commit/9c6dbb1dae70.

Thanks for the patch, I'll try to test it for Debian (although it
doesn't apply at first sight on 1.6.10 so I'll try a backport)

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

Title:
  [SRU] thunar crashes on file renaming

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

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

[Bug 1512120]

[Yves-Alexis Perez]

(In reply to Andreas Böhler from comment #134)
> I forgot to mention that I am on an x64 Arch Linux machine (current as of
> today). an strace (with patch #6779 applied) gives:
> 
> write(4, "\1\0\0\0\0\0\0\0", 8) = 8
> recvmsg(5, {msg_namelen=0}, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource
> temporarily unavailable)
> inotify_rm_watch(14, 5) = 0
> futex(0x7fa94ca47a60, FUTEX_WAKE_PRIVATE, 1) = 1
> inotify_rm_watch(14, 6) = 0
> futex(0x7fa94ca47a60, FUTEX_WAKE_PRIVATE, 1) = 1
> lstat("/path/to/directory", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
> inotify_add_watch(14, "/path/to/directory",
> IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DEL
> ETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR) = 18
> futex(0x69f4f8, FUTEX_WAIT_PRIVATE, 2, NULL
> 
> And there it stops and becomes unresponsive.

Yup, I can confirm that. I've pushed the attachment #6779 to Debian and
got similar reports, and can confirm it myself. It happens when
accessing a removable device, for example.

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

Title:
  [SRU] thunar crashes on file renaming

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

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

[Bug 1742330] Re: Can't reboot, shutdown or suspend with 4.4.0-108

[Alexis Wilke]

The other bug report that seems to be similar is this one:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742323

Although someone said that they tested the other version and it did not
work for them.

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

Title:
  Can't reboot, shutdown or suspend with 4.4.0-108

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

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

[Bug 1742330] Re: Can't reboot, shutdown or suspend with 4.4.0-108

[Alexis Wilke]

Same problem here.

This kernel boots and seems to work as expected:

http://kernel.ubuntu.com/~jsalisbury/lp1741934/

The newer (stock version) 4.4.0-108.131 stops really fast. It looks like
2 or 3 pages of text. I can't scroll or use the keyboard at all once it
dies. I'm attaching my screenshot of the last page which has a stack
trace. I posted it on another bug too, but I'm not too sure whether the
other bug was really in link with the same problem.

** Attachment added: "Screenshot of "panic" showing the callstack"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742330/+attachment/5034055/+files/Screenshot-2a.jpg

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

Title:
  Can't reboot, shutdown or suspend with 4.4.0-108

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

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

[Bug 1742323] Re: Meltdown Update Kernel doesnt boot

[Alexis Wilke]

Achim Behrens,

Is the kernel that fails really 104? Or is that your backup that you
just booted into to report the problem?

The one that fails for me is the new one, 108. It just "panics" nearly
instantaneously.

** Attachment added: "Screenshot of "panic" showing the callstack"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742323/+attachment/5034029/+files/Screenshot-2a.jpg

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

Title:
  Meltdown Update Kernel doesnt boot

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

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

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Alexis Rico]

My Lenovo G50-80 is also fixed by updating to 4.14.9. I've updated the
Bug Description so anyone facing the issue can repair their devices.

** Description changed:

- SRU Justification
+ Description: An update to linux kernel on Ubuntu 17.10 that enabled the
+ intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings
+ being not stored, USB Boot impossible and EFI entries read-only.
  
- Impact: Many users are reporting issues with bios corruption with 17.10.
- This seems to stem from enabling the intel-spi-* drivers in the kernel,
- which don't appear to be ready for use on end-user machines.
+ Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
+ affected machines still suffered from a broken BIOS.
  
- Fix: Disable this driver.
+ Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into Linux
+ and BIOS should be restored to a working state.
+ 
+ ---
  
  Test Case: Fix has been verified by our HWE team on affected hardware.
  
  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.
  
  ---
  
- Hi all,
- 
- Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
- reported a corrupted BIOS.
- 
- It's not possible to save new settings in BIOS anymore and after
- rebooting, the system starts with the old settings.
- 
- Moreover (and most important) USB booting is not possible anymore since
- USB is not recognized. It's very serious, since our machines do not have
- a CDROM.
- 
- Lenovo forums at the moment are full of topics regading this issue.
- 
- Thank you!!
- 
-  UPDATE (22/12/2017) 
- 
- LENOVO machines affected so far (please add your affected model to this
- list):
+ Affected Machines:
  
  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY
  
- The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  
- Bug may effect machines from any manufacturer that uses BIOS based on
- Insyde Software.  Insyde is responding to emails acknowledging that they
- are aware of issue but are not providing details.
- 
  ---
  
- Temporary workaround:
- https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
- -Save-Settings-Or-Exit/m-p/3853208#M157885
+ Original Description:
  
- ---
+ Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
+ reported a corrupted BIOS.
  
- result from apport-collect 1734147:
+ It's not possible to save new settings in BIOS anymore and after
+ rebooting, the system starts with the old settings.
  
- ---
+ Moreover (and most important) USB booting is not possible anymore since
+ USB is not recognized. It's very serious, since our machines do not have
+ a CDROM.
  
- Architecture: amd64
- InstallationDate: Installed on 2017-10-22 (37 days ago)
- InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
- MachineType: LENOVO 20378
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
- ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
- RelatedPackageVersions:
-  linux-restricted-modules-4.13.0-17-generic N/A
-  linux-backports-modules-4.13.0-17-generic  N/A
-  linux-firmware 1.169
- Tags:  artful wayland-session
- Uname: Linux 4.13.0-17-generic x86_64
- dmi.bios.date: 08/12/2015
- dmi.bios.vendor: LENOVO
- dmi.bios.version: 9ECN43WW(V3.03)
- dmi.board.name: Lenovo Y50-70
- dmi.board.vendor: LENOVO
- dmi.board.version: Not Defined
- dmi.chassis.type: 10
- dmi.chassis.vendor: LENOVO
- dmi.chassis.version: Lenovo Y50-70
- dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
- dmi.product.family: IDEAPAD
- dmi.product.name: 20378
- dmi.product.version: Lenovo Y50-70
- dmi.sys.vendor: LENOVO
+ Lenovo forums at the moment are full of topics regading this issue.
  
- ---
+ Thank you!!

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

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

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Alexis Rico]

#275 #276 I reinstalled operating systems on the hdd with another
computer and recreated the partition table ids to mock bios but it
didn't unlock it in any way.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

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

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Alexis Rico]

Workaround for reference to install Windows with the broken BIOS.

If you try to install through PXE Windows you'll see that it errors when
trying to bcdedit the entry to BIOS and the process fails.

A nasty workaround that works is:

- Create a raw Virtual Disk that points to the physical drive
- Install Windows until the first restart through VirtualBox (it extracts only 
the wim files and creates the EFI BCD).
- Finish the installation on the Lenovo

Also I recommend you to leave rEFInd as default EFI entry (EFI/BOOT) so
that you can launch bootable USBs using the novo button when PXE fails
and defaults to rEFInd.

I hope either Lenovo or Ubuntu releases a proper fix but at least now
I've found a way to Install Linuxes, Windows and Boot USBs with the
corrupted BIOS.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

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

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Alexis Rico]

Okay, I'm "unbricked" now as I can finally boot up my system but BIOS is
still corrupted.

I've instaled a new hard drive, with the help of a PXE environment I've
set up partitions so that matches my old drive configuration and
overriden the ESP UUID to the old drive UUID with gdisk and finally
installed Ubuntu 16.04 on it.

Anyways, USB Boot, DVD Boot and BIOS Settings are still a no-go.

Trying to add, delete entries through efibootmgr errors out. Even
setting timeout errors out:

sfera@coruscant:~$ sudo efibootmgr -t 5
efibootmgr: Could not set Timeout: No such file or directory

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

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

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Alexis Rico]

Steve Langasek (vorlon) wrote 1 hour ago: #48
Based on the description of how the problem arises - Ubuntu 17.10 installed on 
a system booted in legacy mode, not in UEFI mode.

The problem appeared to me in UEFI mode, not Legacy.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

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

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Alexis Rico]

@Mathieu Trudel-Lapierre Yes, I have two issues:

1) BIOS Doesn't work fine. Same problem as @bruno USB Boot doesn't work,
DVD boot doesn't work and saving bios settings are lost of exit and
save. No white screen just the changes don't persist across reboots.

2) The hard drive failed leaving system non-bootable.

Today I've also tried installing the OS on a new drive and a different
computer, booting through PXE to a Ubuntu Live CD and trying to insert a
new entry for the new os through efibootmgr.

So far I've learnt that efibootmgr is unable to create a new entry as it
errors No such File. And deleting the old EFI entries seems to work but
when rebooting to bios the old EFI entries are still there.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

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

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Alexis Rico]

Status update: Attempt to install Windows over PXE won't work.

The BIOS is really derped. The error of Windows Installer is: "Windows
could not update the computer's boot configuration. Installation cannot
proceed.".

I'm out of ideas...

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

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

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Alexis Rico]

@Mathieu Trudel-Lapierre (cyphermox)
@Dimitri John Ledkov (xnox)

My Lenovo G50-80 was running a Ubuntu 17.10 with no dualboot. The BIOS
didn't allow me to change ANY of the options and USB/DVD boot did not
work for a few weeks or maybe months (I don't check BIOS every day).

Also it seems that grub failed when doing an apt upgrade (gave me a
syscall error I/O) and the laptop turned itself into a brick because the
"ubuntu"EFI entry also stopped working.

Right now I've set up a PXE server and I'm trying to install Windows 10
over LAN. If I can get it to boot, I'll try to apply the latest BIOS
patch (only available for install through Windows) and see if everything
goes back to normal.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

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

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Alexis Rico]

This is unacceptable, right now my Lenovo G50-80 is a brick.

USB Boot does not work. 
DVD Boot does not work. 
BIOS Boot menu doesn't autodetect changes on the hard drive EFI paths.

And during an update grub stopped working, it reported a syscall error
of I/O and on reboot I couldn't start the computer anymore. I would
normally boot a live cd and boot-repair but guess what UEFI USB Boot
does not work and Legacy capabilities won't work either.

And reprogramming the BIOS chip is not a viable solution by the way...

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

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

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Alexis Rico]

This is unacceptable, right now my Lenovo G50-80 is a brick.

USB Boot does not work. 
DVD Boot does not work. 
BIOS Boot menu doesn't autodetect changes on the hard drive EFI paths.

And during an update grub stopped working, it reported a syscall error
of I/O and on reboot I couldn't start the computer anymore. I would
normally boot a live cd and boot-repair but guess what UEFI USB Boot
does not work and Legacy capabilities won't work either.

And reprogramming the BIOS chip is not a viable solution by the way...

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

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

[Bug 1720908] [NEW] Firefox cannot load Flash because of libxul broken dependency

[Alexis Wilke]

Public bug reported:

When I start Firefox version 56 in my console and then go to a page
using Adobe Flash, I get the following errors:

/usr/lib/firefox/plugin-container: symbol lookup error: 
/usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea
[18352] WARNING: pipe error (114): Connection reset by peer: file 
/build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
/usr/lib/firefox/plugin-container: symbol lookup error: 
/usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea
[18352] WARNING: pipe error (94): Connection reset by peer: file 
/build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353
/usr/lib/firefox/plugin-container: symbol lookup error: 
/usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea
[18352] WARNING: pipe error (41): Connection reset by peer: file 
/build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 353

Each time the problem is the same: gdk_screen_get_monitor_workarea is
undefined. Gnome marked that function as deprecated, but Firefox version
55 worked just fine, whereas Firefox 56 fails with Flash.

https://developer.gnome.org/gdk3/stable/GdkScreen.html#gdk-screen-get-
monitor-workarea

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 56.0+build6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  alexis24733 F pulseaudio
 /dev/snd/controlC0:  alexis24733 F pulseaudio
BuildID: 20170928135459
Channel: Unavailable
CurrentDesktop: Unity
Date: Mon Oct  2 17:05:32 2017
ExecutablePath: /usr/lib/firefox/firefox
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2010-12-27 (2471 days ago)
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.2)
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-33216e86-e3b0-440b-a25a-2754b1171002
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=56.0/20170928135459 (In use)
RfKill:
 
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to xenial on 2016-05-20 (500 days ago)
dmi.bios.date: 09/16/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F14
dmi.board.name: P55A-UD4P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd09/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P55A-UD4P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Affects: firefox (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/1720908

Title:
  Firefox cannot load Flash because of libxul broken dependency

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

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

[Bug 1714832] [NEW] package linux-image-4.4.0-93-generic (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './boot/vmlinuz-4.4.0-93-generic' a '/boot/vmlinuz-4.4.

[alexis junior ambassa]

Public bug reported:

mi pc va muy lento y las configuraciones estan mal hechas

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-93-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  usuario1716 F pulseaudio
  alexisja   2664 F pulseaudio
 /dev/snd/seq:timidity   1002 F timidity
Date: Fri Sep  1 18:54:12 2017
DpkgHistoryLog:
 Start-Date: 2017-09-01  18:54:05
 Commandline: /usr/bin/unattended-upgrade
 Install: linux-image-extra-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic), 
linux-headers-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic), 
linux-headers-4.4.0-93:amd64 (4.4.0-93.116, automatic), 
linux-image-4.4.0-93-generic:amd64 (4.4.0-93.116, automatic)
 Upgrade: linux-headers-generic:amd64 (4.4.0.92.97, 4.4.0.93.98), 
linux-libc-dev:amd64 (4.4.0-92.115, 4.4.0-93.116), python3-jwt:amd64 (1.3.0-1, 
1.3.0-1ubuntu0.1), linux-image-generic:amd64 (4.4.0.92.97, 4.4.0.93.98), 
libgs9:amd64 (9.18~dfsg~0-0ubuntu2.6, 9.18~dfsg~0-0ubuntu2.7), 
chromium-codecs-ffmpeg-extra:amd64 (60.0.3112.78-0ubuntu0.16.04.1293, 
60.0.3112.113-0ubuntu0.16.04.1298), ghostscript:amd64 (9.18~dfsg~0-0ubuntu2.6, 
9.18~dfsg~0-0ubuntu2.7), ghostscript-x:amd64 (9.18~dfsg~0-0ubuntu2.6, 
9.18~dfsg~0-0ubuntu2.7), libgs9-common:amd64 (9.18~dfsg~0-0ubuntu2.6, 
9.18~dfsg~0-0ubuntu2.7), linux-generic:amd64 (4.4.0.92.97, 4.4.0.93.98)
DpkgTerminalLog:
 Preparando para desempaquetar 
.../linux-image-4.4.0-93-generic_4.4.0-93.116_amd64.deb ...
 Done.
 Desempaquetando linux-image-4.4.0-93-generic (4.4.0-93.116) ...
 dpkg: error al procesar el archivo 
/var/cache/apt/archives/linux-image-4.4.0-93-generic_4.4.0-93.116_amd64.deb 
(--unpack):
  no se pudieron copiar los datos extraídos de 
'./boot/vmlinuz-4.4.0-93-generic' a '/boot/vmlinuz-4.4.0-93-generic.dpkg-new': 
fallo al escribir (No queda espacio en el dispositivo)
ErrorMessage: no se pudieron copiar los datos extraídos de 
'./boot/vmlinuz-4.4.0-93-generic' a '/boot/vmlinuz-4.4.0-93-generic.dpkg-new': 
fallo al escribir (No queda espacio en el dispositivo)
HibernationDevice: RESUME=UUID=2696c717-7cde-4f21-b420-2b9c5abfe820
InstallationDate: Installed on 2017-04-22 (134 days ago)
InstallationMedia: It
MachineType: Acer Extensa 5635G
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-92-generic 
root=/dev/mapper/it--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.9
SourcePackage: linux
Title: package linux-image-4.4.0-93-generic (not installed) failed to 
install/upgrade: no se pudieron copiar los datos extraídos de 
'./boot/vmlinuz-4.4.0-93-generic' a '/boot/vmlinuz-4.4.0-93-generic.dpkg-new': 
fallo al escribir (No queda espacio en el dispositivo)
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: V0.3305
dmi.board.name: BA50-MV
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenix:bvrV0.3305:bd08/14/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
dmi.product.name: Extensa 5635G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-4.4.0-93-generic (not installed) failed to
  install/upgrade: no se pudieron copiar los datos extraídos de
  './boot/vmlinuz-4.4.0-93-generic' a '/boot/vmlinuz-4.4.0-93-generic
  .dpkg-new': fallo al escribir (No queda espacio en el dispositivo)

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

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

[Bug 1708341] [NEW] package libldap-2.4-2 2.4.42+dfsg-2ubuntu3.1 failed to install/upgrade: intentando sobreescribir el compartido `/etc/ldap/ldap.conf', que es distinto de otras instancias del paquet

[Alexis Lira]

Public bug reported:

i just wanted to upgrade and appeared that error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libldap-2.4-2 2.4.42+dfsg-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Wed Aug  2 01:41:22 2017
ErrorMessage: intentando sobreescribir el compartido `/etc/ldap/ldap.conf', que 
es distinto de otras instancias del paquetes libldap-2.4-2:amd64
InstallationDate: Installed on 2016-08-04 (363 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: openldap
Title: package libldap-2.4-2 2.4.42+dfsg-2ubuntu3.1 failed to install/upgrade: 
intentando sobreescribir el compartido `/etc/ldap/ldap.conf', que es distinto 
de otras instancias del paquetes libldap-2.4-2:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libldap-2.4-2 2.4.42+dfsg-2ubuntu3.1 failed to
  install/upgrade: intentando sobreescribir el compartido
  `/etc/ldap/ldap.conf', que es distinto de otras instancias del
  paquetes libldap-2.4-2:amd64

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

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

[Bug 1707048] [NEW] bsdutils conflict

[Alexis Lira]

Public bug reported:

dpkg: error al procesar el paquete bsdutils (--configure):
 el paquete bsdutils no está listo para configurarse
 no se puede configurar (estado actual `half-installed')
Se encontraron errores al procesar:
 bsdutils
E: Sub-process /usr/bin/dpkg returned an error code (1)

** Affects: util-linux (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/1707048

Title:
  bsdutils conflict

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

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

Re: [Bug 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.

[ALEXIS]

Sorry, after Windows 7

2017-07-17 16:18 GMT-03:00 Andreas Hasenack :

> Thanks for getting back to us and letting us know your system is working
> correctly again. I will leave this bug marked as incomplete because
> there is not enough data for us to act on a fix. If you come across more
> information on this issue, or if it happens again, please post back here
> and we can take another look. Otherwise, it will expire in due course
> and automatically close.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703350
>
> Title:
>   package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
>   está en un estado grave de inconsistencia - debe reinstalarlo  antes
>   de intentar su configuración.
>
> Status in liburcu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   it crashes on sudo apt update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: liburcu4:i386 0.9.1-3
>   ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
>   Uname: Linux 4.4.0-83-generic i686
>   ApportVersion: 2.20.1-0ubuntu2.9
>   Architecture: i386
>   Date: Mon Jul 10 07:44:55 2017
>   Dependencies:
>gcc-6-base 6.0.1-0ubuntu1
>libc6 2.23-0ubuntu9
>libgcc1 1:6.0.1-0ubuntu1
>   ErrorMessage: El paquete está en un estado grave de inconsistencia -
> debe reinstalarlo  antes de intentar su configuración.
>   InstallationDate: Installed on 2017-05-20 (51 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.2
>apt  1.2.20
>   SourcePackage: liburcu
>   Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El
> paquete está en un estado grave de inconsistencia - debe reinstalarlo
> antes de intentar su configuración.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/
> 1703350/+subscriptions
>

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

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

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

Re: [Bug 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.

[ALEXIS]

Andreas, my english is very poor.
The problem happens before Window 7 checks the hard disck for
inconsistences and I stopped it.
Thank you for your help.

2017-07-17 16:18 GMT-03:00 Andreas Hasenack :

> Thanks for getting back to us and letting us know your system is working
> correctly again. I will leave this bug marked as incomplete because
> there is not enough data for us to act on a fix. If you come across more
> information on this issue, or if it happens again, please post back here
> and we can take another look. Otherwise, it will expire in due course
> and automatically close.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703350
>
> Title:
>   package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
>   está en un estado grave de inconsistencia - debe reinstalarlo  antes
>   de intentar su configuración.
>
> Status in liburcu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   it crashes on sudo apt update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: liburcu4:i386 0.9.1-3
>   ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
>   Uname: Linux 4.4.0-83-generic i686
>   ApportVersion: 2.20.1-0ubuntu2.9
>   Architecture: i386
>   Date: Mon Jul 10 07:44:55 2017
>   Dependencies:
>gcc-6-base 6.0.1-0ubuntu1
>libc6 2.23-0ubuntu9
>libgcc1 1:6.0.1-0ubuntu1
>   ErrorMessage: El paquete está en un estado grave de inconsistencia -
> debe reinstalarlo  antes de intentar su configuración.
>   InstallationDate: Installed on 2017-05-20 (51 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.2
>apt  1.2.20
>   SourcePackage: liburcu
>   Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El
> paquete está en un estado grave de inconsistencia - debe reinstalarlo
> antes de intentar su configuración.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/
> 1703350/+subscriptions
>

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

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

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

Re: [Bug 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.

[ALEXIS]

I had restarted my pc and it works well

2017-07-14 5:23 GMT-03:00 ChristianEhrhardt
<1703...@bugs.launchpad.net>:

> And - did it fix your issue around the inconsistent package?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703350
>
> Title:
>   package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
>   está en un estado grave de inconsistencia - debe reinstalarlo  antes
>   de intentar su configuración.
>
> Status in liburcu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   it crashes on sudo apt update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: liburcu4:i386 0.9.1-3
>   ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
>   Uname: Linux 4.4.0-83-generic i686
>   ApportVersion: 2.20.1-0ubuntu2.9
>   Architecture: i386
>   Date: Mon Jul 10 07:44:55 2017
>   Dependencies:
>gcc-6-base 6.0.1-0ubuntu1
>libc6 2.23-0ubuntu9
>libgcc1 1:6.0.1-0ubuntu1
>   ErrorMessage: El paquete está en un estado grave de inconsistencia -
> debe reinstalarlo  antes de intentar su configuración.
>   InstallationDate: Installed on 2017-05-20 (51 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.2
>apt  1.2.20
>   SourcePackage: liburcu
>   Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El
> paquete está en un estado grave de inconsistencia - debe reinstalarlo
> antes de intentar su configuración.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/
> 1703350/+subscriptions
>

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

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

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

Re: [Bug 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.

[ALEXIS]

Done

2017-07-11 16:10 GMT-03:00 Andreas Hasenack :

> Thanks for filing this bug in Ubuntu.
>
> Could you please try the following commands:
>
> sudo apt update
>
> sudo apt install --reinstall liburcu4
>
> And report back here please?
>
> Thanks
>
>
> ** Changed in: liburcu (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703350
>
> Title:
>   package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
>   está en un estado grave de inconsistencia - debe reinstalarlo  antes
>   de intentar su configuración.
>
> Status in liburcu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   it crashes on sudo apt update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: liburcu4:i386 0.9.1-3
>   ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
>   Uname: Linux 4.4.0-83-generic i686
>   ApportVersion: 2.20.1-0ubuntu2.9
>   Architecture: i386
>   Date: Mon Jul 10 07:44:55 2017
>   Dependencies:
>gcc-6-base 6.0.1-0ubuntu1
>libc6 2.23-0ubuntu9
>libgcc1 1:6.0.1-0ubuntu1
>   ErrorMessage: El paquete está en un estado grave de inconsistencia -
> debe reinstalarlo  antes de intentar su configuración.
>   InstallationDate: Installed on 2017-05-20 (51 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.2
>apt  1.2.20
>   SourcePackage: liburcu
>   Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El
> paquete está en un estado grave de inconsistencia - debe reinstalarlo
> antes de intentar su configuración.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/
> 1703350/+subscriptions
>

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

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

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

[Bug 1703350] [NEW] package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.

[ALEXIS]

Public bug reported:

it crashes on sudo apt update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: liburcu4:i386 0.9.1-3
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic i686
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: i386
Date: Mon Jul 10 07:44:55 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2017-05-20 (51 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: liburcu
Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está 
en un estado grave de inconsistencia - debe reinstalarlo  antes de intentar su 
configuración.
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

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

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

[Bug 1703126] [NEW] package liblttng-ust-ctl2:i386 2.7.1-1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[ALEXIS]

Public bug reported:

crash at start

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: liblttng-ust-ctl2:i386 2.7.1-1
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic i686
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
Date: Sat Jul  8 12:05:54 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
 liburcu4 0.9.1-3
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2017-05-20 (49 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: ust
Title: package liblttng-ust-ctl2:i386 2.7.1-1 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package liblttng-ust-ctl2:i386 2.7.1-1 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

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

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

[Bug 1292324] Re: Support non-root X

[Yves-Alexis Perez]

Robert,

I know you weren't interested in this but would review patches if
needed. Could you point people to the right directions on where to drop
privileges before running X server and stuff like that?

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

Title:
  Support non-root X

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

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

[Bug 1695564] [NEW] package linux-firmware 1.157.10 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[hermes alexis]

Public bug reported:

I intented upgrade my ubuntu but in the end show me the message error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.10
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri Jun  2 20:34:42 2017
Dependencies:
 
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2017-03-16 (78 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: initramfs-tools
Title: package linux-firmware 1.157.10 failed to install/upgrade: el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package linux-firmware 1.157.10 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1695564/+subscriptions

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

[Bug 1678568] [NEW] The installation does not finish

[Alexis Kilovatico]

Public bug reported:

The installer failed before completing the installation

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.8.13
ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: i386
CasperVersion: 1.340.2
Date: Sun Apr  2 00:55:25 2017
InstallCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet 
splash --- maybe-ubiquity
LiveMediaBuild: Xubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
ProcEnviron:
 LANGUAGE=es_VE.UTF-8
 PATH=(custom, no user)
 LANG=es_VE.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 trusty ubiquity-2.18.8.13 xubuntu

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

Title:
  The installation does not finish

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

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

[Bug 1656649] Re: AMDGPU causes kernel panic with

[Alexis Lecocq]

I tested daily-live of March 19. I don't get any AMDGPU *ERROR* and
suspend is as expected so I think this bug has been fixed.

So what about current 16.04 LTS ? For now I'm using kernel 4.10 but I
have to manually update it.

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

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

Title:
  AMDGPU causes kernel panic with

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

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

[Bug 1307559] Re: Window decorations not drawn on external monitor

[Alexis Lecocq]

martinely95 thanks for the tip, working for now, will post future issues

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

Title:
  Window decorations not drawn on external monitor

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

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

[Bug 1656649] Re: AMDGPU causes kernel panic with

[Alexis Lecocq]

Christopher M. Penalver, of course mainline kernel has been tested and
is working fine without any non-default kernel
parameters/WORKAROUNDs/switcharoo.

Why did you add tag bios-outdated-2.00 ? Where did you see this
information ? Added tag "kernel-fixed-upstream"

Paco Raxim I suggest you to open a new bug report.

** Tags added: kernel-fixed-upstream

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

Title:
  AMDGPU causes kernel panic with

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

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

[Bug 1663376] Re: php7.0-snmp generates many warnings without snmp installed.

[Alexis Wilke]

Bug reported to Debian, reference:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855467

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

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

Title:
  php7.0-snmp generates many warnings without snmp installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1663376/+subscriptions

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

[Bug 1663376] [NEW] php7.0-snmp generates many warnings without snmp installed.

[Alexis Wilke]

Public bug reported:

Somehow, the php7.0-snmp generates many warnings about missing "things"
until I install `snmp`. Maybe snmp should be a dependency?

A couple of references of people mentioning the problem:

https://www.digitalocean.com/community/questions/installed-php-7-0-now-
returns-errors

http://stackoverflow.com/questions/21257589/ubuntu-typing-php-in-
terminal-shows-a-lot-of-errors

The following is the output of starting a PHP CLI session without `snmp`
installed. After installing `snmp`, all those errors/warnings disappear.
So this is why I would suggest making `snmp` a dependency of the
`php7.0-snmp` package. Although if setting uip the `/etc/snmp/snmp.conf`
package would be enough (it turns off the MIB search) maybe making the
snmp library react as that was the default could be better. Only it may
be harder to get the snmp library owner to do such.


$ php -a
MIB search path: 
/home/alexis/.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf:/usr/share/mibs/site:/usr/share/snmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp
Cannot find module (SNMPv2-MIB): At line 1 in (none)
Cannot find module (IF-MIB): At line 1 in (none)
Cannot find module (IP-MIB): At line 1 in (none)
Cannot find module (TCP-MIB): At line 1 in (none)
Cannot find module (UDP-MIB): At line 1 in (none)
Cannot find module (HOST-RESOURCES-MIB): At line 1 in (none)
Cannot find module (NOTIFICATION-LOG-MIB): At line 1 in (none)
Cannot find module (DISMAN-EVENT-MIB): At line 1 in (none)
Cannot find module (DISMAN-SCHEDULE-MIB): At line 1 in (none)
Cannot find module (HOST-RESOURCES-TYPES): At line 1 in (none)
Cannot find module (MTA-MIB): At line 1 in (none)
Cannot find module (NETWORK-SERVICES-MIB): At line 1 in (none)
Cannot find module (SNMPv2-TC): At line 15 in 
/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt
Cannot find module (SNMPv2-SMI): At line 34 in 
/usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Cannot find module (SNMPv2-TC): At line 37 in 
/usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Did not find 'enterprises' in module #-1 (/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Did not find 'TruthValue' in module #-1 (/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Unlinked OID in UCD-SNMP-MIB: ucdavis ::= { enterprises 2021 }
Undefined identifier: enterprises near line 39 of 
/usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt)
Did not find 'ucdExperimental' in module UCD-SNMP-MIB 
(/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt)
Unlinked OID in UCD-DISKIO-MIB: ucdDiskIOMIB ::= { ucdExperimental 15 }
Undefined identifier: ucdExperimental near line 19 of 
/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt
Cannot find module (SNMPv2-TC): At line 10 in 
/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt)
Did not find 'ucdExperimental' in module UCD-SNMP-MIB 
(/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt)
Unlinked OID in UCD-DLMOD-MIB: ucdDlmodMIB ::= { ucdExperimental 14 }
Undefined identifier: ucdExperimental near line 13 of 
/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt
Cannot find module (SNMPv2-TC): At line 15 in 
/usr/share/snmp/mibs/LM-SENSORS-MIB.txt
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/LM-SENSORS-MIB.txt)
Did not find 'ucdExperimental' in module UCD-SNMP-MIB 
(/usr/share/snmp/mibs/LM-SENSORS-MIB.txt)
Unlinked OID in LM-SENSORS-MIB: lmSensors ::= { ucdExperimental 16 }
Undefined identifier: ucdExperimental near line 32 of 
/usr/share/snmp/mibs/LM-SENSORS-MIB.txt
Did not find 'ucdavis' in module UCD-SNMP-MIB 
(/usr/share/snmp/mibs/UCD-DEMO-MIB.txt)
Unlinked OID in UCD-DEMO-MIB: ucdDemoMIB ::= { ucdavis 14 }
Undefined identifier: ucdavis near line 7 of 
/usr/share/snmp/mibs/UCD-DEMO-MIB.txt
Cannot find module (SNMP-TARGET-MIB): At line 1 in (none)
Cannot find module (SNMP-FRAMEWORK-MIB): At line 9 in 
/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Cannot find module (SNMPv2-SMI): At line 8 in 
/usr/share/snmp/mibs/NET-SNMP-MIB.txt
Did not find 'enterprises' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-MIB.txt)
Unlinked OID in NET-SNMP-MIB: netSnmp ::= { enterprises 8072 }
Undefined identifier: enterprises near line 10 of 
/usr/share/snmp/mibs/NET-SNMP-MIB.txt
Cannot find module (SNMPv2-TC): At line 21 in 
/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Did not find 'SnmpAdminString' in module #-1 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'netSnmpObjects' in module NET-SNMP-MIB 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'netSnmpModuleIDs' in module NET-SNMP-MIB 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'netSnmpNotifications' in module NET-SNMP-MIB 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'netSnmpGroups' in module NET-SNMP-MIB 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'DisplayString' in module 

[Bug 1656649] Re: AMDGPU causes kernel panic with

[Alexis Lecocq]

I am new to bug reports so I don't know how to set tags but I changed
status to confirmed with message "kernel-fixed-upstream". I tested with
latest mainline kernel v4.10-rc7 mainline build for amd64.

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

Title:
  AMDGPU causes kernel panic with

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

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

[Bug 1656649] Re: AMDGPU causes kernel panic with

[Alexis Lecocq]

kernel-fixed-upstream

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

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

Title:
  AMDGPU causes kernel panic with

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

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

[Bug 1659668] [NEW] package openjdk-8-jre-headless:amd64 8u121-b13-0ubuntu1.16.04.2 failed to install/upgrade: end of file on stdin at conffile prompt

[Alexis]

Public bug reported:

this happen after a "apt-get dist-upgrade" command; my apologies but i
can't give you more information , i simply don't know, because i am not
using at this moment such package.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openjdk-8-jre-headless:amd64 8u121-b13-0ubuntu1.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu Jan 26 13:22:32 2017
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2016-09-11 (137 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.18
SourcePackage: openjdk-8
Title: package openjdk-8-jre-headless:amd64 8u121-b13-0ubuntu1.16.04.2 failed 
to install/upgrade: end of file on stdin at conffile prompt
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openjdk-8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package openjdk-8-jre-headless:amd64 8u121-b13-0ubuntu1.16.04.2 failed
  to install/upgrade: end of file on stdin at conffile prompt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1659668/+subscriptions

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

[Bug 1656649] Re: AMDGPU causes kernel panic with

[Alexis Lecocq]

The working workaround for me was to add "radeon.modeset=0
amdgpu.runpm=0 acpi_backlight=intel_backlight" to
GRUB_CMDLINE_LINUX_DEFAULT and NOT to switch off switcheroo

In case I disable switcheroo, I have a bug on shutdown. The screen goes
to console printing some errors (logs attached) and freezes (caps lock
not blinking).

** Attachment added: "kernel.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656649/+attachment/4804702/+files/kernel.log

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

Title:
  AMDGPU causes kernel panic with

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

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

[Bug 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU

[Alexis Lecocq]

Filed a new report as suggested
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656649

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

Title:
  amdgpu causes NULL pointer dereference when trying to use Topaz
  (Radeon R7 M265) GPU

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

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

[Bug 1656649] [NEW] AMDGPU causes kernel panic with

[Alexis Lecocq]

Public bug reported:

Laptop is Toshiba Satellite S50-B-12R 
http://www.toshiba.be/fr/discontinued-products/satellite-s50-b-12r/
Graphic card is AMD Radeon R7 M260

Running Ubuntu 16.04, system was unstable when first installed it (a lot
of random kernel panic). Problem seemed related to new AMDGPU drivers
introduced into new kernels so I tried to disable graphic card by adding
radeon.modeset=0 to GRUB_CMDLINE_LINUX_DEFAULT as suggested here
http://askubuntu.com/questions/771562/16-04-power-off-discrete-graphics-
ati-amd and there http://askubuntu.com/questions/771838/should-i
-disable-amd-graphic

After this, system is stable except when sleeping. After wake up, I get
a kernel panic within 5min (time is random). System logs show a trouble
about AMDGPU *ERROR*.

I had read that AMD GC was causing trouble with ubuntu 16.04 and I don't care 
to get it working. For my usage, Intel integrated graphics are enough. But an 
easy way to disable those drivers in case of trouble should be written on 
https://wiki.ubuntu.com/XenialXerus/ReleaseNotes#fglrx
Looking on forums, a lot of users are affected by this issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-59-generic 4.4.0-59.80
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  axtux  1963 F pulseaudio
 /dev/snd/controlC1:  axtux  1963 F pulseaudio
CurrentDesktop: Unity
Date: Sun Jan 15 13:29:26 2017
HibernationDevice: RESUME=UUID=d3a0be1f-38a0-475c-863c-38ca63b47d81
InstallationDate: Installed on 2016-11-01 (74 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: TOSHIBA SATELLITE S50-B
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash radeon.modeset=0 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-59-generic N/A
 linux-backports-modules-4.4.0-59-generic  N/A
 linux-firmware1.157.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/26/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.80
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.80:bd08/26/2014:svnTOSHIBA:pnSATELLITES50-B:pvrPSPQ6E-01K002BT:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE S50-B
dmi.product.version: PSPQ6E-01K002BT
dmi.sys.vendor: TOSHIBA

** Affects: linux (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/1656649

Title:
  AMDGPU causes kernel panic with

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

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