[Touch-packages] [Bug 1958019]
On my Legion Slim 7 Gen 7 16ARHA7 Same issue on Debian 12 Testing on Kernel 6.1.0-7 if this is a kernel issue, i hope it gets fixed soon and the distro maintainers can patch this sooner rather than later. Heres my audio info dump: root@Lavavex-Legion:~# aplay --list-devices List of PLAYBACK Hardware Devices card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 3: Generic_1 [HD-Audio Generic], device 0: ALC287 Analog [ALC287 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 root@Lavavex-Legion:~# ls /dev/snd -al total 0 drwxr-xr-x 3 root root 360 Apr 10 22:23 . drwxr-xr-x 19 root root 3800 Apr 10 22:23 .. drwxr-xr-x 2 root root 120 Apr 10 22:23 by-path crw-rw+ 1 root audio 116, 3 Apr 10 22:23 controlC0 crw-rw+ 1 root audio 116, 9 Apr 10 22:23 controlC1 crw-rw+ 1 root audio 116, 10 Apr 10 22:23 controlC2 crw-rw+ 1 root audio 116, 14 Apr 10 22:23 controlC3 crw-rw+ 1 root audio 116, 6 Apr 10 22:23 hwC1D0 crw-rw+ 1 root audio 116, 8 Apr 10 22:23 hwC2D0 crw-rw+ 1 root audio 116, 13 Apr 10 22:23 hwC3D0 crw-rw+ 1 root audio 116, 2 Apr 10 22:23 pcmC0D0c crw-rw+ 1 root audio 116, 4 Apr 10 22:23 pcmC1D3p crw-rw+ 1 root audio 116, 5 Apr 10 22:23 pcmC1D7p crw-rw+ 1 root audio 116, 7 Apr 10 22:23 pcmC2D3p crw-rw+ 1 root audio 116, 12 Apr 10 22:23 pcmC3D0c crw-rw+ 1 root audio 116, 11 Apr 10 22:31 pcmC3D0p crw-rw+ 1 root audio 116, 1 Apr 10 22:23 seq crw-rw+ 1 root audio 116, 33 Apr 10 22:23 timer root@Lavavex-Legion:~# cat /proc/asound/pcm 00-00: DMIC capture dmic-hifi-0 : : capture 1 01-03: HDMI 0 : HDMI 0 : playback 1 01-07: HDMI 1 : HDMI 1 : playback 1 02-03: HDMI 0 : HDMI 0 : playback 1 03-00: ALC287 Analog : ALC287 Analog : playback 1 : capture 1 root@Lavavex-Legion:~# cat /proc/asound/cards 0 [acp6x ]: acp6x - acp6x LENOVO-82UG-LegionS716ARHA7-LNVNB161216 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xc0b0 irq 79 2 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xc06c8000 irq 80 3 [Generic_1 ]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xc06c irq 81 -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16
[Touch-packages] [Bug 1958019]
Can confirm on Endeavour 6.8.5 that my Legion Slim 7 16arha7 has working speakers now! yay! Lets hope they don't break again... -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 994097] Re: Downloading files from SSL/HTTPS sites via proxy is broken
This is your friendly ubuntu admin typing: I just wanted to let you guys know that we here at Ubunutu really love giving our contributors the shaft: fuck you for trying to get ubuntu over ssl, and, additionally, we now no longer offer the MD5 checksums over ssl for you faggot developers. Lol I even remember a couple times when contributors donated us money to us specifically for buying SSL and we just spent it on toiletpaper. We get paid more $ than you can ever fucking imagine by windows and mac just to fuck you open source developers in the ass. Have a nice day. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/994097 Title: Downloading files from SSL/HTTPS sites via proxy is broken Status in wget package in Ubuntu: Confirmed Bug description: Description: Ubuntu 12.04 LTS Release: 12.04 wget: Installed: 1.13.4-2ubuntu1 Candidate: 1.13.4-2ubuntu1 Version table: *** 1.13.4-2ubuntu1 0 When setting the parameter https_proxy, wget fails with the following error: Proxy tunneling failed: Bad RequestUnable to establish SSL connection. Here is and example: WITHOUT PROXY: root@server:~# wget -O test https://www.google.com/ --2012-05-03 16:49:33-- https://www.google.com/ Resolving www.google.com (www.google.com)... 74.125.226.82, 74.125.226.83, 74.125.226.84, ... Connecting to www.google.com (www.google.com)|74.125.226.82|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://www.google.ca/ [following] --2012-05-03 16:49:33-- https://www.google.ca/ Resolving www.google.ca (www.google.ca)... 74.125.226.87, 74.125.226.88, 74.125.226.95 Connecting to www.google.ca (www.google.ca)|74.125.226.87|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: `test' [ <=> ] 12,137 --.-K/s in 0.009s 2012-05-03 16:49:33 (1.36 MB/s) - `test' saved [12137] WITH PROXY: root@server:~# export https_proxy=http://192.168.1.5:80/ root@server:~# wget -O test https://www.google.com/ --2012-05-03 16:49:47-- https://www.google.com/ Connecting to 192.168.1.5:80... connected. Proxy tunneling failed: Bad RequestUnable to establish SSL connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/994097/+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 38694] A change has been merged
Reviewed: https://review.opencontrail.org/39137 Committed: http://github.com/Juniper/contrail-fabric-utils/commit/e45f84e5a28728f7c1f65935d1f28490a2ef2d70 Submitter: Zuul (z...@lists.opencontrail.org) Branch:R4.0 commit e45f84e5a28728f7c1f65935d1f28490a2ef2d70 Author: ankitja Date: Mon Jan 15 15:12:41 2018 +0530 Fix attach_logs_cores issue Closes-bug: #38694 Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9 ** Changed in: juniperopenstack/r4.0 Status: In Progress => Fix Committed ** Changed in: juniperopenstack/r4.0 Milestone: None => r4.0.3.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: Fix Committed Status in Juniper Openstack r4.0 series: Fix Committed Status in Juniper Openstack r4.1 series: Fix Committed Status in Juniper Openstack trunk series: Fix Committed Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] A change has been merged
Reviewed: https://review.opencontrail.org/39137 Committed: http://github.com/Juniper/contrail-fabric-utils/commit/e45f84e5a28728f7c1f65935d1f28490a2ef2d70 Submitter: Zuul (z...@lists.opencontrail.org) Branch:R4.0 commit e45f84e5a28728f7c1f65935d1f28490a2ef2d70 Author: ankitja Date: Mon Jan 15 15:12:41 2018 +0530 Fix attach_logs_cores issue Closes-bug: #38694 Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: Fix Committed Status in Juniper Openstack r4.0 series: Fix Committed Status in Juniper Openstack r4.1 series: Fix Committed Status in Juniper Openstack trunk series: Fix Committed Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] A change has been merged
Reviewed: https://review.opencontrail.org/39136 Committed: http://github.com/Juniper/contrail-fabric-utils/commit/e2ce2e05bf864f8c96750073fc35f98cff70c386 Submitter: Zuul v3 CI (zuu...@zuul.opencontrail.org) Branch:master commit e2ce2e05bf864f8c96750073fc35f98cff70c386 Author: ankitja Date: Mon Jan 15 15:12:41 2018 +0530 Fix attach_logs_cores issue Closes-bug: #38694 Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9 ** Changed in: juniperopenstack/trunk Status: In Progress => Fix Committed ** Changed in: juniperopenstack/trunk Milestone: None => r5.0.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: Fix Committed Status in Juniper Openstack r4.0 series: Fix Committed Status in Juniper Openstack r4.1 series: Fix Committed Status in Juniper Openstack trunk series: Fix Committed Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] A change has been merged
Reviewed: https://review.opencontrail.org/39136 Committed: http://github.com/Juniper/contrail-fabric-utils/commit/e2ce2e05bf864f8c96750073fc35f98cff70c386 Submitter: Zuul v3 CI (zuu...@zuul.opencontrail.org) Branch:master commit e2ce2e05bf864f8c96750073fc35f98cff70c386 Author: ankitja Date: Mon Jan 15 15:12:41 2018 +0530 Fix attach_logs_cores issue Closes-bug: #38694 Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: Fix Committed Status in Juniper Openstack r4.0 series: Fix Committed Status in Juniper Openstack r4.1 series: Fix Committed Status in Juniper Openstack trunk series: Fix Committed Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 1763273] Re: kernel panic in Radeon driver while screen blank
** Attachment added: "Full kern.log from April 1 crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117229/+files/apr1.full.kern.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/1763273 Title: kernel panic in Radeon driver while screen blank Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: I maintain a set of older kiosks running a mix of stock Ubuntu 14.04 LTS and 16.04. As we have gradually transitioned them to 16.04, we have noticed that the machines running 16.04.1 now regularly exhibit problems restoring from the blank screen which appears after a period of inactivity. This only occurs on the machines where we've installed 16.04. All of the 16.04.1 installations are "fresh", that is, complete re-installs from scratch, and we install all security and other updates on a regular basis. This problem has persisted right from the beginning when we started using 16.04. Following a period of user inactivity, the screen goes blank; this is, of course, expected. When the user tries to restore the session by typing a key or moving the mouse, one of three outcomes occurs. Sometimes, the session restores normally. Other times, the screen remains blank regardless of all normal keyboard input, until a magic SysRq sequence is performed. After Alt-SysRq-k, either the virtual console resets to a login screen (as expected after this SysRq sequence), or we get a kernel panic text screen (see attached screen photo) and can only restore via a hard power-cycle reboot. I will continue to try to capture a better trace output from one of these conditions, perhaps from /var/log/kern.log or by installing linux-crashdump (although these old machines may not have enough memory for the stock package). But in the meantime, I'm attaching a photo of the kernel panic we see, which suggests a problem may reside in the Radeon driver ... which would seem possible, given the general blank-screen no-resume problem on these systems. Any advice on how to further capture any other needed details would be appreciated. Thanks very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1764211] [NEW] apport bug details for #1763273 (radeon crash while screen blank)
Public bug reported: Unfortunately, I had to create a second bug report because apport- collect will not accept a different set of Launchpad user credentials from those I used to create the original bug report (#1763273). My apologies, but I had to use a different Launchpad account to run apport- bug, so this is the result. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 15 18:28:07 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon X1300/X1550 Series] [174b:e020] Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon X1300/X1550 Series] (Secondary) [174b:e021] InstallationDate: Installed on 2017-07-24 (265 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic root=UUID=fe381ac7-304a-4c28-b497-bdefa6602251 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 2JKT30AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvr2JKT30AUS:bd01/24/2007:svnLENOVO:pn8811BJ8:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvr:cvnLENOVO:ct7:cvr: dmi.product.name: 8811BJ8 dmi.product.version: ThinkCentre M55 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Apr 15 17:45:51 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputUSB Optical MouseMOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu 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/1764211 Title: apport bug details for #1763273 (radeon crash while screen blank) Status in xorg package in Ubuntu: New Bug description: Unfortunately, I had to create a second bug report because apport- collect will not accept a different set of Launchpad user credentials from those I used to create the original bug report (#1763273). My apologies, but I had to use a different Launchpad account to run apport-bug, so this is the result. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 15 18:28:07 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebugging
[Touch-packages] [Bug 1764211] Re: apport bug details for #1763273 (radeon crash while screen blank)
When I get home I'll copy these attachments and data into the original bug report under my personal Launchpad account. -- 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/1764211 Title: apport bug details for #1763273 (radeon crash while screen blank) Status in xorg package in Ubuntu: New Bug description: Unfortunately, I had to create a second bug report because apport- collect will not accept a different set of Launchpad user credentials from those I used to create the original bug report (#1763273). My apologies, but I had to use a different Launchpad account to run apport-bug, so this is the result. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 15 18:28:07 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon X1300/X1550 Series] [174b:e020] Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon X1300/X1550 Series] (Secondary) [174b:e021] InstallationDate: Installed on 2017-07-24 (265 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic root=UUID=fe381ac7-304a-4c28-b497-bdefa6602251 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 2JKT30AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvr2JKT30AUS:bd01/24/2007:svnLENOVO:pn8811BJ8:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvr:cvnLENOVO:ct7:cvr: dmi.product.name: 8811BJ8 dmi.product.version: ThinkCentre M55 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Apr 15 17:45:51 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputUSB Optical MouseMOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764211/+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 1763273] Re: kernel panic in Radeon driver while screen blank
Further details from apport-bug are in #1764211; I'll copy them into this account using my "cdarroch" personal Launchpad account in a few hours, when I get home. -- 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/1763273 Title: kernel panic in Radeon driver while screen blank Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: I maintain a set of older kiosks running a mix of stock Ubuntu 14.04 LTS and 16.04. As we have gradually transitioned them to 16.04, we have noticed that the machines running 16.04.1 now regularly exhibit problems restoring from the blank screen which appears after a period of inactivity. This only occurs on the machines where we've installed 16.04. All of the 16.04.1 installations are "fresh", that is, complete re-installs from scratch, and we install all security and other updates on a regular basis. This problem has persisted right from the beginning when we started using 16.04. Following a period of user inactivity, the screen goes blank; this is, of course, expected. When the user tries to restore the session by typing a key or moving the mouse, one of three outcomes occurs. Sometimes, the session restores normally. Other times, the screen remains blank regardless of all normal keyboard input, until a magic SysRq sequence is performed. After Alt-SysRq-k, either the virtual console resets to a login screen (as expected after this SysRq sequence), or we get a kernel panic text screen (see attached screen photo) and can only restore via a hard power-cycle reboot. I will continue to try to capture a better trace output from one of these conditions, perhaps from /var/log/kern.log or by installing linux-crashdump (although these old machines may not have enough memory for the stock package). But in the meantime, I'm attaching a photo of the kernel panic we see, which suggests a problem may reside in the Radeon driver ... which would seem possible, given the general blank-screen no-resume problem on these systems. Any advice on how to further capture any other needed details would be appreciated. Thanks very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1763273] Re: kernel panic in Radeon driver while screen blank
** Attachment added: "gdb-Xorg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117324/+files/gdb-Xorg.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/1763273 Title: kernel panic in Radeon driver while screen blank Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: I maintain a set of older kiosks running a mix of stock Ubuntu 14.04 LTS and 16.04. As we have gradually transitioned them to 16.04, we have noticed that the machines running 16.04.1 now regularly exhibit problems restoring from the blank screen which appears after a period of inactivity. This only occurs on the machines where we've installed 16.04. All of the 16.04.1 installations are "fresh", that is, complete re-installs from scratch, and we install all security and other updates on a regular basis. This problem has persisted right from the beginning when we started using 16.04. Following a period of user inactivity, the screen goes blank; this is, of course, expected. When the user tries to restore the session by typing a key or moving the mouse, one of three outcomes occurs. Sometimes, the session restores normally. Other times, the screen remains blank regardless of all normal keyboard input, until a magic SysRq sequence is performed. After Alt-SysRq-k, either the virtual console resets to a login screen (as expected after this SysRq sequence), or we get a kernel panic text screen (see attached screen photo) and can only restore via a hard power-cycle reboot. I will continue to try to capture a better trace output from one of these conditions, perhaps from /var/log/kern.log or by installing linux-crashdump (although these old machines may not have enough memory for the stock package). But in the meantime, I'm attaching a photo of the kernel panic we see, which suggests a problem may reside in the Radeon driver ... which would seem possible, given the general blank-screen no-resume problem on these systems. Any advice on how to further capture any other needed details would be appreciated. Thanks very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1763273] Re: kernel panic in Radeon driver while screen blank
** Attachment added: "rom.vga.bin" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117323/+files/rom.vga.bin -- 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/1763273 Title: kernel panic in Radeon driver while screen blank Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: I maintain a set of older kiosks running a mix of stock Ubuntu 14.04 LTS and 16.04. As we have gradually transitioned them to 16.04, we have noticed that the machines running 16.04.1 now regularly exhibit problems restoring from the blank screen which appears after a period of inactivity. This only occurs on the machines where we've installed 16.04. All of the 16.04.1 installations are "fresh", that is, complete re-installs from scratch, and we install all security and other updates on a regular basis. This problem has persisted right from the beginning when we started using 16.04. Following a period of user inactivity, the screen goes blank; this is, of course, expected. When the user tries to restore the session by typing a key or moving the mouse, one of three outcomes occurs. Sometimes, the session restores normally. Other times, the screen remains blank regardless of all normal keyboard input, until a magic SysRq sequence is performed. After Alt-SysRq-k, either the virtual console resets to a login screen (as expected after this SysRq sequence), or we get a kernel panic text screen (see attached screen photo) and can only restore via a hard power-cycle reboot. I will continue to try to capture a better trace output from one of these conditions, perhaps from /var/log/kern.log or by installing linux-crashdump (although these old machines may not have enough memory for the stock package). But in the meantime, I'm attaching a photo of the kernel panic we see, which suggests a problem may reside in the Radeon driver ... which would seem possible, given the general blank-screen no-resume problem on these systems. Any advice on how to further capture any other needed details would be appreciated. Thanks very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1763273] Re: kernel panic in Radeon driver while screen blank
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117322/+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/1763273 Title: kernel panic in Radeon driver while screen blank Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: I maintain a set of older kiosks running a mix of stock Ubuntu 14.04 LTS and 16.04. As we have gradually transitioned them to 16.04, we have noticed that the machines running 16.04.1 now regularly exhibit problems restoring from the blank screen which appears after a period of inactivity. This only occurs on the machines where we've installed 16.04. All of the 16.04.1 installations are "fresh", that is, complete re-installs from scratch, and we install all security and other updates on a regular basis. This problem has persisted right from the beginning when we started using 16.04. Following a period of user inactivity, the screen goes blank; this is, of course, expected. When the user tries to restore the session by typing a key or moving the mouse, one of three outcomes occurs. Sometimes, the session restores normally. Other times, the screen remains blank regardless of all normal keyboard input, until a magic SysRq sequence is performed. After Alt-SysRq-k, either the virtual console resets to a login screen (as expected after this SysRq sequence), or we get a kernel panic text screen (see attached screen photo) and can only restore via a hard power-cycle reboot. I will continue to try to capture a better trace output from one of these conditions, perhaps from /var/log/kern.log or by installing linux-crashdump (although these old machines may not have enough memory for the stock package). But in the meantime, I'm attaching a photo of the kernel panic we see, which suggests a problem may reside in the Radeon driver ... which would seem possible, given the general blank-screen no-resume problem on these systems. Any advice on how to further capture any other needed details would be appreciated. Thanks very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1763273] Re: kernel panic in Radeon driver while screen blank
Further debugging today while I'm on-site with the kiosks. The system froze, as usual, after normal idle screen blanking. I was able to login via ssh and retrieve some details. First, it appears that the basic screen blanking problem is somehow related to the Radeon driver. I will attach the Xorg.0.log file and a gdb backtrace on the running but non-responsive Xorg process. No keyboard or mouse activity will un-blank the screen. Here's the output from lspci | grep VGA: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] I'll also attach the PCI ROM dump from the /sys/devices rom file for this device. This suggests that when we use Alt-SysRq-k to restore the system, sometimes we trigger *another* bug in the driver which results in the overall system crash. See the attached apr1.full.kern.log file for what details I could recover from the crash on April 1st; that corresponds to the screen photo I took that day (the radeon_kernel_panic1.jpg attachment). The Xorg "hang" bug which precedes this appears similar, but not identical, to what is documented in #1664979: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979 I will continue to try to study the live Xorg process to see if I can determine where its hung, but I may not have time this evening. Let me know if there are specific further debugging steps I can take to examine either the Xorg hang or the subsequent crash which (sometimes) follows on attempting to recover with Alt-SysRq-k. (And note that I'll copy in the files apport-bug generated from #1764211 later tonight, using my "cdarroch" personal account, and then I'll try to close that extra bug report.) Thanks very much, Chris. -- 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/1763273 Title: kernel panic in Radeon driver while screen blank Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: I maintain a set of older kiosks running a mix of stock Ubuntu 14.04 LTS and 16.04. As we have gradually transitioned them to 16.04, we have noticed that the machines running 16.04.1 now regularly exhibit problems restoring from the blank screen which appears after a period of inactivity. This only occurs on the machines where we've installed 16.04. All of the 16.04.1 installations are "fresh", that is, complete re-installs from scratch, and we install all security and other updates on a regular basis. This problem has persisted right from the beginning when we started using 16.04. Following a period of user inactivity, the screen goes blank; this is, of course, expected. When the user tries to restore the session by typing a key or moving the mouse, one of three outcomes occurs. Sometimes, the session restores normally. Other times, the screen remains blank regardless of all normal keyboard input, until a magic SysRq sequence is performed. After Alt-SysRq-k, either the virtual console resets to a login screen (as expected after this SysRq sequence), or we get a kernel panic text screen (see attached screen photo) and can only restore via a hard power-cycle reboot. I will continue to try to capture a better trace output from one of these conditions, perhaps from /var/log/kern.log or by installing linux-crashdump (although these old machines may not have enough memory for the stock package). But in the meantime, I'm attaching a photo of the kernel panic we see, which suggests a problem may reside in the Radeon driver ... which would seem possible, given the general blank-screen no-resume problem on these systems. Any advice on how to further capture any other needed details would be appreciated. Thanks very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1763273] Re: kernel panic in Radeon driver while screen blank
While logged in via ssh to the machine with the "hung" Xorg (screen blank, no way to recover except Alt-SysRq-k), I dumped the output of Alt-SysRq-t into the syslog -- see attached file. Not sure this is much use, however. Just trying to be complete while I'm on-site with a hung machine. ** Attachment added: "syslog with output from Alt-SysRq-t in ssh session" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117347/+files/syslog -- 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/1763273 Title: kernel panic in Radeon driver while screen blank Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: I maintain a set of older kiosks running a mix of stock Ubuntu 14.04 LTS and 16.04. As we have gradually transitioned them to 16.04, we have noticed that the machines running 16.04.1 now regularly exhibit problems restoring from the blank screen which appears after a period of inactivity. This only occurs on the machines where we've installed 16.04. All of the 16.04.1 installations are "fresh", that is, complete re-installs from scratch, and we install all security and other updates on a regular basis. This problem has persisted right from the beginning when we started using 16.04. Following a period of user inactivity, the screen goes blank; this is, of course, expected. When the user tries to restore the session by typing a key or moving the mouse, one of three outcomes occurs. Sometimes, the session restores normally. Other times, the screen remains blank regardless of all normal keyboard input, until a magic SysRq sequence is performed. After Alt-SysRq-k, either the virtual console resets to a login screen (as expected after this SysRq sequence), or we get a kernel panic text screen (see attached screen photo) and can only restore via a hard power-cycle reboot. I will continue to try to capture a better trace output from one of these conditions, perhaps from /var/log/kern.log or by installing linux-crashdump (although these old machines may not have enough memory for the stock package). But in the meantime, I'm attaching a photo of the kernel panic we see, which suggests a problem may reside in the Radeon driver ... which would seem possible, given the general blank-screen no-resume problem on these systems. Any advice on how to further capture any other needed details would be appreciated. Thanks very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1764211] Re: apport bug details for #1763273 (radeon crash while screen blank)
*** This bug is a duplicate of bug 1763273 *** https://bugs.launchpad.net/bugs/1763273 ** This bug has been marked a duplicate of bug 1763273 kernel panic in Radeon driver while screen blank -- 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/1764211 Title: apport bug details for #1763273 (radeon crash while screen blank) Status in xorg package in Ubuntu: New Bug description: Unfortunately, I had to create a second bug report because apport- collect will not accept a different set of Launchpad user credentials from those I used to create the original bug report (#1763273). My apologies, but I had to use a different Launchpad account to run apport-bug, so this is the result. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 15 18:28:07 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon X1300/X1550 Series] [174b:e020] Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon X1300/X1550 Series] (Secondary) [174b:e021] InstallationDate: Installed on 2017-07-24 (265 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic root=UUID=fe381ac7-304a-4c28-b497-bdefa6602251 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 2JKT30AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvr2JKT30AUS:bd01/24/2007:svnLENOVO:pn8811BJ8:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvr:cvnLENOVO:ct7:cvr: dmi.product.name: 8811BJ8 dmi.product.version: ThinkCentre M55 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Apr 15 17:45:51 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputUSB Optical MouseMOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764211/+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 38694] [Review update] R4.1
Review in progress for https://review.opencontrail.org/38895 Submitter: Ankit Jain (anki...@juniper.net) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: New Status in Juniper Openstack r4.1 series: In Progress Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] [Review update] R4.1
Review in progress for https://review.opencontrail.org/38895 Submitter: Ankit Jain (anki...@juniper.net) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: New Status in Juniper Openstack r4.1 series: In Progress Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] [Review update] R4.1
Review in progress for https://review.opencontrail.org/38895 Submitter: Ankit Jain (anki...@juniper.net) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: New Status in Juniper Openstack r4.1 series: In Progress Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] [Review update] R4.1
Review in progress for https://review.opencontrail.org/38895 Submitter: Ankit Jain (anki...@juniper.net) ** Also affects: juniperopenstack/r4.1 Importance: Undecided Status: New ** Also affects: juniperopenstack/r4.1 Importance: Medium Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: New Status in Juniper Openstack r4.1 series: In Progress Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] A change has been merged
Reviewed: https://review.opencontrail.org/38895 Committed: http://github.com/Juniper/contrail-fabric-utils/commit/f47e0cab468567a39d58cdb7cc3c5c93a4907f33 Submitter: Zuul (z...@lists.opencontrail.org) Branch:R4.1 commit f47e0cab468567a39d58cdb7cc3c5c93a4907f33 Author: ankitja Date: Mon Jan 15 15:12:41 2018 +0530 Fix attach_logs_cores issue Closes-bug: #38694 Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: New Status in Juniper Openstack r4.1 series: Fix Committed Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] A change has been merged
Reviewed: https://review.opencontrail.org/38895 Committed: http://github.com/Juniper/contrail-fabric-utils/commit/f47e0cab468567a39d58cdb7cc3c5c93a4907f33 Submitter: Zuul (z...@lists.opencontrail.org) Branch:R4.1 commit f47e0cab468567a39d58cdb7cc3c5c93a4907f33 Author: ankitja Date: Mon Jan 15 15:12:41 2018 +0530 Fix attach_logs_cores issue Closes-bug: #38694 Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9 ** Changed in: juniperopenstack/r4.1 Status: In Progress => Fix Committed ** Changed in: juniperopenstack/r4.1 Milestone: None => r4.1.1.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: New Status in Juniper Openstack r4.1 series: Fix Committed Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] [Review update] master
Review in progress for https://review.opencontrail.org/39136 Submitter: Ankit Jain (anki...@juniper.net) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: In Progress Status in Juniper Openstack r4.0 series: In Progress Status in Juniper Openstack r4.1 series: Fix Committed Status in Juniper Openstack trunk series: In Progress Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] [Review update] R4.0
Review in progress for https://review.opencontrail.org/39137 Submitter: Ankit Jain (anki...@juniper.net) ** Also affects: juniperopenstack/trunk Importance: Undecided Status: New ** Also affects: juniperopenstack/trunk Importance: Medium Status: In Progress ** Also affects: juniperopenstack/r4.0 Importance: Undecided Status: New ** Also affects: juniperopenstack/r4.0 Importance: Medium Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: In Progress Status in Juniper Openstack r4.0 series: In Progress Status in Juniper Openstack r4.1 series: Fix Committed Status in Juniper Openstack trunk series: In Progress Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] [Review update] master
Review in progress for https://review.opencontrail.org/39136 Submitter: Ankit Jain (anki...@juniper.net) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: In Progress Status in Juniper Openstack r4.0 series: In Progress Status in Juniper Openstack r4.1 series: Fix Committed Status in Juniper Openstack trunk series: In Progress Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] [Review update] R4.0
Review in progress for https://review.opencontrail.org/39137 Submitter: Ankit Jain (anki...@juniper.net) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/38694 Title: No XChat in Dapper Status in Juniper Openstack: In Progress Status in Juniper Openstack r4.0 series: In Progress Status in Juniper Openstack r4.1 series: Fix Committed Status in Juniper Openstack trunk series: In Progress Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Apparently someone made the decision to remove XChat from the default installation for Dapper. This is important because it is the means new users use to reach the various IRC channels on Freenode and all the support those have to offer. I understand that Gaim is still included and supports IRC, but this has a few problems as an alternative. First, new users are not going to thing that Gaim Internet Messenger in their Applications menu has anything to do with getting support. Second, setting up, connecting to, and using IRC isn't entirely intuitive. Third, many people simply don't like Gaim's IRC UI. Fourth, it does not have the built-in setting like XChat had to automatically join #ubuntu when first started. In short, a brand new user is significantly less likely to manage to find the support of the IRC channels on their first boot of Ubuntu without XChat included and not knowing the ropes pretty well already. The IRC channels are an absolutely vital way of helping new users, and must be very easily accessible. Inclusion of XChat is a big step towards that. (Further UI setup for first boot are an issue as well, but that's a separate issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 1876219] Re: iris driver for old cpu
After upgrade to Ubuntu 20.04 most KDE native apps are now crashing and this includes systemsettings5. segfault stacktrace points to crash in /usr/lib/x86_64-linux-gnu/dri/iris_dri.so > inxi -G Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel Display: x11 server: X.Org 1.20.8 driver: intel resolution: 3440x1440~60Hz OpenGL: renderer: Mesa Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 20.1.8 xserver-xorg-video-intel version 2:2.99.917+git20200226-1 Setting MESA_LOADER_DRIVER_OVERRIDE=i965 does resolve this issue completely, however I am wondering why this is not selected automatically if iris driver does not support my GPU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1876219 Title: iris driver for old cpu Status in Mesa: Confirmed Status in mesa package in Ubuntu: Confirmed Status in ring package in Ubuntu: New Status in vlc package in Ubuntu: Invalid Bug description: I am not completely sure where I should file the bug. I am using Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the default graphics driver, which results in crashes in multiple apps including guvcview and calibre. Setting MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but is it true that iris does not support older generations of Intel CPUs? If it is the case would it be possible to revert to i965 in those circumstances? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1876219/+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 144085] master
*** This bug is a duplicate of bug 130444 *** https://bugs.launchpad.net/bugs/130444 Review in progress for https://review.opencontrail.org/9558 Submitter: Ranjeet R (rranj...@juniper.net) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/144085 Title: Charset is not set correctly in VGA text-mode Status in console-setup package in Ubuntu: Incomplete Bug description: The charset (and special characters) are not displayed correctly in VGA text-mode while usplash is running. There was a bug report #21567 in which Michael Vogt already described the problem.: 'The kernel just refuses it in drivers/char/vt.c:con_font_set(). But that seems to be because the vga text-mode uses parts of it's video memory to store the fontmap. That can't work when in graphic mode obviously. I don't know why the kernel doesn't store the fontmap for the next switch to text-mode. It looks like it keeps a copy in kernel memory anyway' This bug still exists in Feisty. As the vga text-mode is currently still the default mode in Ubuntu, it should affect nearly everybody until he/she changes the console screen mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/144085/+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 144085] A change has been merged
*** This bug is a duplicate of bug 130444 *** https://bugs.launchpad.net/bugs/130444 Reviewed: https://review.opencontrail.org/9558 Committed: http://github.org/Juniper/contrail-packaging/commit/1df649ffa9547e8a78cddba8a1e3c31c306c0254 Submitter: Zuul Branch:master commit 1df649ffa9547e8a78cddba8a1e3c31c306c0254 Author: Ranjeet R Date: Mon Apr 27 11:10:36 2015 -0700 Fixes: Upgrade RabbitMQ from 3.1 to 3.5 Changes for Rabbitmq-server upgrade to 3.5.0-1. RHEL only supports 3.3.5 el7 package. Hence added the version check to 3.3.5 for the Contrail config spec files. Related review - https://review.opencontrail.org/#/c/9134/ Upgrading RabbitMQ for CentOs 6.5 Havana ClosesBug: 144085 Change-Id: I62f10fe40b7850da0482f4560cd8e5fedfd23bc7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/144085 Title: Charset is not set correctly in VGA text-mode Status in console-setup package in Ubuntu: Incomplete Bug description: The charset (and special characters) are not displayed correctly in VGA text-mode while usplash is running. There was a bug report #21567 in which Michael Vogt already described the problem.: 'The kernel just refuses it in drivers/char/vt.c:con_font_set(). But that seems to be because the vga text-mode uses parts of it's video memory to store the fontmap. That can't work when in graphic mode obviously. I don't know why the kernel doesn't store the fontmap for the next switch to text-mode. It looks like it keeps a copy in kernel memory anyway' This bug still exists in Feisty. As the vga text-mode is currently still the default mode in Ubuntu, it should affect nearly everybody until he/she changes the console screen mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/144085/+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 1049345] A change has been merged
Reviewed: https://review.opencontrail.org/6246 Committed: http://github.org/Juniper/contrail-controller/commit/c2005aa2f31ec71fd641433193f1e55bc12839ee Submitter: Zuul Branch:master commit c2005aa2f31ec71fd641433193f1e55bc12839ee Author: Tapan Karwa Date: Thu Jan 15 15:56:45 2015 -0800 Removing asserts in the channel code that were being called in response to unexpected bytes in the packet. Instead, we will return error to the SM and restart the connection. Fixes gnats bug 1049345. Change-Id: Ie7e3647b71cbc081ccb20f5033afaf61883cce45 Partial-Bug: #1408740 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1049345 Title: telepathy-gabble crashed with signal 7 in tp_base_channel_close() Status in telepathy-gabble package in Ubuntu: Confirmed Bug description: Got error message after dist-upgrade and reboot. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: telepathy-gabble 0.16.1-1 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Tue Sep 11 22:57:34 2012 ExecutablePath: /usr/lib/telepathy/telepathy-gabble InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) ProcCmdline: /usr/lib/telepathy/telepathy-gabble ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 7 SourcePackage: telepathy-gabble StacktraceTop: tp_base_channel_close () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0 ?? () ?? () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: telepathy-gabble crashed with signal 7 in tp_base_channel_close() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/1049345/+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 1798400]
[Automated Action] NeedInfo-To-Unconfirmed -- 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/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+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