[Desktop-packages] [Bug 2062950] [NEW] RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10
Public bug reported:
this is a continuation of the bug reported in
https://bugs.launchpad.net/ubuntu/+bug/2062504
I reinstalled ubuntu 23, and didn't install anything else. I'm still
having the flickering when connecting an HDMI to an external monitor.
please help
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 22:27:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias:
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
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 mantic ubuntu wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2062950
Title:
RE: Flickering problems on external monitor with HDMI after installing
Ubuntu 23.10
Status in xorg package in Ubuntu:
New
Bug description:
this is a continuation of the bug reported in
https://bugs.launchpad.net/ubuntu/+bug/2062504
I reinstalled ubuntu 23, and didn't install anything else. I'm still
having the flickering when connecting an HDMI to an external monitor.
please help
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 22:27:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
[Desktop-packages] [Bug 2062504] [NEW] Flickering problems on external monitor with HDMI after installing Ubuntu 23.10
Public bug reported:
I just installed ubuntu 23.10 on my thinkpad L13. It works fine on my
laptop monitor. But when I connect an HDMI cable to my other monitor,
then the screen flickers on the laptop and nothing shows on the other
monitor
I know it can't be the problem with the other monitor as I bought it
brand new last week, and the cable works fine on this same laptop when I
run in windows, and it works fine on other laptops with windows/mac
I already installed the driver with `sudo apt install nvidia-driver-535
nvidia-dkms-535` and rebooted, but that didn't help. I then installed
driver 550 and I still have the flickering
This laptop uses an intel Alder Lake-UP3 GT2
I also tried editing `etc/default/grub` by adding 'nomodeset' or
'radeon.modeset=0' within the quotation marks in the line
GRUB_CMDLINE_LINUX_DEFAULT but that didn't help either
can anyone help?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 18 23:17:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: nvidia/550.54.14, 6.5.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-13 (6 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=bc80dc13-87d7-4310-bd10-43d45de6d3a7 ro quiet splash radeon.modeset=0
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias:
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120+git2404140851.1179ed~oibaf~m
version.libgl1-mesa-dri: libgl1-mesa-dri 24.1~git2404150600.4a1904~oibaf~m
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
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 mantic third-party-packages ubuntu wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2062504
Title:
Flickering problems on external monitor with HDMI after installing
Ubuntu 23.10
Status in xorg package in Ubuntu:
New
Bug description:
I just installed ubuntu 23.10 on my thinkpad L13. It works fine on my
laptop monitor. But when I connect an HDMI cable to my other monitor,
then the screen flickers on the laptop and nothing shows on the other
monitor
I know it can't be the problem with the other monitor as I bought it
brand new last week, and the cable works fine on this same laptop when
I run in windows, and it works fine on other laptops with windows/mac
I already installed the driver with `sudo apt install nvidia-
driver-535 nvidia-dkms-535` and rebooted, but that didn't help. I then
installed driver 550 and I still have the flickering
This laptop uses an intel Alder Lake-UP3 GT2
I also tried editing `etc/default/grub` by adding 'nomodeset' or
'radeon.modeset=0' within the quotation marks in the line
GRUB_CMDLINE_LINUX_DEFAULT but that didn't help either
can anyone help?
ProblemType: Bug
DistroRelease: Ubuntu
[Desktop-packages] [Bug 1872103] [NEW] After update to 6.4.2.2: Split database only accessible while running in Safe Mode
Public bug reported: I updated LibreOffice from 6.0.7 to 6.4.2.2 via ppa:libreoffice/libreoffice-6-4. Now I get an error when trying to open a form in a HSQLDB 2.3.2 split database: “Error in script file line: 1 Unexpected token UNIQUE, requires COLLATION in statement [SET DATABASE UNIQUE]“ When running in Safe Mode, I can access the database. But even when using a new, clean profile, I can't access the database! When starting LibreOffice with LC_ALL=C libreoffice I can open a form within the database but then an error like “The data could not be loaded. There exists no table named "[Name of my table]".“ is displayed. I tried installing the DEB packages provided on https://www.libreoffice.org/download/download/ , same version 6.4.2.2, and there the split database is working as expected. I reported this bug wrongly first here: https://bugs.documentfoundation.org/show_bug.cgi?id=132009 Steps to Reproduce: 1. Update LibreOffice from 6.0.7 to 6.4.2.2 on Ubuntu 18.04.4 using https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-6-4 2. Start LO and open a split database (Use this test database: http://bugs.documentfoundation.org/attachment.cgi?id=159465 ) 3. Click on a table Actual Results: Seeing following error message (when using German localization as normally) “Error in script file line: 1 Unexpected token UNIQUE, requires COLLATION in statement [SET DATABASE UNIQUE]“ When starting LO with LC_ALL=C libreoffice I can open a form within the database but then an error message like “The data could not be loaded. There exists no table named "[Name of my table]".“ is displayed. So the database is not usable at all. Expected Results: The split database should be accessible. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: [Information automatically included from LibreOffice] Locale: de Module: OfficeDatabaseDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.18.04.3 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-US (C); UI-Language: en-US Calc: threaded Ubuntu 18.04.4 LTS ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: packaging ppa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1872103 Title: After update to 6.4.2.2: Split database only accessible while running in Safe Mode Status in libreoffice package in Ubuntu: New Bug description: I updated LibreOffice from 6.0.7 to 6.4.2.2 via ppa:libreoffice/libreoffice-6-4. Now I get an error when trying to open a form in a HSQLDB 2.3.2 split database: “Error in script file line: 1 Unexpected token UNIQUE, requires COLLATION in statement [SET DATABASE UNIQUE]“ When running in Safe Mode, I can access the database. But even when using a new, clean profile, I can't access the database! When starting LibreOffice with LC_ALL=C libreoffice I can open a form within the database but then an error like “The data could not be loaded. There exists no table named "[Name of my table]".“ is displayed. I tried installing the DEB packages provided on https://www.libreoffice.org/download/download/ , same version 6.4.2.2, and there the split database is working as expected. I reported this bug wrongly first here: https://bugs.documentfoundation.org/show_bug.cgi?id=132009 Steps to Reproduce: 1. Update LibreOffice from 6.0.7 to 6.4.2.2 on Ubuntu 18.04.4 using https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-6-4 2. Start LO and open a split database (Use this test database: http://bugs.documentfoundation.org/attachment.cgi?id=159465 ) 3. Click on a table Actual Results: Seeing following error message (when using German localization as normally) “Error in script file line: 1 Unexpected token UNIQUE, requires COLLATION in statement [SET DATABASE UNIQUE]“ When starting LO with LC_ALL=C libreoffice I can open a form within the database but then an error message like “The data could not be loaded. There exists no table named "[Name of my table]".“ is displayed. So the database is not usable at all. Expected Results: The split database should be accessible. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: [Information automatically included from LibreOffice] Locale: de Module: OfficeDatabaseDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.18.04.3 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-US (C); UI-Language: en-US Calc: threaded Ubuntu 18.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1872103/+subscriptions --
[Desktop-packages] [Bug 1751837] [NEW] Opening documents on a sshfs share isn't working anymore
Public bug reported: I'm using Ubuntu 16.04.4 LTS with http://ppa.launchpad.net/libreoffice/libreoffice-5-4/ubuntu and the latest version of LibreOffice 5.4.5-0ubuntu0.16.04.1~lo1 . Since the latest update, LibreOffice can't open documents from a sshfs share anymore. It starts to load and then exits silently. There is no output when starting LibreOffice on a command line. With the version before (5.4.4~rc2-0ubuntu0.16.04.1~lo1) it was working without any problems. When copying an ODF-file from the sshfs-share to a local directory, LibreOffice opens it correctly. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Description changed: I'm using Ubuntu 16.04.4 LTS with http://ppa.launchpad.net/libreoffice/libreoffice-5-4/ubuntu and the latest version of LibreOffice 5.4.5-0ubuntu0.16.04.1~lo1 . Since the latest update, LibreOffice can't open documents from a sshfs share anymore. It starts to load and then exits silently. There is no output when starting LibreOffice on a command line. With the version before (5.4.4~rc2-0ubuntu0.16.04.1~lo1) it was working without any problems. + When copying an ODF-file from the sshfs-share to a local directory, LibreOffice opens it correctly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1751837 Title: Opening documents on a sshfs share isn't working anymore Status in libreoffice package in Ubuntu: New Bug description: I'm using Ubuntu 16.04.4 LTS with http://ppa.launchpad.net/libreoffice/libreoffice-5-4/ubuntu and the latest version of LibreOffice 5.4.5-0ubuntu0.16.04.1~lo1 . Since the latest update, LibreOffice can't open documents from a sshfs share anymore. It starts to load and then exits silently. There is no output when starting LibreOffice on a command line. With the version before (5.4.4~rc2-0ubuntu0.16.04.1~lo1) it was working without any problems. When copying an ODF-file from the sshfs-share to a local directory, LibreOffice opens it correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744963] [NEW] printing a PDF generated by LibreOffice sometimes fail with lpr but is printed correctly with evince
Public bug reported: Sometimes a PDF generated by LibreOffice is not printed correctly with lpr but is printed correctly with evince. For an example see attached PDF: Using lpr only the first line is printed, nothing more. I'm using Ubuntu 16.04.2 LTS with cups-filters 1.8.3-2ubuntu3.1 . The printer is HP LaserJet 3055, connected via network - DeviceURI hp:/net/HP_LaserJet_3055?ip=192.168.XXX.XXX using hplip 3.16.3+repack0-1 . Maybe this bug is related to https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=613987 ? Do you need additional information? ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Attachment added: "example document which is not printed correctly using lpr" https://bugs.launchpad.net/bugs/1744963/+attachment/5041809/+files/Hol+Pack.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1744963 Title: printing a PDF generated by LibreOffice sometimes fail with lpr but is printed correctly with evince Status in cups-filters package in Ubuntu: New Bug description: Sometimes a PDF generated by LibreOffice is not printed correctly with lpr but is printed correctly with evince. For an example see attached PDF: Using lpr only the first line is printed, nothing more. I'm using Ubuntu 16.04.2 LTS with cups-filters 1.8.3-2ubuntu3.1 . The printer is HP LaserJet 3055, connected via network - DeviceURI hp:/net/HP_LaserJet_3055?ip=192.168.XXX.XXX using hplip 3.16.3+repack0-1 . Maybe this bug is related to https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=613987 ? Do you need additional information? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1744963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693709] [NEW] Wrong substitution for TimesNewRomanPSMT in evince / postscriptname not used
Public bug reported: A PDF I got referenced the not embedded font TimesNewRomanPSMT. Document viewer evince by fontconfig used DejaVu Sans to display it. But „TimesNewRomanPSMT“ is the postscriptname of Times New Roman, so it looks like fontconfig is not looking for the postscript names. ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1693709 Title: Wrong substitution for TimesNewRomanPSMT in evince / postscriptname not used Status in fontconfig package in Ubuntu: New Bug description: A PDF I got referenced the not embedded font TimesNewRomanPSMT. Document viewer evince by fontconfig used DejaVu Sans to display it. But „TimesNewRomanPSMT“ is the postscriptname of Times New Roman, so it looks like fontconfig is not looking for the postscript names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1693709/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635797] [NEW] Analog audio out not showing in GUI sound settings.
Public bug reported: "aplay -Dplughw:0,0 -fcd sound.wav" works fine kes@vesta:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC1150 Analog [ALC1150 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 <...other cards which do appear in the System sound GUI...> ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 22 16:13:28 2016 InstallationDate: Installed on 2016-10-16 (6 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1150, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1810 dmi.board.asset.tag: Default string dmi.board.name: H170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1810:bd07/12/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1635797 Title: Analog audio out not showing in GUI sound settings. Status in alsa-driver package in Ubuntu: New Bug description: "aplay -Dplughw:0,0 -fcd sound.wav" works fine kes@vesta:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC1150 Analog [ALC1150 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 <...other cards which do appear in the System sound GUI...> ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 22 16:13:28 2016 InstallationDate: Installed on 2016-10-16 (6 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1150, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1810 dmi.board.asset.tag: Default string dmi.board.name: H170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1810:bd07/12/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1635797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1523269] [NEW] updating ppa:libreoffice/libreoffice-5-0 leads to HttpError404: binary-amd64 and binary-i386
Public bug reported: I'm using Ubuntu 14.04.3 LTS and the ppa:libreoffice/libreoffice-5-0 , libreoffice 1:5.0.3~rc2-0ubuntu1~trusty2 is installed. When I do sudo apt-get update I get the following errors: W: Failed to fetch https://launchpad.net/~libreoffice/+archive/libreoffice-5-0/dists/trusty/main /binary-amd64/Packages HttpError404 W: Failed to fetch https://launchpad.net/~libreoffice/+archive/libreoffice-5-0/dists/trusty/main/binary-i386/Packages HttpError404 E: Some index files failed to download. They have been ignored, or old ones used instead. I expect not to get 404 errors while updating the package information. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1523269 Title: updating ppa:libreoffice/libreoffice-5-0 leads to HttpError404: binary-amd64 and binary-i386 Status in libreoffice package in Ubuntu: New Bug description: I'm using Ubuntu 14.04.3 LTS and the ppa:libreoffice/libreoffice-5-0 , libreoffice 1:5.0.3~rc2-0ubuntu1~trusty2 is installed. When I do sudo apt-get update I get the following errors: W: Failed to fetch https://launchpad.net/~libreoffice/+archive/libreoffice-5-0/dists/trusty/main /binary-amd64/Packages HttpError404 W: Failed to fetch https://launchpad.net/~libreoffice/+archive/libreoffice-5-0/dists/trusty/main/binary-i386/Packages HttpError404 E: Some index files failed to download. They have been ignored, or old ones used instead. I expect not to get 404 errors while updating the package information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1523269/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Much obliged. --Jeff On 08/15/2015 03:03 AM, Robin wrote: JK, the link you need to fully unsubscribe is well hidden: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340-updates/+bug/1431753/+subscriptions, and then the bottom link, assuming that you are signed in to launchpad. HTH R. On 15/08/15 02:33, J K Cunningham wrote: On 08/14/2015 01:46 PM, teo1978 wrote: Are you aware that each comment triggers THOUSAND of emails to other users? Are you aware that you can unsubscribe if you want to? I unsubscribed from this bug report days ago and it's still sending me your silly tirades. Would you please STFU? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Invalid Status in nvidia-graphics-drivers-331-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
On 08/14/2015 01:46 PM, teo1978 wrote: Are you aware that each comment triggers THOUSAND of emails to other users? Are you aware that you can unsubscribe if you want to? I unsubscribed from this bug report days ago and it's still sending me your silly tirades. Would you please STFU? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Invalid Status in nvidia-graphics-drivers-331-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-340-updates source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346 source package in Trusty: Fix Released Status in nvidia-graphics-drivers-346-updates source package in Trusty: Fix Released Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
None of the people you are sending this email to can help you with that. On 01/23/2015 05:42 AM, Tomáš Kalász wrote: The unsubscribe action doesn't work. When I hit the button I get this error message: Timeout error Sorry, something just went wrong in Launchpad. We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience. Trying again in a couple of minutes might work. (Error ID: OOPS-6b943110657fa7e664f6502c31f87f60) -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of alex Sent: Friday, January 23, 2015 2:29 PM To: tomi.kal...@gmail.com Subject: Re: [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Thank you !! Am 22.01.2015 um 17:18 schrieb J K Cunningham: Link at bottom of email. On 01/22/2015 02:37 AM, SillasOS wrote: How to unsubscribe ? I have not subscribe to this email list ? It was a system report that do it. I dont want to receive lots of bug email reports every day. How can I stop this ? -- You received this bug notification because you are subscribed to a duplicate bug report (1387115). https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in nvidia-graphics-drivers-331 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Triaged Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in nvidia-graphics-drivers-331 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Triaged Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build
Re: [Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
Link at bottom of email. On 01/22/2015 02:37 AM, SillasOS wrote: How to unsubscribe ? I have not subscribe to this email list ? It was a system report that do it. I dont want to receive lots of bug email reports every day. How can I stop this ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in nvidia-graphics-drivers-331 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Triaged Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1411763] [NEW] Random system error popups. System76 box with nVidia driver
Public bug reported: $ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-44-generic Date: Thu Jan 15 11:34:02 2015 InstallationDate: Installed on 2014-09-27 (110 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages trusty ** Summary changed: - No idea. The notification keeps popping up of a system error at seemingly random times. This time it was after an upgrade and reboot. This is a System76 box and they use the NVidia driver - might have something to do with that. + Random system error popups. System76 box with nVidia driver -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1411763 Title: Random system error popups. System76 box with nVidia driver Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: $ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-44-generic Date: Thu Jan 15 11:34:02 2015 InstallationDate: Installed on 2014-09-27 (110 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1411763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
