[Desktop-packages] [Bug 2048481] [NEW] Graphics Glitch (Screen Unusable) On Boot
Public bug reported: When I boot, I get to an unusable screen with the pointer stuck in the middle. If I use 'nomodeset' as a kernel boot parameter, I am able to get into the desktop. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: LXQt Date: Sun Jan 7 19:57:17 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. GT215 [GeForce GT 240] [1682:3001] InstallationDate: Installed on 2024-01-05 (3 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240103) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 8086:0808 Intel Corp. USB PnP Sound Device Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdc3 nomodeset SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: EPoX MCP61 Series dmi.board.vendor: EPoX COMPUTER CO., LTD dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/09/2007:svn:pn:pvr:rvnEPoXCOMPUTERCO.,LTD:rnEPoXMCP61Series:rvr1.x:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.117-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.0-2ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble reproducible single-occurrence ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/2048481 Title: Graphics Glitch (Screen Unusable) On Boot Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: When I boot, I get to an unusable screen with the pointer stuck in the middle. If I use 'nomodeset' as a kernel boot parameter, I am able to get into the desktop. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: LXQt Date: Sun Jan 7 19:57:17 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. GT215 [GeForce GT 240] [1682:3001] InstallationDate: Installed on 2024-01-05 (3 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240103) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 8086:0808 Intel Corp. USB PnP Sound Device Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdc3 nomodeset SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: EPoX MCP61 Series dmi.board.vendor: EPoX COMPUTER CO., LTD dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/09/2007:svn:pn:pvr:rvnEPoXCOMPUTERCO.,LTD:rnEPoXMCP61Series:rvr1.x:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.117-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.0-2ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.10-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1796649] Re: gjs-console crashed with SIGABRT in g_assertion_message()
I got this while launching steam. Automatic crash report. I've also never used gnome-sound-recorder -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1796649 Title: gjs-console crashed with SIGABRT in g_assertion_message() Status in gjs package in Ubuntu: Confirmed Bug description: Problem is from using the application "gnome-sound-recorder" (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:42.848: Some code accessed the property 'Application' on the module 'application'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Gjs-Message: 17:44:42.968: JS LOG: Sound Recorder started Gjs-Message: 17:44:42.969: JS WARNING: [resource:///org/gnome/SoundRecorder/js/application.js 84]: Too many arguments to function Gst.init: expected 1, got 2 (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.087: Some code accessed the property 'MainWindow' on the module 'mainWindow'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.087: Some code accessed the property 'AudioProfile' on the module 'audioProfile'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.088: Some code accessed the property 'OffsetController' on the module 'fileUtil'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.088: Some code accessed the property 'DisplayTime' on the module 'fileUtil'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.090: Some code accessed the property 'Listview' on the module 'listview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.090: Some code accessed the property 'Record' on the module 'record'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.091: Some code accessed the property 'Play' on the module 'play'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Gjs-Message: 17:44:43.309: JS WARNING: [resource:///org/gnome/SoundRecorder/js/listview.js 110]: reference to undefined property 1 (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.309: Some code accessed the property 'displayTime' on the module 'mainWindow'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
[Desktop-packages] [Bug 1796649] Re: gjs-console crashed with SIGABRT in g_assertion_message()
I get this in my Ubuntu 22.10 installation. As far as I know, I've never invoked the gnome sound recorder. I have used the ubuntustudio-installer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1796649 Title: gjs-console crashed with SIGABRT in g_assertion_message() Status in gjs package in Ubuntu: Confirmed Bug description: Problem is from using the application "gnome-sound-recorder" (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:42.848: Some code accessed the property 'Application' on the module 'application'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Gjs-Message: 17:44:42.968: JS LOG: Sound Recorder started Gjs-Message: 17:44:42.969: JS WARNING: [resource:///org/gnome/SoundRecorder/js/application.js 84]: Too many arguments to function Gst.init: expected 1, got 2 (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.087: Some code accessed the property 'MainWindow' on the module 'mainWindow'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.087: Some code accessed the property 'AudioProfile' on the module 'audioProfile'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.088: Some code accessed the property 'OffsetController' on the module 'fileUtil'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.088: Some code accessed the property 'DisplayTime' on the module 'fileUtil'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.090: Some code accessed the property 'Listview' on the module 'listview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.090: Some code accessed the property 'Record' on the module 'record'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.091: Some code accessed the property 'Play' on the module 'play'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Gjs-Message: 17:44:43.309: JS WARNING: [resource:///org/gnome/SoundRecorder/js/listview.js 110]: reference to undefined property 1 (org.gnome.SoundRecorder:30542): Gjs-WARNING **: 17:44:43.309: Some code accessed the property 'displayTime' on the module 'mainWindow'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but
Re: [Desktop-packages] [Bug 1973464] Re: Firefox does not supply name when it asks to open default keyring in Lubuntu 20.04
Please see attached the ubuntu-bug attachment, and let me know if I still need to do this again. Thanks! On Sun, May 15, 2022 at 10:05 PM Chris Guiver <1973...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please execute the following command only once, as it > will automatically gather debugging information, in a terminal: > > apport-collect 1973464 > > When reporting bugs in the future please use apport by using 'ubuntu- > bug' and the name of the package affected. You can learn more about this > functionality at https://wiki.ubuntu.com/ReportingBugs. > > > (please run it on the impacted box; so details can be correctly populated > allowing exploration using tools) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1973464 > > Title: > Firefox does not supply name when it asks to open default keyring in > Lubuntu 20.04 > > Status in firefox package in Ubuntu: > New > > Bug description: > When using auto-login in Lubuntu 20.04 LTS, browsing firefox causes > firefox to send a request to the default keyring to unlock. > > The problem is, it doesn't provide any information about what > application is making the request. This can be disorienting to the > user, especially since the security prompt locks out the system until > you enter the password or press cancel, with no hints about why you're > getting the message. > > Image: application asking to unlock default keyring. > https://i.ibb.co/4K36pqT/48cce3e1-abfc-4b12-9561-acb2a78da7bd.jpg > > I have verified that it is firefox, by removing > ~/.local/share/keyrings directory, and restarting the system. When > firefox is opened again, you get a new message asking you to create a > new password for the default keyring. > > Image: Opening firefox prompts the creation of a new password for the > default keyring. > https://i.ibb.co/RpSJ8L6/4fda479e-4603-4330-80cf-e2bc20643a61.jpg > > I am not sure what program is handling the default keyring on lubuntu. > Would it be possible for firefox to supply its name when interacting > with the default keyring? > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973464/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1973464 Title: Firefox does not supply name when it asks to open default keyring in Lubuntu 20.04 Status in firefox package in Ubuntu: New Bug description: When using auto-login in Lubuntu 20.04 LTS, browsing firefox causes firefox to send a request to the default keyring to unlock. The problem is, it doesn't provide any information about what application is making the request. This can be disorienting to the user, especially since the security prompt locks out the system until you enter the password or press cancel, with no hints about why you're getting the message. Image: application asking to unlock default keyring. https://i.ibb.co/4K36pqT/48cce3e1-abfc-4b12-9561-acb2a78da7bd.jpg I have verified that it is firefox, by removing ~/.local/share/keyrings directory, and restarting the system. When firefox is opened again, you get a new message asking you to create a new password for the default keyring. Image: Opening firefox prompts the creation of a new password for the default keyring. https://i.ibb.co/RpSJ8L6/4fda479e-4603-4330-80cf-e2bc20643a61.jpg I am not sure what program is handling the default keyring on lubuntu. Would it be possible for firefox to supply its name when interacting with the default keyring? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973464] [NEW] Firefox does not supply name when it asks to open default keyring in Lubuntu 20.04
Public bug reported: When using auto-login in Lubuntu 20.04 LTS, browsing firefox causes firefox to send a request to the default keyring to unlock. The problem is, it doesn't provide any information about what application is making the request. This can be disorienting to the user, especially since the security prompt locks out the system until you enter the password or press cancel, with no hints about why you're getting the message. Image: application asking to unlock default keyring. https://i.ibb.co/4K36pqT/48cce3e1-abfc-4b12-9561-acb2a78da7bd.jpg I have verified that it is firefox, by removing ~/.local/share/keyrings directory, and restarting the system. When firefox is opened again, you get a new message asking you to create a new password for the default keyring. Image: Opening firefox prompts the creation of a new password for the default keyring. https://i.ibb.co/RpSJ8L6/4fda479e-4603-4330-80cf-e2bc20643a61.jpg I am not sure what program is handling the default keyring on lubuntu. Would it be possible for firefox to supply its name when interacting with the default keyring? ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Attachment added: "apport information" https://bugs.launchpad.net/bugs/1973464/+attachment/5589848/+files/apport.firefox.k3utv7sf.apport -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1973464 Title: Firefox does not supply name when it asks to open default keyring in Lubuntu 20.04 Status in firefox package in Ubuntu: New Bug description: When using auto-login in Lubuntu 20.04 LTS, browsing firefox causes firefox to send a request to the default keyring to unlock. The problem is, it doesn't provide any information about what application is making the request. This can be disorienting to the user, especially since the security prompt locks out the system until you enter the password or press cancel, with no hints about why you're getting the message. Image: application asking to unlock default keyring. https://i.ibb.co/4K36pqT/48cce3e1-abfc-4b12-9561-acb2a78da7bd.jpg I have verified that it is firefox, by removing ~/.local/share/keyrings directory, and restarting the system. When firefox is opened again, you get a new message asking you to create a new password for the default keyring. Image: Opening firefox prompts the creation of a new password for the default keyring. https://i.ibb.co/RpSJ8L6/4fda479e-4603-4330-80cf-e2bc20643a61.jpg I am not sure what program is handling the default keyring on lubuntu. Would it be possible for firefox to supply its name when interacting with the default keyring? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1517884] Re: libxp6 not available in wily
Hello! The lib need me in Ubuntu 16.04 too quickly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxp in Ubuntu. https://bugs.launchpad.net/bugs/1517884 Title: libxp6 not available in wily Status in libxp package in Ubuntu: Confirmed Bug description: libxp6:i386 is not available in 15.10/Wily but is needed. Citrix Icaclient depends on it and will not work without it. It would be nice to have it in the repos again. lsb_release -rd Description: Ubuntu 15.10 Release: 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxp/+bug/1517884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
