[Touch-packages] [Bug 2047137] Re: nvidia 390 driver from ppa segfault
** Description changed:
I tried to build and install package form binaries,
nvidia-graphics-drivers-390 (390.157-0ubuntu8).
Now, I am writing this bug report with nouveau, because I commented blacklist
in /usr/lib/modprobe.d/nvidia-graphics-drivers.conf.
But I want to use nvidia driver like on 22.10 (on 22.04/22.10 it were
working). On 23.04/23.10 it crashes.
There is an error in xorg log, it runs wrong mode, and writes:
[34.950] (II) NVIDIA(0): Validated MetaModes:
[34.950] (II) NVIDIA(0): "DFP-1:nvidia-auto-select"
[34.950] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[34.956] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi"
X config
[34.956] (--) NVIDIA(0): option
[34.957] (II) NVIDIA: Using 6144.00 MB of virtual memory for indirect
memory
[34.957] (II) NVIDIA: access.
[34.959] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event
daemon; the daemon
...
[35.115] (II) Initializing extension DRI2
[35.115] (II) Initializing extension GLX
[35.115] (II) Initializing extension GLX
[35.115] (II) Indirect GLX disabled.
- Then, in lightdm log an error with segfault appears.
+ Then, in lightdm log an error with segfault appears:
+
+ malloc(): unaligned tcache chunk detected
+
I tried different configs of xorg, so I made a conclusion that nvidia drivers
are built wrong again.
My /etc/X11/xorg.conf.d/10-nvidia.conf:
Section "Files"
ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
ModulePath "/usr/lib/x86_64-linux-gnu/vdpau"
ModulePath "/usr/lib/x86_64-linux-gnu/"
ModulePath "/usr/lib/modules/6.5.0-14-generic/updates/dkms"
ModulePath "/usr/lib/xorg/modules/extensions"
ModulePath "/usr/lib/xorg/modules/drivers"
ModulePath "/usr/lib/xorg/modules/input"
ModulePath "/usr/lib/xorg/modules"
EndSection
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
EndSection
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Dec 21 16:55:06 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/390.157, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 430] [1043:83c3]
InstallationDate: Installed on 2023-12-16 (5 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=ru_RU.UTF-8
LANGUAGE=ru_RU
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=554b729e-40d0-453e-8bb7-a893de671152 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2010
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.name: IC780M-A2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd11/03/2010:br8.15:svnECS:pnIC780M-A2:pvr1.0:rvnECS:rnIC780M-A2:rvr1.0:cvnECS:ct3:cvr:sku:
dmi.product.name: IC780M-A2
dmi.product.version: 1.0
dmi.sys.vendor: ECS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2047137
Title:
nvidia 390 driver from ppa segfault
Status in nvidia-graphics-drivers-390 package in Ubuntu:
New
Status in xorg package in Ubuntu:
New
Bug description:
I tried to build and install package form binaries,
nvidia-graphics-drivers-390 (390.157-0ubuntu8).
Now, I am writing this bug report with nouveau, because
[Touch-packages] [Bug 2047137] Re: nvidia 390 driver from ppa segfault
** Description changed:
I tried to build and install package form binaries,
nvidia-graphics-drivers-390 (390.157-0ubuntu8).
Now, I am writing this bug report with nouveau, because I commented blacklist
in /usr/lib/modprobe.d/nvidia-graphics-drivers.conf.
- But I want to use nvidia driver like on 22.10 (on 22.04/22.10 it were
working). On 23.04/23.10 it crashes.
+ But I want to use nvidia driver like on 22.10 (on 22.04/22.10 it were
working). On 23.04/23.10 it crashes.
There is an error in xorg log, it runs wrong mode, and writes:
[34.950] (II) NVIDIA(0): Validated MetaModes:
[34.950] (II) NVIDIA(0): "DFP-1:nvidia-auto-select"
[34.950] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[34.956] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi"
X config
[34.956] (--) NVIDIA(0): option
[34.957] (II) NVIDIA: Using 6144.00 MB of virtual memory for indirect
memory
[34.957] (II) NVIDIA: access.
[34.959] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event
daemon; the daemon
...
[35.115] (II) Initializing extension DRI2
[35.115] (II) Initializing extension GLX
[35.115] (II) Initializing extension GLX
[35.115] (II) Indirect GLX disabled.
- Then, in lightdm log an error with segfault appears.
+ Then, in lightdm log an error with segfault appears.
I tried different configs of xorg, so I made a conclusion that nvidia drivers
are built wrong again.
My /etc/X11/xorg.conf.d/10-nvidia.conf:
Section "Files"
- ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
- ModulePath "/usr/lib/x86_64-linux-gnu/vdpau"
- ModulePath "/usr/lib/x86_64-linux-gnu/"
- ModulePath "/usr/lib/modules/6.5.0-14-generic/updates/dkms"
- ModulePath "/usr/lib/xorg/modules/extensions"
- ModulePath "/usr/lib/xorg/modules/drivers"
- ModulePath "/usr/lib/xorg/modules/input"
- ModulePath "/usr/lib/xorg/modules"
+ ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
+ ModulePath "/usr/lib/x86_64-linux-gnu/vdpau"
+ ModulePath "/usr/lib/x86_64-linux-gnu/"
+ ModulePath "/usr/lib/modules/6.5.0-14-generic/updates/dkms"
+ ModulePath "/usr/lib/xorg/modules/extensions"
+ ModulePath "/usr/lib/xorg/modules/drivers"
+ ModulePath "/usr/lib/xorg/modules/input"
+ ModulePath "/usr/lib/xorg/modules"
EndSection
Section "OutputClass"
- Identifier "nvidia"
- MatchDriver "nvidia-drm"
- Driver "nvidia"
- Option "AllowEmptyInitialConfiguration"
+ Identifier "nvidia"
+ MatchDriver "nvidia-drm"
+ Driver "nvidia"
+ Option "AllowEmptyInitialConfiguration"
EndSection
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
- BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Dec 21 16:55:06 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
- nvidia/390.157, 6.5.0-14-generic, x86_64: installed
- virtualbox/7.0.10, 6.5.0-14-generic, x86_64: installed
+ nvidia/390.157, 6.5.0-14-generic, x86_64: installed
+ virtualbox/7.0.10, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
- NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
-Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 430] [1043:83c3]
+ NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
+ Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 430] [1043:83c3]
InstallationDate: Installed on 2023-12-16 (5 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
- LANG=ru_RU.UTF-8
- LANGUAGE=ru_RU
- PATH=(custom, no user)
- SHELL=/bin/bash
- XDG_RUNTIME_DIR=
+ LANG=ru_RU.UTF-8
+ LANGUAGE=ru_RU
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+ XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=554b729e-40d0-453e-8bb7-a893de671152 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2010
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.name: IC780M-A2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd11/03/2010:br8.15:svnECS:pnIC780M-A2:pvr1.0:rvnECS:rnIC780M-A2:rvr1.0:cvnECS:ct3:cvr:sku:
dmi.product.name: IC780M-A2
dmi.product.version: 1.0
dmi
[Touch-packages] [Bug 2047137] Re: nvidia 390 driver from ppa segfault
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2047137
Title:
nvidia 390 driver from ppa segfault
Status in nvidia-graphics-drivers-390 package in Ubuntu:
New
Status in xorg package in Ubuntu:
New
Bug description:
I tried to build and install package form binaries,
nvidia-graphics-drivers-390 (390.157-0ubuntu8).
Now, I am writing this bug report with nouveau, because I commented blacklist
in /usr/lib/modprobe.d/nvidia-graphics-drivers.conf.
But I want to use nvidia driver like on 22.10 (on 22.04/22.10 it were
working). On 23.04/23.10 it crashes.
There is an error in xorg log, it runs wrong mode, and writes:
[34.950] (II) NVIDIA(0): Validated MetaModes:
[34.950] (II) NVIDIA(0): "DFP-1:nvidia-auto-select"
[34.950] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[34.956] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi"
X config
[34.956] (--) NVIDIA(0): option
[34.957] (II) NVIDIA: Using 6144.00 MB of virtual memory for indirect
memory
[34.957] (II) NVIDIA: access.
[34.959] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event
daemon; the daemon
...
[35.115] (II) Initializing extension DRI2
[35.115] (II) Initializing extension GLX
[35.115] (II) Initializing extension GLX
[35.115] (II) Indirect GLX disabled.
Then, in lightdm log an error with segfault appears.
I tried different configs of xorg, so I made a conclusion that nvidia drivers
are built wrong again.
My /etc/X11/xorg.conf.d/10-nvidia.conf:
Section "Files"
ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
ModulePath "/usr/lib/x86_64-linux-gnu/vdpau"
ModulePath "/usr/lib/x86_64-linux-gnu/"
ModulePath "/usr/lib/modules/6.5.0-14-generic/updates/dkms"
ModulePath "/usr/lib/xorg/modules/extensions"
ModulePath "/usr/lib/xorg/modules/drivers"
ModulePath "/usr/lib/xorg/modules/input"
ModulePath "/usr/lib/xorg/modules"
EndSection
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
EndSection
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Dec 21 16:55:06 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/390.157, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 430] [1043:83c3]
InstallationDate: Installed on 2023-12-16 (5 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=ru_RU.UTF-8
LANGUAGE=ru_RU
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=554b729e-40d0-453e-8bb7-a893de671152 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2010
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.name: IC780M-A2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd11/03/2010:br8.15:svnECS:pnIC780M-A2:pvr1.0:rvnECS:rnIC780M-A2:rvr1.0:cvnECS:ct3:cvr:sku:
dmi.product.name: IC780M-A2
dmi.product.version: 1.0
dmi.sys.vendor: ECS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidi
[Touch-packages] [Bug 2047137] Re: nvidia 390 driver from ppa segfault
** Summary changed:
- ubuntu 390 driver from ppa segfault
+ nvidia 390 driver from ppa segfault
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2047137
Title:
nvidia 390 driver from ppa segfault
Status in xorg package in Ubuntu:
New
Bug description:
I tried to build and install package form binaries,
nvidia-graphics-drivers-390 (390.157-0ubuntu8).
Now, I am writing this bug report with nouveau, because I commented blacklist
in /usr/lib/modprobe.d/nvidia-graphics-drivers.conf.
But I want to use nvidia driver like on 22.10 (on 22.04/22.10 it were
working). On 23.04/23.10 it crashes.
There is an error in xorg log, it runs wrong mode, and writes:
[34.950] (II) NVIDIA(0): Validated MetaModes:
[34.950] (II) NVIDIA(0): "DFP-1:nvidia-auto-select"
[34.950] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[34.956] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi"
X config
[34.956] (--) NVIDIA(0): option
[34.957] (II) NVIDIA: Using 6144.00 MB of virtual memory for indirect
memory
[34.957] (II) NVIDIA: access.
[34.959] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event
daemon; the daemon
...
[35.115] (II) Initializing extension DRI2
[35.115] (II) Initializing extension GLX
[35.115] (II) Initializing extension GLX
[35.115] (II) Indirect GLX disabled.
Then, in lightdm log an error with segfault appears.
I tried different configs of xorg, so I made a conclusion that nvidia drivers
are built wrong again.
My /etc/X11/xorg.conf.d/10-nvidia.conf:
Section "Files"
ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
ModulePath "/usr/lib/x86_64-linux-gnu/vdpau"
ModulePath "/usr/lib/x86_64-linux-gnu/"
ModulePath "/usr/lib/modules/6.5.0-14-generic/updates/dkms"
ModulePath "/usr/lib/xorg/modules/extensions"
ModulePath "/usr/lib/xorg/modules/drivers"
ModulePath "/usr/lib/xorg/modules/input"
ModulePath "/usr/lib/xorg/modules"
EndSection
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
EndSection
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Dec 21 16:55:06 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/390.157, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 430] [1043:83c3]
InstallationDate: Installed on 2023-12-16 (5 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=ru_RU.UTF-8
LANGUAGE=ru_RU
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=554b729e-40d0-453e-8bb7-a893de671152 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2010
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.name: IC780M-A2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd11/03/2010:br8.15:svnECS:pnIC780M-A2:pvr1.0:rvnECS:rnIC780M-A2:rvr1.0:cvnECS:ct3:cvr:sku:
dmi.product.name: IC780M-A2
dmi.product.version: 1.0
dmi.sys.vendor: ECS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2047137/+subscriptions
--
Mailing list: https://launchpa
[Touch-packages] [Bug 2047137] [NEW] ubuntu 390 driver from ppa segfault
Public bug reported:
I tried to build and install package form binaries, nvidia-graphics-drivers-390
(390.157-0ubuntu8).
Now, I am writing this bug report with nouveau, because I commented blacklist
in /usr/lib/modprobe.d/nvidia-graphics-drivers.conf.
But I want to use nvidia driver like on 22.10 (on 22.04/22.10 it were working).
On 23.04/23.10 it crashes.
There is an error in xorg log, it runs wrong mode, and writes:
[34.950] (II) NVIDIA(0): Validated MetaModes:
[34.950] (II) NVIDIA(0): "DFP-1:nvidia-auto-select"
[34.950] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[34.956] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi" X
config
[34.956] (--) NVIDIA(0): option
[34.957] (II) NVIDIA: Using 6144.00 MB of virtual memory for indirect memory
[34.957] (II) NVIDIA: access.
[34.959] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon;
the daemon
...
[35.115] (II) Initializing extension DRI2
[35.115] (II) Initializing extension GLX
[35.115] (II) Initializing extension GLX
[35.115] (II) Indirect GLX disabled.
Then, in lightdm log an error with segfault appears.
I tried different configs of xorg, so I made a conclusion that nvidia drivers
are built wrong again.
My /etc/X11/xorg.conf.d/10-nvidia.conf:
Section "Files"
ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
ModulePath "/usr/lib/x86_64-linux-gnu/vdpau"
ModulePath "/usr/lib/x86_64-linux-gnu/"
ModulePath "/usr/lib/modules/6.5.0-14-generic/updates/dkms"
ModulePath "/usr/lib/xorg/modules/extensions"
ModulePath "/usr/lib/xorg/modules/drivers"
ModulePath "/usr/lib/xorg/modules/input"
ModulePath "/usr/lib/xorg/modules"
EndSection
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
EndSection
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Dec 21 16:55:06 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/390.157, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 430] [1043:83c3]
InstallationDate: Installed on 2023-12-16 (5 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=ru_RU.UTF-8
LANGUAGE=ru_RU
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=554b729e-40d0-453e-8bb7-a893de671152 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2010
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.name: IC780M-A2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd11/03/2010:br8.15:svnECS:pnIC780M-A2:pvr1.0:rvnECS:rnIC780M-A2:rvr1.0:cvnECS:ct3:cvr:sku:
dmi.product.name: IC780M-A2
dmi.product.version: 1.0
dmi.sys.vendor: ECS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug false-gpu-hang freeze mantic ubuntu
** Attachment added: "xorg log"
https://bugs.launchpad.net/bugs/2047137/+attachment/5731603/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2047137
Title:
ubuntu 390 driver from ppa segfault
Status in xorg package in Ubuntu:
New
Bug description:
I tried to build and install package form binaries,
nvidia-graphics-drivers-390 (390.157-0ubuntu8).
Now, I am writing this bug report with nouveau, b
[Touch-packages] [Bug 2004011] Re: Checks are not skipped when building esm packages package from source
** Description changed: **Describe the bug** Under the policy, building a deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options However, this is what `override_dh_auto_test` target in `debian/rules` looks like in `heimdal=1.7~git20150920+dfsg-4ubuntu1.16.04.1+esm3`: ``` override_dh_auto_test: $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. Apparently, this has been patched: https://salsa.debian.org/debian/heimdal/-/commit/b1a7b04591873e7d0e88acaf24cc76073ee47fc9 However, the patch did not make its way to ESM packages for 16.04. Is it - possible to cherry-pick this commit to the packages ESM? + possible to cherry-pick this commit to the ESM packages? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2004011 Title: Checks are not skipped when building esm packages package from source Status in heimdal package in Ubuntu: New Bug description: **Describe the bug** Under the policy, building a deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options However, this is what `override_dh_auto_test` target in `debian/rules` looks like in `heimdal=1.7~git20150920+dfsg-4ubuntu1.16.04.1+esm3`: ``` override_dh_auto_test: $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. Apparently, this has been patched: https://salsa.debian.org/debian/heimdal/-/commit/b1a7b04591873e7d0e88acaf24cc76073ee47fc9 However, the patch did not make its way to ESM packages for 16.04. Is it possible to cherry-pick this commit to the ESM packages? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2004011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004011] Re: Checks are not skipped when building esm packages package from source
** Description changed: **Describe the bug** Under the policy, building deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options - However, this is what `override_dh_auto_test` target in `debian/rules` looks like in your case: + However, this is what `override_dh_auto_test` target in `debian/rules` looks like in `heimdal=1.7~git20150920+dfsg-4ubuntu1.16.04.1+esm3`: ``` override_dh_auto_test: - $(MAKE) check + $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. + Apparently, this has been patched: + https://salsa.debian.org/debian/heimdal/-/commit/b1a7b04591873e7d0e88acaf24cc76073ee47fc9 - **Expected behavior** - `override_dh_auto_test` target in `debian/rules` should normally look like this: - ``` - override_dh_auto_test: - ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) - ./run-upstream-testsuite - endif - ``` - This way checks are not run when `DEB_BUILD_OPTIONS="nocheck"` is provided. + However, the patch did not make its way to ESM packages for 16.04. Is it + possible to cherry-pick this commit to the packages? ** Description changed: **Describe the bug** - Under the policy, building deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: + Under the policy, building a deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options However, this is what `override_dh_auto_test` target in `debian/rules` looks like in `heimdal=1.7~git20150920+dfsg-4ubuntu1.16.04.1+esm3`: ``` override_dh_auto_test: $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. Apparently, this has been patched: https://salsa.debian.org/debian/heimdal/-/commit/b1a7b04591873e7d0e88acaf24cc76073ee47fc9 However, the patch did not make its way to ESM packages for 16.04. Is it possible to cherry-pick this commit to the packages? ** Description changed: **Describe the bug** Under the policy, building a deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options However, this is what `override_dh_auto_test` target in `debian/rules` looks like in `heimdal=1.7~git20150920+dfsg-4ubuntu1.16.04.1+esm3`: ``` override_dh_auto_test: $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. Apparently, this has been patched: https://salsa.debian.org/debian/heimdal/-/commit/b1a7b04591873e7d0e88acaf24cc76073ee47fc9 However, the patch did not make its way to ESM packages for 16.04. Is it - possible to cherry-pick this commit to the packages? + possible to cherry-pick this commit to the packages ESM? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2004011 Title: Checks are not skipped when building esm packages package from source Status in heimdal package in Ubuntu: New Bug description: **Describe the bug** Under the policy, building a deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options However, this is what `override_dh_auto_test` target in `debian/rules` looks like in `heimdal=1.7~git20150920+dfsg-4ubuntu1.16.04.1+esm3`: ``` override_dh_auto_test: $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. Apparently, this has been patched: https://salsa.debian.org/debian/heimdal/-/commit/b1a7b04591873e7d0e88acaf24cc76073ee47fc9 However, the patch did not make its way to ESM packages for 16.04. Is it possible to cherry-pick this commit to the packages ESM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2004011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004011] [NEW] Checks are not skipped when building esm packages package from source
Public bug reported: **Describe the bug** Under the policy, building deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options However, this is what `override_dh_auto_test` target in `debian/rules` looks like in your case: ``` override_dh_auto_test: $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. **Expected behavior** `override_dh_auto_test` target in `debian/rules` should normally look like this: ``` override_dh_auto_test: ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) ./run-upstream-testsuite endif ``` This way checks are not run when `DEB_BUILD_OPTIONS="nocheck"` is provided. ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2004011 Title: Checks are not skipped when building esm packages package from source Status in heimdal package in Ubuntu: New Bug description: **Describe the bug** Under the policy, building deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options However, this is what `override_dh_auto_test` target in `debian/rules` looks like in your case: ``` override_dh_auto_test: $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. **Expected behavior** `override_dh_auto_test` target in `debian/rules` should normally look like this: ``` override_dh_auto_test: ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) ./run-upstream-testsuite endif ``` This way checks are not run when `DEB_BUILD_OPTIONS="nocheck"` is provided. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2004011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1955833] [NEW] Crash on the update of the local ICS calendar file
Public bug reported: I start reproducing the crash after my upgrade to Ubuntu 21.10. The crash happens if I setup local ICS calendar file and change something in it outside of evolution. Then the whole evolution calendar service crashes. There is an upstream bug reported which fixes that crash: https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/365 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: evolution-data-server 3.40.4-1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Dec 27 16:42:59 2021 InstallationDate: Installed on 2021-08-18 (130 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: evolution-data-server UpgradeStatus: Upgraded to impish on 2021-12-26 (1 days ago) ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1955833 Title: Crash on the update of the local ICS calendar file Status in evolution-data-server package in Ubuntu: New Bug description: I start reproducing the crash after my upgrade to Ubuntu 21.10. The crash happens if I setup local ICS calendar file and change something in it outside of evolution. Then the whole evolution calendar service crashes. There is an upstream bug reported which fixes that crash: https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/365 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: evolution-data-server 3.40.4-1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Dec 27 16:42:59 2021 InstallationDate: Installed on 2021-08-18 (130 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: evolution-data-server UpgradeStatus: Upgraded to impish on 2021-12-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1955833/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 874438] Re: [USB-Audio - USB Device 0x46d:0x802, recording] Sound is distorted
I have the same problem. ** Changed in: alsa-driver (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/874438 Title: [USB-Audio - USB Device 0x46d:0x802, recording] Sound is distorted Status in alsa-driver package in Ubuntu: Incomplete Bug description: In natty the sound on this device was flawless. On a fresh install of Oneiric I sound more like Alvin and the Chipmunks. I've tried plugging in a headset on the off chance that it was a device driver at fault no joy. So it can only be a codec (but you'd have more reports) or an issue with the onboard soundcard driver. I'll have and tinker and report any improvements here. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: davmor21574 F pulseaudio /dev/snd/controlC0: davmor21574 F pulseaudio Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xdfef8000 irq 22' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18493662,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'U0x46d0x802'/'USB Device 0x46d:0x802 at usb-:00:02.1-3.1, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0802' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6144 Mono: Capture 5711 [93%] [28.30dB] [on] Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xdffbc000 irq 43' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 4 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Fri Oct 14 17:53:17 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:U0x46d0x802 successful Symptom_Card: Manhattan HDMI Audio [Mobility Radeon HD 5000 Series] - HD-Audio Generic Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:U0x46d0x802 successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - USB Device 0x46d:0x802, recording] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: N61P-S dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd09/18/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnN61P-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877717] Re: Sound stop working after wakeup
root@svmk-laptop:/var/log# grep pulseaudio syslog May 10 16:08:31 svmk-laptop pulseaudio[87919]: Error opening PCM device front:0: Нет такого файла или каталога ** Attachment added: "Output of command `pacmd list`" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877717/+attachment/5369385/+files/pacmd_list.out.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877717 Title: Sound stop working after wakeup Status in pulseaudio package in Ubuntu: New Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 I don't know how to reproduce this bug. Sometimes after notebook wakup sound stop working. pulseaudio -k fixes this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1925 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 9 15:43:32 2020 InstallationDate: Installed on 2018-04-03 (766 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to focal on 2020-04-24 (14 days ago) dmi.bios.date: 06/29/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83C9 dmi.board.vendor: HP dmi.board.version: 32.59 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd06/29/2017:svnHP:pnHPEnvy:pvrType1ProductConfigId:rvnHP:rn83C9:rvr32.59:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV NOTEBOOK dmi.product.name: HP Envy dmi.product.sku: 2PQ29EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877717] [NEW] Sound stop working after wakeup
Public bug reported: Description:Ubuntu 20.04 LTS Release:20.04 I don't know how to reproduce this bug. Sometimes after notebook wakup sound stop working. pulseaudio -k fixes this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1925 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 9 15:43:32 2020 InstallationDate: Installed on 2018-04-03 (766 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to focal on 2020-04-24 (14 days ago) dmi.bios.date: 06/29/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83C9 dmi.board.vendor: HP dmi.board.version: 32.59 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd06/29/2017:svnHP:pnHPEnvy:pvrType1ProductConfigId:rvnHP:rn83C9:rvr32.59:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV NOTEBOOK dmi.product.name: HP Envy dmi.product.sku: 2PQ29EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877717 Title: Sound stop working after wakeup Status in pulseaudio package in Ubuntu: New Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 I don't know how to reproduce this bug. Sometimes after notebook wakup sound stop working. pulseaudio -k fixes this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1925 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 9 15:43:32 2020 InstallationDate: Installed on 2018-04-03 (766 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to focal on 2020-04-24 (14 days ago) dmi.bios.date: 06/29/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83C9 dmi.board.vendor: HP dmi.board.version: 32.59 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd06/29/2017:svnHP:pnHPEnvy:pvrType1ProductConfigId:rvnHP:rn83C9:rvr32.59:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV NOTEBOOK dmi.product.name: HP Envy dmi.product.sku: 2PQ29EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1071941] Re: apport-cli asks me to input localized key / letter and can't understand my answer
So many bugs in Ubuntu, and become more with every new LTS release, so the one good sulution for me is just removing all buggy components instead of testing and reporting (because nobody has time to fix it), even if Cannonical promote it as essential. No big problem really, but programs, which require input answers from user in non-latin Unicode, are not very smart programs, because: 1) problems with Unicode decoding are always possible (by developer mistake), 2) user can have problem with input of non-latin symbols by keyboard (by some other bug). Good solution is: expects answers hotkeys in latin (English) short strings (like `Да[Y]/Нет[N]:` for `Yes[Y]/No[N]:`), even you show localized message. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1071941 Title: apport-cli asks me to input localized key / letter and can't understand my answer Status in apport package in Ubuntu: Incomplete Bug description: 1) The release of Ubuntu you are using $ lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 2) The version of the package you are using $ apt-cache policy apport apport: Установлен: 2.0.1-0ubuntu14 Кандидат: 2.0.1-0ubuntu14 Таблица версий: *** 2.0.1-0ubuntu14 0 500 http://mirror.yandex.ru/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 2.0.1-0ubuntu5 0 500 http://mirror.yandex.ru/ubuntu/ precise/main i386 Packages 3) What you expected to happen I start in terminal simple command: apport-cli (under x-environment, Unity 2D/3D, with Russian localization and UTF-8 default encoding). $ apport-cli *** Отправить отчёт об ошибке разработчикам? После того, как отчёт будет отправлен, заполните форму в автоматически открывшемся окне браузера. Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (2.6 MB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо И: Отменить и игнорировать будущие сбои в этой версии программы Т: Отменить Пожалуйста, выберите (О/П/С/И/Т): Т До свидания! $ It is what I expect. 4) What happened instead $ apport-cli *** Отправить отчёт об ошибке разработчикам? После того, как отчёт будет отправлен, заполните форму в автоматически открывшемся окне браузера. Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (4.7 MB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо И: Отменить и игнорировать будущие сбои в этой версии программы Т: Отменить Пожалуйста, выберите (О/П/С/И/Т): Т /usr/bin/apport-cli:84: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal return self.keys.index(response[0].upper()) + 1 Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (4.7 MB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо И: Отменить и игнорировать будущие сбои в этой версии программы Т: Отменить Пожалуйста, выберите (О/П/С/И/Т): Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (4.7 MB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо И: Отменить и игнорировать будущие сбои в этой версии программы Т: Отменить Пожалуйста, выберите (О/П/С/И/Т): ^C $ When I inputed Russian letter 'Т', which means Cancel (Отменить), it shows me warning: /usr/bin/apport-cli:84: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal return self.keys.index(response[0].upper()) + 1 Then it interprets my answer as 2 bytes (2 letters / symbols), I think it because of Unicode. It shows me double question, and the only thing what I can do: break program by pressing Ctrl+C (^C as you can see above). P. S. : I always hated people, who allows programs to use non-latin / non-english hotkeys. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apport 2.0.1-0ubuntu14 Uname: Linux 3.5.7-zen-proxym-3 i686 ApportLog: ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 Date: Sat Oct 27 02:18:28 2012 InstallationMedia: Ubuntu-Studio 10.10 "Maverick Meerkat" - Release i386 (20101008) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to precise on 2012-10-23 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1071941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1071941] Re: apport-cli asks me to input localized key / letter and can't understand my answer
So, you wait till it is unsupported version... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1071941 Title: apport-cli asks me to input localized key / letter and can't understand my answer Status in apport package in Ubuntu: Incomplete Bug description: 1) The release of Ubuntu you are using $ lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 2) The version of the package you are using $ apt-cache policy apport apport: Установлен: 2.0.1-0ubuntu14 Кандидат: 2.0.1-0ubuntu14 Таблица версий: *** 2.0.1-0ubuntu14 0 500 http://mirror.yandex.ru/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 2.0.1-0ubuntu5 0 500 http://mirror.yandex.ru/ubuntu/ precise/main i386 Packages 3) What you expected to happen I start in terminal simple command: apport-cli (under x-environment, Unity 2D/3D, with Russian localization and UTF-8 default encoding). $ apport-cli *** Отправить отчёт об ошибке разработчикам? После того, как отчёт будет отправлен, заполните форму в автоматически открывшемся окне браузера. Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (2.6 MB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо И: Отменить и игнорировать будущие сбои в этой версии программы Т: Отменить Пожалуйста, выберите (О/П/С/И/Т): Т До свидания! $ It is what I expect. 4) What happened instead $ apport-cli *** Отправить отчёт об ошибке разработчикам? После того, как отчёт будет отправлен, заполните форму в автоматически открывшемся окне браузера. Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (4.7 MB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо И: Отменить и игнорировать будущие сбои в этой версии программы Т: Отменить Пожалуйста, выберите (О/П/С/И/Т): Т /usr/bin/apport-cli:84: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal return self.keys.index(response[0].upper()) + 1 Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (4.7 MB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо И: Отменить и игнорировать будущие сбои в этой версии программы Т: Отменить Пожалуйста, выберите (О/П/С/И/Т): Что вы хотите сделать? Возможные варианты: О: Отправить отчёт (4.7 MB) П: Просмотреть отчёт С: Сохранить файл отчёта для последующей отправки или копирования куда-либо И: Отменить и игнорировать будущие сбои в этой версии программы Т: Отменить Пожалуйста, выберите (О/П/С/И/Т): ^C $ When I inputed Russian letter 'Т', which means Cancel (Отменить), it shows me warning: /usr/bin/apport-cli:84: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal return self.keys.index(response[0].upper()) + 1 Then it interprets my answer as 2 bytes (2 letters / symbols), I think it because of Unicode. It shows me double question, and the only thing what I can do: break program by pressing Ctrl+C (^C as you can see above). P. S. : I always hated people, who allows programs to use non-latin / non-english hotkeys. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apport 2.0.1-0ubuntu14 Uname: Linux 3.5.7-zen-proxym-3 i686 ApportLog: ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 Date: Sat Oct 27 02:18:28 2012 InstallationMedia: Ubuntu-Studio 10.10 "Maverick Meerkat" - Release i386 (20101008) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to precise on 2012-10-23 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1071941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850159] Re: gnome-control-center reports Ethernet Connection Failure while Connection success
Can't explain better, but I found root cause. So, full steps to reproduce: 1) sudo service NetworkManager stop 2) sudo wpa_supplicant -c /etc/wpa_supplicant/wired.conf -i eth1 -D wired 3) sudo dhclient eth1 4) see in output "ls: cannot access '/run/systemd/resolved.conf.d/isc-dhcp-v6-***.conf': No such file or directory" 5) check ifconfig that only IPv4 address was received Work-around: Disable IPv6 for Ethernet ** Summary changed: - gnome-control-center reports Ethernet Connection Failure while Connection success + dhclient can't obtain IPv6 addr -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1850159 Title: dhclient can't obtain IPv6 addr Status in network-manager package in Ubuntu: Incomplete Bug description: gnome-control-center reports Ethernet Connection Failure with TLS Authentication 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu2 3) Show Connected for Wired Connection 4) Show Disconnected for Wired Connection ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 17:06:43 2019 InstallationDate: Installed on 2019-08-01 (88 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850159] Re: gnome-control-center reports Ethernet Connection Failure while Connection success
Sorry for wrong package name changed to network-manager ** Package changed: gnome-control-center (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1850159 Title: gnome-control-center reports Ethernet Connection Failure while Connection success Status in network-manager package in Ubuntu: Incomplete Bug description: gnome-control-center reports Ethernet Connection Failure with TLS Authentication 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu2 3) Show Connected for Wired Connection 4) Show Disconnected for Wired Connection ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 17:06:43 2019 InstallationDate: Installed on 2019-08-01 (88 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
There is a bug in Samba >= 4.8: https://bugzilla.samba.org/show_bug.cgi?id=13939 A fix for samba is needed if negotiate authorization still does not work. Sympthom is a window asking for some password. ** Bug watch added: Samba Bugzilla #13939 https://bugzilla.samba.org/show_bug.cgi?id=13939 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Bionic: Fix Released Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every join, instead of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+subscriptions -- Mailing list: https://launch
[Touch-packages] [Bug 1832060] [NEW] Backport "add an option that allows rewinds to be disabled"
Public bug reported: PulseAudio git master added an option that allows rewinds to be disabled. I backported it to v12.2, the patch is here: https://gitlab.com/nixtux-packaging/pulseaudio- ubuntu/blob/master/pulseaudio-12.2/debian/patches/0001-Backport-add-an- option-that-allows-rewinds-to-be-dis.patch This will help PulseEffects that is being packaged in https://bugs.launchpad.net/ubuntu/+bug/1832059 by fixing crackling sound when changing the volume level. It would be good to have this patches applied in Eoan if PulseAudio 13.0 does not get to it. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Patch added: "0001-Backport-add-an-option-that-allows-rewinds-to-be-dis.patch" https://bugs.launchpad.net/bugs/1832060/+attachment/5269487/+files/0001-Backport-add-an-option-that-allows-rewinds-to-be-dis.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1832060 Title: Backport "add an option that allows rewinds to be disabled" Status in pulseaudio package in Ubuntu: New Bug description: PulseAudio git master added an option that allows rewinds to be disabled. I backported it to v12.2, the patch is here: https://gitlab.com/nixtux-packaging/pulseaudio- ubuntu/blob/master/pulseaudio-12.2/debian/patches/0001-Backport-add- an-option-that-allows-rewinds-to-be-dis.patch This will help PulseEffects that is being packaged in https://bugs.launchpad.net/ubuntu/+bug/1832059 by fixing crackling sound when changing the volume level. It would be good to have this patches applied in Eoan if PulseAudio 13.0 does not get to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1832060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805203] Re: libcurl3-gnutls in cosmic breaks git with Azure DevOps
Faced same issue and solved by downgrading. To avoid upgrade of package and adding bionic-security to sources list One can do: 1. Manually download package from https://packages.ubuntu.com/bionic/libcurl3-gnutls 2. Install libcurl3-gnutls with dpkg -i libcurl3-gnutls*.deb 3. Lock package version with apt-mark hold libcurl3-gnutls 4. Once update will be pushed just unlock package with apt-mark unhold libcurl3-gnutls -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1805203 Title: libcurl3-gnutls in cosmic breaks git with Azure DevOps Status in curl package in Ubuntu: Confirmed Bug description: The version of libcurl3-gnutls in cosmic (7.61.0) causes authentication failures with Azure DevOps. This causes all git operations with the server to fail (eg clone, push, pull). For details see this curl bug: https://github.com/curl/curl/pull/2754 To work around this I downgraded libcurl3-gnutls to the version in bionic (7.58.0) From the curl change list https://curl.haxx.se/changes.html#7_61_1, this issue should be fixed in package version 7.61.1 or above. Request: please upgrade package in cosmic for libcurl3-gnutls to 7.61.1 or above Details: 1 - Ubuntu 18.10 2 - libcurl3-gnutls (7.61.0-1ubuntu2.2 and others) 3 - Be able to git clone from an Azure DevOps repository using a Personal Access Token 4 - git operations fail to authenticate Thank you, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1805203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS
*** This bug is a duplicate of bug 1683383 *** https://bugs.launchpad.net/bugs/1683383 ! SOLUTION ! For myself I created temporary hack allowing to switch Keyboard layouts (en<->ru) by Ctrl+Shift on key release. My method does not interfere with other shortcuts. I use it myself on daily basis. It's simple Python script which listen to Ctrl+Shift key combination and switch layout on release. It can be downloaded here https://drive.google.com/file/d/1IvgvLFwe2HoGtEzuQnrUoAnEZk1ZCcSw/view?usp=sharing Please read instructions in ReadMe.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1720364 Title: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS Status in MATE Desktop: New Status in ubuntu-mate: New Status in X.Org X server: Confirmed Status in marco package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Status in xorg-hwe-16.04 package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: marco 1.18.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Fri Sep 29 16:18:02 2017 InstallationDate: Installed on 2017-08-26 (33 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) SourcePackage: marco UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1720364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814162] [NEW] Xorg freeze
Public bug reported: When I lock my machine on the latest ubuntu version 4.15.0-44-generic, it turns my display completely black and unresponsive. This is only when I have my dock (with external displays in). After it freezes however, removing the dock has no effect. Booting back into 4.15.0-43-generic has fixed the problem so this is a regression bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 14:25:01 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081c] InstallationDate: Installed on 2018-10-17 (106 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814162 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: When I lock my machine on the latest ubuntu version 4.15.0-44-generic, it turns my display completely black and unresponsive. This is only when I have my dock (with external displays in). After it freezes however, removing the dock has no effect. Booting back into 4.15.0-43-generic has fixed the problem so this is a regression bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 14:25:01 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081c] InstallationDate: Installed on 2018-10-17 (106 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2018 dmi.bios.vendor: Dell Inc. dmi.bios.ve
[Touch-packages] [Bug 1814162] Re: Xorg freeze
Sorry I realized this bug is misleading with the version listed, the bug is for version: 4.15.0-44-generic. I am booted into 43 to fix the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814162 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: When I lock my machine on the latest ubuntu version 4.15.0-44-generic, it turns my display completely black and unresponsive. This is only when I have my dock (with external displays in). After it freezes however, removing the dock has no effect. Booting back into 4.15.0-43-generic has fixed the problem so this is a regression bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 14:25:01 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081c] InstallationDate: Installed on 2018-10-17 (106 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
After some time CPU load grew to 100% again. Have found another workaround which is working so far (disabling nvidia rules for udev): sudo mv /lib/udev/rules.d/71-nvidia.rules /lib/udev/rules.d/71-nvidia.save (and then restart). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Confirmed Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
gaetan-quentin's workaround helped me for now: systemctl stop systemd-udevd sudo apt remove *nvidia-compute-utils* systemctl start systemd-udevd (Lenovo P51) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Confirmed Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1749398] [NEW] Update libva: 2.0.0 --> 2.1.1 before release 18.04 bionic
Public bug reported: Libva 2.1.0 has been released: https://github.com/intel/libva/releases ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libva2 2.0.0-2 Uname: Linux 4.14.0-18.2-liquorix-amd64 x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Wed Feb 14 11:46:06 2018 InstallationDate: Installed on 2017-08-28 (169 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libva UpgradeStatus: Upgraded to bionic on 2018-02-08 (5 days ago) ** Affects: libva (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1749398 Title: Update libva: 2.0.0 --> 2.1.1 before release 18.04 bionic Status in libva package in Ubuntu: New Bug description: Libva 2.1.0 has been released: https://github.com/intel/libva/releases ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libva2 2.0.0-2 Uname: Linux 4.14.0-18.2-liquorix-amd64 x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Wed Feb 14 11:46:06 2018 InstallationDate: Installed on 2017-08-28 (169 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libva UpgradeStatus: Upgraded to bionic on 2018-02-08 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1749398/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438014] Re: gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts
I'm also using "Artful Aardwark" got many crashes with different circumstances. After some work in the background. When I'm opening and try to interact: - Trying to open Preferences - Trying to right-click on highlighted link to select "Open Link" (crash just after right click) - Trying to switch tab -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1438014 Title: gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I put my laptop to sleep for an hour or so; when I restored it, gnome- terminal had crashed. It did not do this the previous time I suspended my laptop today, so I doubt that's immediately related. This crash can be reproduced by setting a shortcut in preferences. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 30 00:19:43 2015 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2014-02-03 (419 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f98e2afbf1f : testb $0x4,0x16(%rax) PC (0x7f98e2afbf1f) ok source "$0x4" ok destination "0x16(%rax)" (0xbcae) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel (widget=0x2580c30) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382 window_group_cleanup_grabs (group=, window=window@entry=0x252a230) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110 gtk_window_group_add_window (window_group=0x27e5c40, window=0x252a230) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169 gtk_window_set_transient_for (window=0x252a230, parent=0x23ac7d0) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindow.c:3134 Title: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1438014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1739509] [NEW] Why was gstreamer0.10 dropped from Ubuntu
Public bug reported: Why was gstreamer0.10 dropped from Ubuntu? It is still available in debian and many applications do use it https://packages.debian.org/search?keywords=libgstreamer0.10&searchon=names&suite=all§ion=all , e.g. proprietary eTXT Antiplagiat. ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1739509 Title: Why was gstreamer0.10 dropped from Ubuntu Status in gstreamer0.10 package in Ubuntu: New Bug description: Why was gstreamer0.10 dropped from Ubuntu? It is still available in debian and many applications do use it https://packages.debian.org/search?keywords=libgstreamer0.10&searchon=names&suite=all§ion=all , e.g. proprietary eTXT Antiplagiat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1739509/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731550] Re: module-switch-on-connect switches to virtual devices
I don't think that Ubuntu developers can do anything with it, they will not disable propper handling of USB dongles to allow PulseEffects work properly and solve https://github.com/wwmm/pulseeffects/issues/99 ** Bug watch added: github.com/wwmm/pulseeffects/issues #99 https://github.com/wwmm/pulseeffects/issues/99 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1731550 Title: module-switch-on-connect switches to virtual devices Status in pulseaudio package in Ubuntu: Confirmed Bug description: The module-switch-on-connect module that has been enabled by default in Artful is causing virtual devices added by PulseEffects (https://github.com/wwmm/pulseeffects) to be activated and set to the default/failsafe device. This also changes which device the system volume control changes. It should only automatically switch when a physical audio device is plugged in. If there is no way to detect this automatically, then I would say this should not be the default configuration, or it should be added as an optional preference. In the meantime, I have worked around the issue by copying /etc/pulse/default.pa into ~/.config/pulse and commenting out loading the module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1731550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650634] Re: when installing systemd, it creates /run/nologin preventing all users from logging in.
I got this again. Commented out the line auth requisite pam_nologin.so in /etc/pam.d/login Now /run/nologin must be ignored and do not prevent the system from booting up correctly, but this bug must be marked as CRITICAL, I think. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1650634 Title: when installing systemd, it creates /run/nologin preventing all users from logging in. Status in systemd: New Status in systemd package in Ubuntu: Confirmed Status in systemd package in Suse: Unknown Bug description: How to replicate: sudo apt-get install systemd wait for 5 minutes check to see if /run/nologin appears. If it does the bug is present. See https://ubuntuforums.org/showthread.php?t=2327330 I ran this command via ansible on all of my servers. Then I could no longer log into any of them. Pretty big bug in my opinion. Please fix. -Tim ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd 204-5ubuntu20.20 ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39 Uname: Linux 3.13.0-105-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: KDE Date: Fri Dec 16 12:03:55 2016 InstallationDate: Installed on 2014-04-21 (970 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1650634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650634] Re: when installing systemd, it creates /run/nologin preventing all users from logging in.
Thank you, today my Ubuntu 16.04 booted into the maintenance mode and systemctl --failed showed only nfs-resolvd.service. I made # systemctl restart ssh then I got: "System is booting up. See pam_nologin(8)" Authentication failed. # rm -fv /run/nologin solved the issue. I ran # apt install --reinstall systemd and /run/nologin did not appear again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1650634 Title: when installing systemd, it creates /run/nologin preventing all users from logging in. Status in systemd: New Status in systemd package in Ubuntu: Confirmed Status in systemd package in Suse: Unknown Bug description: How to replicate: sudo apt-get install systemd wait for 5 minutes check to see if /run/nologin appears. If it does the bug is present. See https://ubuntuforums.org/showthread.php?t=2327330 I ran this command via ansible on all of my servers. Then I could no longer log into any of them. Pretty big bug in my opinion. Please fix. -Tim ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd 204-5ubuntu20.20 ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39 Uname: Linux 3.13.0-105-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: KDE Date: Fri Dec 16 12:03:55 2016 InstallationDate: Installed on 2014-04-21 (970 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1650634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710666] Re: No resolution until manually adding a nameserver to resolv.conf
Oh, sorry! Not $ sudo systemctl restart systemd-networkd but $ sudo systemctl restart systemd-resolved -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710666 Title: No resolution until manually adding a nameserver to resolv.conf Status in systemd package in Ubuntu: New Bug description: I have no resolution until I manually add a `nameserver 8.8.8.8` to `/run/resolvconf/resolv.conf`. And if `resolvconf` is not installed, I don't know how to add a nameserver. So I keep that installed. I'm using Network Manager and it should take care of adding nameservers. I don't know where what is going wrong. I'm willing to send any necessary info from this system. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Aug 14 18:58:10 2017 InstallationDate: Installed on 2010-10-12 (2498 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Supermicro X10SRA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-13-generic root=/dev/mapper/root ro nomdmonddf nomdmonisw nomodeset SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-04-29 (107 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X10SRA dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710666] Re: No resolution until manually adding a nameserver to resolv.conf
Post the output of $ sudo systemctl status systemd-resolved And try: $ sudo systemctl restart systemd-networkd Will DNs resolution start working after it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710666 Title: No resolution until manually adding a nameserver to resolv.conf Status in systemd package in Ubuntu: New Bug description: I have no resolution until I manually add a `nameserver 8.8.8.8` to `/run/resolvconf/resolv.conf`. And if `resolvconf` is not installed, I don't know how to add a nameserver. So I keep that installed. I'm using Network Manager and it should take care of adding nameservers. I don't know where what is going wrong. I'm willing to send any necessary info from this system. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Aug 14 18:58:10 2017 InstallationDate: Installed on 2010-10-12 (2498 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Supermicro X10SRA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-13-generic root=/dev/mapper/root ro nomdmonddf nomdmonisw nomodeset SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-04-29 (107 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X10SRA dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710666] Re: No resolution until manually adding a nameserver to resolv.conf
NetworkManager does not take care of DNS resolution, in Ubuntu 17.10 systemd-resolved does it, dnsmasq did it in older Ubuntu releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710666 Title: No resolution until manually adding a nameserver to resolv.conf Status in systemd package in Ubuntu: New Bug description: I have no resolution until I manually add a `nameserver 8.8.8.8` to `/run/resolvconf/resolv.conf`. And if `resolvconf` is not installed, I don't know how to add a nameserver. So I keep that installed. I'm using Network Manager and it should take care of adding nameservers. I don't know where what is going wrong. I'm willing to send any necessary info from this system. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Aug 14 18:58:10 2017 InstallationDate: Installed on 2010-10-12 (2498 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Supermicro X10SRA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-13-generic root=/dev/mapper/root ro nomdmonddf nomdmonisw nomodeset SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-04-29 (107 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X10SRA dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711474] Re: graphical session and network not start up due to root FS being mounted read-only
Upgraded to artful proposed, now NetworkManager does start, but the system still does not boot without /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="rw" I made btrfs check, btrfs rescue, btrfs balance, nothing helped. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1711474 Title: graphical session and network not start up due to root FS being mounted read-only Status in systemd package in Ubuntu: New Bug description: Kubuntu 17.10, fresh install $ systemctl --version systemd 233 Graphical session (sddm.service), systemd-resolved.service and NetworkManager.service are not loaded due to system root being mounted read-only $ journalctl -b0 авг 18 01:27:45 Kseniya-Desktop kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ This is the default kernel command line, ro means that the root filesystem must be mounted read-only, then fsck is believed to be permormed, after what the FS must be remounted rw (read-write) But in my system (Ubuntu 17.10) the /home is mouned rw, but the root is still ro. I added to /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="rw" Now my kernel command line is: авг 18 01:27:45 Kseniya-Desktop kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw No the root fs is mounted rw and sddm.service starts the graphical session automatically. BUT: NetworkManager.service is not started automatically and should be started manually (sudo systemctl start NetworkManager) Due to network offline, network fileshares are not mounted. I also noticed that there is no dependency from fsck in -.mount, but there is in home.mount $ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sdc1 during installation UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e / btrfs subvol=@,defaults,compress=lzo 0 2 # /home was on /dev/sdc1 during installation UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e /home btrfs defaults,discard,compress=lzo,subvol=@home 0 3 # swap was on /dev/sdc2 during installation UUID=cd2ba3e8-5ec9-49b3-aa2d-79082a8b8012 noneswapsw 0 0 -- $ cat /run/systemd/generator/-.mount # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) Before=local-fs.target [Mount] Where=/ What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e Type=btrfs Options=subvol=@,defaults,compress=lzo -- $ cat /run/systemd/generator/home.mount # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) Before=local-fs.target Requires=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service After=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service [Mount] Where=/home What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e Type=btrfs Options=defaults,discard,compress=lzo,subvol=@home ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: KDE Date: Fri Aug 18 01:30:46 2017 InstallationDate: Installed on 2017-07-23 (25 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) MachineType: Gigabyte Technology Co., Ltd. GA-A75M-DS2 ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no username) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-A75M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd03/27/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-DS2:pvr:rvnGigabyteTechnologyCo.,Ltd.:
[Touch-packages] [Bug 1711474] Re: graphical session and network not start up due to root FS being mounted read-only
Forgot to wrte that I do # mount -o remount,rw / # systemctl restart sddm systemd-resolved NetworkManager and after that I get access to fully working graphical session (except of network-dependant mounts) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1711474 Title: graphical session and network not start up due to root FS being mounted read-only Status in systemd package in Ubuntu: New Bug description: Kubuntu 17.10, fresh install $ systemctl --version systemd 233 Graphical session (sddm.service), systemd-resolved.service and NetworkManager.service are not loaded due to system root being mounted read-only $ journalctl -b0 авг 18 01:27:45 Kseniya-Desktop kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ This is the default kernel command line, ro means that the root filesystem must be mounted read-only, then fsck is believed to be permormed, after what the FS must be remounted rw (read-write) But in my system (Ubuntu 17.10) the /home is mouned rw, but the root is still ro. I added to /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="rw" Now my kernel command line is: авг 18 01:27:45 Kseniya-Desktop kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw No the root fs is mounted rw and sddm.service starts the graphical session automatically. BUT: NetworkManager.service is not started automatically and should be started manually (sudo systemctl start NetworkManager) Due to network offline, network fileshares are not mounted. I also noticed that there is no dependency from fsck in -.mount, but there is in home.mount $ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sdc1 during installation UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e / btrfs subvol=@,defaults,compress=lzo 0 2 # /home was on /dev/sdc1 during installation UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e /home btrfs defaults,discard,compress=lzo,subvol=@home 0 3 # swap was on /dev/sdc2 during installation UUID=cd2ba3e8-5ec9-49b3-aa2d-79082a8b8012 noneswapsw 0 0 -- $ cat /run/systemd/generator/-.mount # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) Before=local-fs.target [Mount] Where=/ What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e Type=btrfs Options=subvol=@,defaults,compress=lzo -- $ cat /run/systemd/generator/home.mount # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) Before=local-fs.target Requires=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service After=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service [Mount] Where=/home What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e Type=btrfs Options=defaults,discard,compress=lzo,subvol=@home ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: KDE Date: Fri Aug 18 01:30:46 2017 InstallationDate: Installed on 2017-07-23 (25 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) MachineType: Gigabyte Technology Co., Ltd. GA-A75M-DS2 ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no username) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-A75M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd03/27/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-DS2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-DS
[Touch-packages] [Bug 1711474] [NEW] graphical session and network not start up due to root FS being mounted read-only
Public bug reported: Kubuntu 17.10, fresh install $ systemctl --version systemd 233 Graphical session (sddm.service), systemd-resolved.service and NetworkManager.service are not loaded due to system root being mounted read-only $ journalctl -b0 авг 18 01:27:45 Kseniya-Desktop kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ This is the default kernel command line, ro means that the root filesystem must be mounted read-only, then fsck is believed to be permormed, after what the FS must be remounted rw (read-write) But in my system (Ubuntu 17.10) the /home is mouned rw, but the root is still ro. I added to /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="rw" Now my kernel command line is: авг 18 01:27:45 Kseniya-Desktop kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw No the root fs is mounted rw and sddm.service starts the graphical session automatically. BUT: NetworkManager.service is not started automatically and should be started manually (sudo systemctl start NetworkManager) Due to network offline, network fileshares are not mounted. I also noticed that there is no dependency from fsck in -.mount, but there is in home.mount $ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sdc1 during installation UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e / btrfs subvol=@,defaults,compress=lzo 0 2 # /home was on /dev/sdc1 during installation UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e /home btrfs defaults,discard,compress=lzo,subvol=@home 0 3 # swap was on /dev/sdc2 during installation UUID=cd2ba3e8-5ec9-49b3-aa2d-79082a8b8012 noneswapsw 0 0 -- $ cat /run/systemd/generator/-.mount # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) Before=local-fs.target [Mount] Where=/ What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e Type=btrfs Options=subvol=@,defaults,compress=lzo -- $ cat /run/systemd/generator/home.mount # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) Before=local-fs.target Requires=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service After=systemd-fsck@dev-disk-by\x2duuid-87e60ca5\x2d1b9f\x2d4790\x2d8b9e\x2d6394b9d0a40e.service [Mount] Where=/home What=/dev/disk/by-uuid/87e60ca5-1b9f-4790-8b9e-6394b9d0a40e Type=btrfs Options=defaults,discard,compress=lzo,subvol=@home ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: KDE Date: Fri Aug 18 01:30:46 2017 InstallationDate: Installed on 2017-07-23 (25 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) MachineType: Gigabyte Technology Co., Ltd. GA-A75M-DS2 ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no username) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.12.0-11-generic root=UUID=87e60ca5-1b9f-4790-8b9e-6394b9d0a40e ro rootflags=subvol=@ rw SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-A75M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd03/27/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-DS2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75M-DS2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1711474 Title: graphical session and network not start up due to root FS being mounted read-only Status in systemd package in Ubuntu: New Bug description: Kubuntu 17.10, fresh install $ systemctl --version systemd 233 Graphical session (sddm.service), systemd-resolved.service and
[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text
Confirm the bug with the dafault Xubuntu theme. $ env GTK_THEME=Abiword solves the problem, no more flickering -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: In Progress Status in abiword package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Invalid Status in abiword source package in Xenial: Confirmed Status in gtk+3.0 source package in Xenial: Confirmed Status in lubuntu-artwork source package in Xenial: Invalid Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround for Ubuntu 16.04 LTS === 1. Open the Lubuntu menu. 2. Open Preferences>Customize Look and Feel 3. Change the theme to something other than Lubuntu-default or Lubuntu-dark-panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: abiword 3.0.1-6 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Apr 24 16:12:14 2016 ExecutablePath: /usr/bin/abiword InstallationDate: Installed on 2016-04-22 (2 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: abiword UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/1574278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1564252] Re: [HDA-Intel - HDA Intel PCH, recording] No sound from external microphone on headset
Fix proposed in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539843 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1564252 Title: [HDA-Intel - HDA Intel PCH, recording] No sound from external microphone on headset Status in alsa-driver package in Ubuntu: Confirmed Bug description: No sound from external microphone on headset. Work well in windows. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2273 F pulseaudio /dev/snd/pcmC1D0p: ubuntu 2273 F...m pulseaudio /dev/snd/controlC1: ubuntu 2273 F pulseaudio CasperVersion: 1.368 CurrentDesktop: Unity Date: Thu Mar 31 06:18:30 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2273 F pulseaudio /dev/snd/controlC1: ubuntu 2273 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JM.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N551JM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1564252/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
I can confirm this, have the same behaviour on my new Dell XPS 15 9560. So sad to see this still hasn't been fixed... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in alsa-driver package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1610772] Re: [drm] stuck on render ring
I don't know, sorry Mikhail Sent from my Samsung Galaxy smartphone. Original message From: "Christopher M. Penalver" Date: 2016-09-17 11:15 PM (GMT-05:00) To: mikhail.kara...@gmail.com Subject: [Bug 1610772] Re: [drm] stuck on render ring Mikhail, to clarify, what kernel version were you using in Ubuntu 14.04 specifically when this didn't happen? ** Tags added: regression-release ** Tags added: needs-bisect -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1610772 Title: [drm] stuck on render ring Status in xorg package in Ubuntu: Incomplete Bug description: The problem is similiar to the one discrabed in #1547800 It was happen once in a while. Now it always happens when returning from sleep. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/sda6: clean, 278496/3727360 files, 2012554/14884352 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Aug 7 22:04:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:179b] InstallationDate: Installed on 2016-06-26 (42 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP EliteBook 8470p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=1126bf38-027a-410d-a905-5dbbd05a6b4d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.45 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8470p dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Jul 25 07:40:00 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 5236 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1610772/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1610772 Title: [drm] stuck on render ring Status in xorg package in Ubuntu: Incomplete Bug description: The problem is similiar to the one discrabed in #1547800 It was happen once in a while. Now it always happens when returning from sleep. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/sda6: clean, 278496/3727360 files, 2012554/14884352 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Aug 7 22:04:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd
Re: [Touch-packages] [Bug 1610772] Re: [drm] stuck on render ring
I had 14 before and had no problem Sent from my Samsung Galaxy smartphone. Original message From: "Christopher M. Penalver" Date: 2016-09-17 11:08 AM (GMT-05:00) To: mikhail.kara...@gmail.com Subject: [Bug 1610772] Re: [drm] stuck on render ring Mihail, was this an issue in a Ubuntu release prior to 16.04? ** Tags removed: bios-outdated-f.64 ** Tags added: latest-bios-f.65 ** Changed in: xorg (Ubuntu) Importance: Low => Medium -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1610772 Title: [drm] stuck on render ring Status in xorg package in Ubuntu: Incomplete Bug description: The problem is similiar to the one discrabed in #1547800 It was happen once in a while. Now it always happens when returning from sleep. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/sda6: clean, 278496/3727360 files, 2012554/14884352 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Aug 7 22:04:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:179b] InstallationDate: Installed on 2016-06-26 (42 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP EliteBook 8470p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=1126bf38-027a-410d-a905-5dbbd05a6b4d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.45 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8470p dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Jul 25 07:40:00 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 5236 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1610772/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1610772 Title: [drm] stuck on render ring Status in xorg package in Ubuntu: Incomplete Bug description: The problem is similiar to the one discrabed in #1547800 It was happen once in a while. Now it always happens when returning from sleep. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/sda6: clean, 278496/3727360 files, 2012554/14884352 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Aug 7 22:04:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor
Re: [Touch-packages] [Bug 1610772] Re: [drm] stuck on render ring
The problem still present on the latest BIOS as well 68ICF Ver. F.65 08/11/2016 Regards On Thu, Sep 1, 2016 at 12:02 AM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > Mikhail, thank you for reporting this and helping make Ubuntu better. > > As per > http://h20564.www2.hp.com/hpsc/swd/public/readIndex? > sp4ts.oid=5212842&swLangOid=8&swEnvOid=4060 > an update to your computer's buggy, insecure, and outdated BIOS is > available (F.64). When you update to this following > https://help.ubuntu.com/community/BIOSUpdate how does this improve the > situation? > > For more on BIOS updates and linux, please see > https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette > . > > Please note your current BIOS is already in the Bug Description, so > posting this on the old BIOS would not be helpful. > > Also, you don't have to create a new report. > > Once the BIOS is updated, if the problem is still reproducible: > 1) Please provide the output of the following terminal command (not > perform an apport-collect): > sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date > 2) Please make a comment specifically advising on how this improves the > situation. > 3) Please mark this report Status New. > > If it's not reproducible, please mark this as Invalid. > > Thank you for your help. > > ** Tags added: bios-outdated-f.64 > > ** Changed in: xorg (Ubuntu) >Importance: Undecided => Low > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1610772 > > Title: > [drm] stuck on render ring > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > The problem is similiar to the one discrabed in #1547800 > > It was happen once in a while. Now it always happens when returning > from sleep. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3 > ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 > Uname: Linux 4.4.0-31-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.1 > Architecture: amd64 > BootLog: /dev/sda6: clean, 278496/3727360 files, 2012554/14884352 blocks > CompizPlugins: No value set for `/apps/compiz-1/general/ > screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: KDE > Date: Sun Aug 7 22:04:40 2016 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: kubuntu > EcryptfsInUse: Yes > ExtraDebuggingInterest: No > GraphicsCard: >Intel Corporation 3rd Gen Core processor Graphics Controller > [8086:0166] (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics > Controller [103c:179b] > InstallationDate: Installed on 2016-06-26 (42 days ago) > InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > MachineType: Hewlett-Packard HP EliteBook 8470p > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic > root=UUID=1126bf38-027a-410d-a905-5dbbd05a6b4d ro quiet splash > vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/07/2013 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: 68ICF Ver. F.45 > dmi.board.name: 179B > dmi.board.vendor: Hewlett-Packard > dmi.board.version: KBC Version 42.36 > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013: > svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:rvnHewlett- > Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr: > dmi.product.name: HP EliteBook 8470p > dmi.product.version: A1029D1102 > dmi.sys.vendor: Hewlett-Packard > version.compiz: compiz N/A > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 > version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.1-1ubuntu2 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20160325-1ubuntu1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.12-1build2 > xserver.bootTime: Mon Jul 25 07:
[Touch-packages] [Bug 1610772] [NEW] [drm] stuck on render ring
Public bug reported: The problem is similiar to the one discrabed in #1547800 It was happen once in a while. Now it always happens when returning from sleep. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/sda6: clean, 278496/3727360 files, 2012554/14884352 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Aug 7 22:04:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:179b] InstallationDate: Installed on 2016-06-26 (42 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP EliteBook 8470p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=1126bf38-027a-410d-a905-5dbbd05a6b4d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.45 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8470p dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Jul 25 07:40:00 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5236 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1610772 Title: [drm] stuck on render ring Status in xorg package in Ubuntu: New Bug description: The problem is similiar to the one discrabed in #1547800 It was happen once in a while. Now it always happens when returning from sleep. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/sda6: clean, 278496/3727360 files, 2012554/14884352 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Aug 7 22:04:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:179b] InstallationDate: Installed on 2016-06-26 (42 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP EliteBook 8470p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=1126bf38-027a-410d-a905-5dbbd05a6b4d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.45 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013:svnHewlett-Packard:pnH
[Touch-packages] [Bug 1563283] Re: tail: unrecognized file system type 0x7c7c6673
Upstream fixed it. Ubuntu maintainers, please monitor when the new version will be released to update it in Ubuntu 14.04. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1563283 Title: tail: unrecognized file system type 0x7c7c6673 Status in coreutils package in Ubuntu: New Bug description: When using Parallels 11 OS X with Vagrant and Ubuntu guest, got this error. `tails` utility can't detect `prl_fs` filesystem. tail: unrecognized file system type 0x7c7c6673 for 'file.log'. please report this to bug-coreut...@gnu.org. reverting to polling # lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 coreutils 8.21-1ubuntu5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1563283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563283] Re: tail: unrecognized file system type 0x7c7c6673
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23143 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1563283 Title: tail: unrecognized file system type 0x7c7c6673 Status in coreutils package in Ubuntu: New Bug description: When using Parallels 11 OS X with Vagrant and Ubuntu guest, got this error. `tails` utility can't detect `prl_fs` filesystem. tail: unrecognized file system type 0x7c7c6673 for 'file.log'. please report this to bug-coreut...@gnu.org. reverting to polling # lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 coreutils 8.21-1ubuntu5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1563283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563283] [NEW] tail: unrecognized file system type 0x7c7c6673
Public bug reported: When using Parallels 11 OS X with Vagrant and Ubuntu guest, got this error. `tails` utility can't detect `prl_fs` filesystem. tail: unrecognized file system type 0x7c7c6673 for 'file.log'. please report this to bug-coreut...@gnu.org. reverting to polling # lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 coreutils 8.21-1ubuntu5.4 ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1563283 Title: tail: unrecognized file system type 0x7c7c6673 Status in coreutils package in Ubuntu: New Bug description: When using Parallels 11 OS X with Vagrant and Ubuntu guest, got this error. `tails` utility can't detect `prl_fs` filesystem. tail: unrecognized file system type 0x7c7c6673 for 'file.log'. please report this to bug-coreut...@gnu.org. reverting to polling # lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 coreutils 8.21-1ubuntu5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1563283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399100] Re: QT Applications ignore theme XFCE settings
*** This bug is a duplicate of bug 1382741 *** https://bugs.launchpad.net/bugs/1382741 ~/.config/Trolltech.conf ... [Qt] style=GTK+ ... helped on Xubuntu 16.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1399100 Title: QT Applications ignore theme XFCE settings Status in qt4-x11 package in Ubuntu: Confirmed Bug description: qt applications ignore xfce theme, f.exe smplayer in 14.04 all works fine ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libqtgui4 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 4 10:57:05 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-17 (47 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) SourcePackage: qt4-x11 UpgradeStatus: Upgraded to utopic on 2014-12-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1399100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399100] Re: QT Applications ignore theme XFCE settings
*** This bug is a duplicate of bug 1382741 *** https://bugs.launchpad.net/bugs/1382741 The bug is still in Xubuntu 16.04 beta2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1399100 Title: QT Applications ignore theme XFCE settings Status in qt4-x11 package in Ubuntu: Confirmed Bug description: qt applications ignore xfce theme, f.exe smplayer in 14.04 all works fine ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libqtgui4 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 4 10:57:05 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-17 (47 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) SourcePackage: qt4-x11 UpgradeStatus: Upgraded to utopic on 2014-12-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1399100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1561228] [NEW] dmevent can not open shared object file libdevmapper-event-lvm2snapshot.so leads to lvcreate/lvremove being slow
Public bug reported: 1) lsb_release -rd Description:Ubuntu Xenial Xerus (development branch) Release:16.04 2) apt-cache policy lvm2 lvm2: Installed: 2.02.133-1ubuntu7 Candidate: 2.02.133-1ubuntu7 Version table: *** 2.02.133-1ubuntu7 500 500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages 100 /var/lib/dpkg/status 3) Expected lvcreate/lvremove test to take less than a second 4) It took about 30 seconds instead To reproduce Use the script. export GROUP='group-test' export VOLUME='volume-test' export SNAPSHOT='_snapshot-test' export BACKING_FILE=/root/lvmbacking if ! vgs -o name | grep $GROUP; then dd if=/dev/zero of=$BACKING_FILE bs=1M count=2000 losetup /dev/loop100 $BACKING_FILE pvcreate /dev/loop100 vgcreate $GROUP /dev/loop100 fi lvcreate -n $VOLUME $GROUP -L 1g lvcreate --name $SNAPSHOT --snapshot $GROUP/$VOLUME -L 1.00g lvremove -f $GROUP/$SNAPSHOT time lvremove -f $GROUP/$VOLUME During lvcreate/lvremove, /var/log/syslog would show: Mar 23 15:39:59 xenial-server-2016-01-18-ppc64el dmeventd[2753]: dmeventd libdevmapper-event-lvm2snapshot.so dlopen failed: libdevmapper-event-lvm2snapshot.so: cannot open shared object file: No such file or directory. Workaround == In /etc/lvm/lvm.conf, change snapshot_library to use absolute path: snapshot_library = "/lib/powerpc64le-linux-gnu/device-mapper /libdevmapper-event-lvm2snapshot.so" The workaround is obviously would only work for the specific architecture. A proper fix would be to find out why dmevent can not load the library, and fix that. Additional Notes I have also tested this on Xenial x86 VM, and on baremetal install of Xenial. Had the same problem on both. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1561228 Title: dmevent can not open shared object file libdevmapper-event- lvm2snapshot.so leads to lvcreate/lvremove being slow Status in lvm2 package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) apt-cache policy lvm2 lvm2: Installed: 2.02.133-1ubuntu7 Candidate: 2.02.133-1ubuntu7 Version table: *** 2.02.133-1ubuntu7 500 500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages 100 /var/lib/dpkg/status 3) Expected lvcreate/lvremove test to take less than a second 4) It took about 30 seconds instead To reproduce Use the script. export GROUP='group-test' export VOLUME='volume-test' export SNAPSHOT='_snapshot-test' export BACKING_FILE=/root/lvmbacking if ! vgs -o name | grep $GROUP; then dd if=/dev/zero of=$BACKING_FILE bs=1M count=2000 losetup /dev/loop100 $BACKING_FILE pvcreate /dev/loop100 vgcreate $GROUP /dev/loop100 fi lvcreate -n $VOLUME $GROUP -L 1g lvcreate --name $SNAPSHOT --snapshot $GROUP/$VOLUME -L 1.00g lvremove -f $GROUP/$SNAPSHOT time lvremove -f $GROUP/$VOLUME During lvcreate/lvremove, /var/log/syslog would show: Mar 23 15:39:59 xenial-server-2016-01-18-ppc64el dmeventd[2753]: dmeventd libdevmapper-event-lvm2snapshot.so dlopen failed: libdevmapper-event-lvm2snapshot.so: cannot open shared object file: No such file or directory. Workaround == In /etc/lvm/lvm.conf, change snapshot_library to use absolute path: snapshot_library = "/lib/powerpc64le-linux-gnu/device-mapper /libdevmapper-event-lvm2snapshot.so" The workaround is obviously would only work for the specific architecture. A proper fix would be to find out why dmevent can not load the library, and fix that. Additional Notes I have also tested this on Xenial x86 VM, and on baremetal install of Xenial. Had the same problem on both. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1561228/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1541892] [NEW] package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Public bug reported: Clear 64 bit system Ubuntu Mate 16.04 , can't update in first time. apt-get install -f : dpkg: зависимости пакетов не позволяют настроить пакет ubuntu-mate-core: ubuntu-mate-core зависит от lightdm, однако: Пакет lightdm пока не настроен. dpkg: ошибка при обработке пакета ubuntu-mate-core (--configure): проблемы зависимостей — оставляем не настроенным Отчёты apport не записаны, так как сообщение об ошибке указывает на повторную ошибку от предыдущего отказа. Description:Ubuntu Xenial Xerus (development branch) Release:16.04 lightdm: Установлен: 1.17.5-0ubuntu2 Кандидат: 1.17.5-0ubuntu2 Таблица версий: *** 1.17.5-0ubuntu2 500 500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lightdm 1.17.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Thu Feb 4 18:10:40 2016 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2016-02-03 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160127.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: lightdm Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1541892 Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in lightdm package in Ubuntu: New Bug description: Clear 64 bit system Ubuntu Mate 16.04 , can't update in first time. apt-get install -f : dpkg: зависимости пакетов не позволяют настроить пакет ubuntu-mate-core: ubuntu-mate-core зависит от lightdm, однако: Пакет lightdm пока не настроен. dpkg: ошибка при обработке пакета ubuntu-mate-core (--configure): проблемы зависимостей — оставляем не настроенным Отчёты apport не записаны, так как сообщение об ошибке указывает на повторную ошибку от предыдущего отказа. Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 lightdm: Установлен: 1.17.5-0ubuntu2 Кандидат: 1.17.5-0ubuntu2 Таблица версий: *** 1.17.5-0ubuntu2 500 500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lightdm 1.17.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Thu Feb 4 18:10:40 2016 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2016-02-03 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160127.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: lightdm Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1541892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447888] [NEW] ** (gufw.py:3313): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-sjkBKr6pc2: Connection refused
Public bug reported: persists after reboot, various applications triggers this issue ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dbus 1.6.18-0ubuntu4.3 ProcVersionSignature: Ubuntu 3.16.0-34.47~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 24 06:21:52 2015 InstallationDate: Installed on 2015-03-02 (52 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) upstart.dbus.log: Activating service name='org.a11y.Bus' Successfully activated service 'org.a11y.Bus' ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1447888 Title: ** (gufw.py:3313): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-sjkBKr6pc2: Connection refused Status in dbus package in Ubuntu: New Bug description: persists after reboot, various applications triggers this issue ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dbus 1.6.18-0ubuntu4.3 ProcVersionSignature: Ubuntu 3.16.0-34.47~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 24 06:21:52 2015 InstallationDate: Installed on 2015-03-02 (52 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) upstart.dbus.log: Activating service name='org.a11y.Bus' Successfully activated service 'org.a11y.Bus' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1447888/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1286910] Re: Lock screen uses last active window's language instead of default keyboard language
This sulution (https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/comments/19) doesn't work for me (Ubuntu 14.04 LTS). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1286910 Title: Lock screen uses last active window's language instead of default keyboard language Status in Unity: New Status in “gnome-screensaver” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Lock screen (gnome-screensaver) uses last active window's language (keyboard layout) instead of default keyboard language. Steps to reproduce this bug: 1. In the system Text Entry settings: 1a. add two or more languages to the input sources list, e.g. English (as first and default) and Russian (as second); 1b. Set hotkeys to switch sources (e.g. Ctrl+Shift or CapsLock). 1c. Select "Allow different sources for each window" radio button. 1d. Select "New windows use the default source" radio button. 2. Run any application (e.g. gedit) and switch keyboard to second input language (Russian). 3. Lock the screen (Ctrl+Alt+L) or just wait idle time. 4. See what language set by default for password input in the lock screen. Expected: lock screen uses first input language (English) by default. What happened instead: lock screen uses last active window's language (Russian). Ubuntu versions affected: Ubuntu 13.10, Ubuntu 14.04 (daily builds) gnome-screensaver versions: 3.6.1-0ubuntu7, 3.6.1-0ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1286910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371246] Re: netns ifconfig problem
Namespaces are working now after the last ubuntu update and plugging Ethernet cable. ** Changed in: iproute2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1371246 Title: netns ifconfig problem Status in “iproute2” package in Ubuntu: Confirmed Bug description: I am using IP name space virtualization feature in Ubuntu 14.04. The simplest script for this is: #! /bin/sh ip netns add test ip link set dev eth1 netns test ip netns exec ip addr add 10.4.1.21/16 dev eth1 ip netns exec test ip link set dev eth1 up The node has eth0 with 10.4.1.20/16 and connected eth0 to eth1 by external cable. All had worked fine during updating Ubuntu 14.04 at the 14th or 15th of September. All is OK in Ubuntu 12.04 LTS. After the starting script I have a wrong result for 'sudo ip netns exec test ifconfig eth1' output as zero's broadcast address in test IP name space. Command 'sudo ip netns exec test ping 10.4.21.1' has failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1371246/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1205482] Re: /var/lib/ureadahead/pack file never created
I have this problem on Ubuntu 12.04 LTS. Because of this problem, preload do nothing useful. Hot to fix it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1205482 Title: /var/lib/ureadahead/pack file never created Status in “ureadahead” package in Ubuntu: Confirmed Bug description: I noticed that the pack file was never created. Looking at the /etc/init/ureadahead.conf, it appears that the 'mountall' event triggers ureadahead. However, according to the /etc/init/* files, this event is possibly never fired. /var/log/upstart file directory doesn't show any log file with 'ureadahead.log' name but shows only a 'ureadahead-other.log' file with the below error messages : --- ureadahead:/var/lib/ureadahead/var.pack: No such file or directory ureadahead:/var/lib/ureadahead/usr.pack: No such file or directory ureadahead:/var/lib/ureadahead/var.pack: No such file or directory ureadahead:/var/lib/ureadahead/home.pack: No such file or directory ureadahead:/var/lib/ureadahead/var.pack: No such file or directory ureadahead:/var/lib/ureadahead/var.pack: No such file or directory ureadahead:/var/lib/ureadahead/home.pack: No such file or directory ureadahead:/var/lib/ureadahead/data.pack: No such file or directory ureadahead:/var/lib/ureadahead/usr.pack: No such file or directory --- ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ureadahead 0.100.0-12 ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46 Uname: Linux 3.2.0-49-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Fri Jul 26 22:10:37 2013 MarkForUpload: True SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1205482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
