[Touch-packages] [Bug 2033295] Re: AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary. AMD Ryzen
Selection of specific source package: I am not sure in which package the Linux Kernel AMD Ryzen graphic drivers are located. I chose "libdrm" as it includes libdrm-amdgpu. I hope that this is correct. ** Package changed: ubuntu => libdrm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/2033295 Title: AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary. AMD Ryzen Status in libdrm package in Ubuntu: New Bug description: Frequently, when I just use the computer, the mouse cursor freezes, the screen starts to flicker and freezes (screen flickers between entirely black and desktop visible). No interaction possible. In most cases Ctrl-Alt-Prnt-REISUB works to hard reboot the system. Frequency: Freezes happen several times a day. Unsaved work is lost. I noticed that: * The freezes usually happen when an external display is connected (it does not matter whether USB-C or HDMI). The freezes rarely happen when no external display is connected. * The freezes happen with Wayland and X11, with Ubuntu UI and Gnome Shell. * The freezes happen randomly, but I have the feeling that they happen more often when "something graphical" happens, e.g. when I go to the Gnome Shell overview, desktop switching, or when I switch to/from full screen mode, click on an image to scale it, or when I use map services in the web browser like Google Maps or radio.garden. * The freezes even more often happened when WebGL is active in Firefox or Chomium. * I encounter these annoying freezes already for several weeks. Having looked at the log files, I assume that AMDGPU is at the core of the problem. System: Ubuntu 23.04 (up to date), Wayland (freezes also happen with X11), Gnome 44.3. Linux 6.2.0-31-generic Lenovo ThinkPad T14s Gen 1 (with most recent BIOS/UEFI 1.44), AMD Ryzen™ 7 PRO 4750U with Radeon™ Graphics × 16. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/2033295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1738605] Re: Yesterday I had sound. Today I don't.
Hello, I went back to the very start and removed every audio related package I could and then reinstalled them and ran through all the trouble shooting lists I had and have fixed audio. I'm don't know what was causing it or what fixed it, but what was notable was that trying to stop/start PulseAudio manually was returning; daemon is already running when trying to start, and daemon is not running when trying to stop it. I think PulseAudio was the problem, but I think it was being caused by some ancillary thing that doesn't install/remove with it, as I purged/reinstalled PA and Alsa half a dozen times or so, but it wasn't fixed until I purged everything I could find related to audio. I'm unfamiliar with the .crash files, but maybe it will provide something useful for you. I wish I could be more helpful. GT On 12/18/2017 02:49 AM, Daniel van Vugt wrote: > It appears the reason is in the bug description: > > "PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon." > > Do you have any crash files in /var/crash ? > > ** Changed in: pulseaudio (Ubuntu) > Status: New => Incomplete > ** Attachment added: "_usr_bin_compiz.1000.crash" https://bugs.launchpad.net/bugs/1738605/+attachment/5024347/+files/_usr_bin_compiz.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1738605 Title: Yesterday I had sound. Today I don't. Status in pulseaudio package in Ubuntu: Incomplete Bug description: Happens every single time I install Ubuntu on every single computer I have ever install it on. This time, it doesn't seem to have a solution. Shows audio in volume control under output devices, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: master 1752 F pulseaudio /dev/snd/pcmC0D0c: master 1752 F...m pulseaudio /dev/snd/pcmC0D0p: master 1752 F...m pulseaudio /dev/snd/controlC0: master 1752 F pulseaudio Date: Sat Dec 16 23:23:28 2017 InstallationDate: Installed on 2017-12-15 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738605/+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 1738605] [NEW] Yesterday I had sound. Today I don't.
Public bug reported: Happens every single time I install Ubuntu on every single computer I have ever install it on. This time, it doesn't seem to have a solution. Shows audio in volume control under output devices, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: master 1752 F pulseaudio /dev/snd/pcmC0D0c: master 1752 F...m pulseaudio /dev/snd/pcmC0D0p: master 1752 F...m pulseaudio /dev/snd/controlC0: master 1752 F pulseaudio Date: Sat Dec 16 23:23:28 2017 InstallationDate: Installed on 2017-12-15 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1738605 Title: Yesterday I had sound. Today I don't. Status in pulseaudio package in Ubuntu: New Bug description: Happens every single time I install Ubuntu on every single computer I have ever install it on. This time, it doesn't seem to have a solution. Shows audio in volume control under output devices, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: master 1752 F pulseaudio /dev/snd/pcmC0D0c: master 1752 F...m pulseaudio /dev/snd/pcmC0D0p: master 1752 F...m pulseaudio /dev/snd/controlC0: master 1752 F pulseaudio Date: Sat Dec 16 23:23:28 2017 InstallationDate: Installed on 2017-12-15 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738605/+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 1539621] Re: Add an option to cancel pending snooze
Being highly irritated by the current (non)communication regarding Ubuntu Touch, I would like to ask about the future regarding this bug (and bugs like this). The "option to cancel pending snooze" is a feature which is neccessary for a mobile OS, independently whether it will be called Ubuntu Touch or Ubuntu Personal, whether it uses click or snap. I am curious to know what the future approach is to tackle this bug (and bugs like this)? Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1539621 Title: Add an option to cancel pending snooze Status in Canonical System Image: Confirmed Status in Ubuntu Clock App: Invalid Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: It’s happened to me a few times that my alarm wakes me up in the morning, I tap the snooze button to sleep 10 minutes more, but end up getting up before then. In that case, it would be very handy to have an option to cancel the pending snooze so that the alarm doesn’t go off again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539621/+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 1539621] Re: Add an option to cancel pending snooze
@Pat McGowan (pat-mcgowan): Will this bug be fixed in OTA 13 or did it miss this milestone? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1539621 Title: Add an option to cancel pending snooze Status in Canonical System Image: Confirmed Status in Ubuntu Clock App: Invalid Status in Ubuntu UX: Triaged Status in indicator-datetime package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: It’s happened to me a few times that my alarm wakes me up in the morning, I tap the snooze button to sleep 10 minutes more, but end up getting up before then. In that case, it would be very handy to have an option to cancel the pending snooze so that the alarm doesn’t go off again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539621/+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 1620393] [NEW] Keyboard does not show on page https://meet.jit.si Jitsi Meet
Public bug reported: In the Ubuntu Touch Webbrowser, the deyboard does not show on the Jitsi Meet page https://meet.jit.si How to reproduce: * Please tap on the page https://meet.jit.si in the input field (the one with the button "GO"). The keyboard will not show up. * Generally, the page seems not to render properly System: BQ M10 with OTA12 ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1620393 Title: Keyboard does not show on page https://meet.jit.si Jitsi Meet Status in webbrowser-app package in Ubuntu: New Bug description: In the Ubuntu Touch Webbrowser, the deyboard does not show on the Jitsi Meet page https://meet.jit.si How to reproduce: * Please tap on the page https://meet.jit.si in the input field (the one with the button "GO"). The keyboard will not show up. * Generally, the page seems not to render properly System: BQ M10 with OTA12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1620393/+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 1568750] Re: With dual SIM, SIM choice is not retained for a SMS conversation
OTA10 Regression: On my bq4.5 this very annoying issue appeared after updating to OTA10. Before OTA10, there was no problem, but now the SIM2 is not retained in SMS conversations and even actively tapping on "SIM2" does not send the SMS on SIM2, but SIM1. Since I am travelling in another country, this bug costed me approximately 30 Euro of mobile phone credit, because it was unpredictable whether the SMS was sent correctly via SIM2 or incorrectly via SIM1 (from my home country). There is a tendency of the phone to fall-back to SIM1 for SMS-sending after the OTA10 update. The behavior is very annoying and can be very costly!!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1568750 Title: With dual SIM, SIM choice is not retained for a SMS conversation Status in messaging-app package in Ubuntu: Confirmed Bug description: For an existing SMS conversation with one contact (when using dual SIM): Expected behaviour: tap on conversation in messaging-app, the messaging screen opens showing the SMS conversation, with the previously used SIM selected. Actual behaviour: SIM #1 is always selected, even if all previous SMS messages to that contact have used SIM #2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1568750/+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 1478222] Re: Ubuntu Touch forgets WiFi settings after first connection. EDUROAM network WPA WPA2 Enterprise
Thanks Enrique for the work-around. In fact, doing what you describe allows me to tick the remember password. Otherwise, one can never tick the field, because it is covered by the keyboard. This means: Anyone who fills the form from the top to the bottom (like everyone usually does it) will not succeed! Point (1) is a bug. Your point (2) is also a bug. The correct password is not accepted if remember password was not ticked before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1478222 Title: Ubuntu Touch forgets WiFi settings after first connection. EDUROAM network WPA WPA2 Enterprise Status in indicator-network package in Ubuntu: New Bug description: Using WPA WPA2 Enterprise I connected to the EDUROAM WiFi network with Ubuntu Touch. This works fine. However, when leaving the WiFi range and coming back, Ubuntu Touch will not be able to connect again. It asks again for the password, but the correct password does not work anymore. The only (annoying) workaround is to delete EDUROAM network from previous networks in the WiFi setting and then apply all setting again. The WiFi access will work then until one leaves the WiFi range again. Additional info: The EDUROAM WiFi network is a unified WiFi network to get access almost any European University. Default set-up is described here: http://www.urz.uni-heidelberg.de/zugang/eduroam/linux_ubuntu.html System: Ubuntu Touch 15.04(r24). Device-Built: KRILIN01A-S15A_BQ_L100EN_2024_150713 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1478222/+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 1478222] [NEW] Ubuntu Touch forgets WiFi settings after first connection. EDUROAM network WPA WPA2 Enterprise
Public bug reported: Using WPA WPA2 Enterprise I connected to the EDUROAM WiFi network with Ubuntu Touch. This works fine. However, when leaving the WiFi range and coming back, Ubuntu Touch will not be able to connect again. It asks again for the password, but the correct password does not work anymore. The only (annoying) workaround is to delete EDUROAM network from previous networks in the WiFi setting and then apply all setting again. The WiFi access will work then until one leaves the WiFi range again. Additional info: The EDUROAM WiFi network is a unified WiFi network to get access almost any European University. Default set-up is described here: http://www.urz.uni-heidelberg.de/zugang/eduroam/linux_ubuntu.html System: Ubuntu Touch 15.04(r24). Device-Built: KRILIN01A-S15A_BQ_L100EN_2024_150713 ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1478222 Title: Ubuntu Touch forgets WiFi settings after first connection. EDUROAM network WPA WPA2 Enterprise Status in indicator-network package in Ubuntu: New Bug description: Using WPA WPA2 Enterprise I connected to the EDUROAM WiFi network with Ubuntu Touch. This works fine. However, when leaving the WiFi range and coming back, Ubuntu Touch will not be able to connect again. It asks again for the password, but the correct password does not work anymore. The only (annoying) workaround is to delete EDUROAM network from previous networks in the WiFi setting and then apply all setting again. The WiFi access will work then until one leaves the WiFi range again. Additional info: The EDUROAM WiFi network is a unified WiFi network to get access almost any European University. Default set-up is described here: http://www.urz.uni-heidelberg.de/zugang/eduroam/linux_ubuntu.html System: Ubuntu Touch 15.04(r24). Device-Built: KRILIN01A-S15A_BQ_L100EN_2024_150713 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1478222/+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
