[Desktop-packages] [Bug 1751479] Re: Firefox always show download "Failed" even if it downloads successfully
** Bug watch added: Mozilla Bugzilla #1440679 https://bugzilla.mozilla.org/show_bug.cgi?id=1440679 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1440679 Importance: Unknown Status: Unknown ** Changed in: firefox (Ubuntu) Status: Incomplete => New -- 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/1751479 Title: Firefox always show download "Failed" even if it downloads successfully Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: New Bug description: Firefox version: Installed: 58.0.2+build1-0ubuntu0.16.04.1 Candidate: 58.0.2+build1-0ubuntu0.16.04.1 Version table: *** 58.0.2+build1-0ubuntu0.16.04.1 500 500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial-updates/main arm64 Packages 500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial-security/main arm64 Packages 100 /var/lib/dpkg/status 45.0.2+build1-0ubuntu1 500 500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial/main arm64 Packages Architecture: Arm64 (aarch64) Distro (lsb_release): Ubuntu xenial 16.04.4 LTS Desktop Environment: Xfce 4.12 and Mate 1.20 Hardware: Samsung Chromebook plus with crouton (a Ubuntu Xenial chroot) installed. What I did: I want to download files in Firefox. Just open any website, click "Download" link. Actual results: I can not see my downloading items on browser panel, it just says "No downloads for this session". What's more, if I click "Show all downloads", I can see my downloading items whose status is "Failed". However, I can confirm it's downloading background successfully, and the downloaded file appears on my computer. I tried to remove my profile, say, the ".mozilla" folder, and downloaded again, but nothing improved. Expected results: It should download successfully. I just downgrade my Firefox to 57.x, everything is fine, and this downloading issue is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1751479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1784969] Re: upowerd segfaults over and over again.
I am no longer running this version. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Fri, 15 Feb 2019, Sebastien Bacher wrote: > Date: Fri, 15 Feb 2019 15:27:30 - > From: Sebastien Bacher > Reply-To: Bug 1784969 <1784...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1784969] Re: upowerd segfaults over and over again. > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please try to obtain a backtrace following the > instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload > the backtrace (as an attachment) to the bug report. This will greatly > help us in tracking down your problem. > > ** Changed in: upower (Ubuntu) > Importance: Undecided => High > > ** Changed in: upower (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1784969 > > Title: > upowerd segfaults over and over again. > > Status in upower package in Ubuntu: > Incomplete > > Bug description: > [392516.984355] upowerd[29614]: segfault at 8 ip 55e142176d50 sp > 7ffe615a51e0 error 4 in upowerd[55e142156000+39000] > [392542.249963] upowerd[29775]: segfault at 8 ip 55a107c1bd50 sp > 7ffd1d444f80 error 4 in upowerd[55a107bfb000+39000] > [392567.755465] upowerd[29946]: segfault at 8 ip 561edaf8cd50 sp > 7ffe03101330 error 4 in upowerd[561edaf6c000+39000] > [392592.998110] upowerd[30107]: segfault at 8 ip 558da7db8d50 sp > 7fffbcfece90 error 4 in upowerd[558da7d98000+39000] > [392618.233396] upowerd[30291]: segfault at 8 ip 5652ae549d50 sp > 7ffdddb529b0 error 4 in upowerd[5652ae529000+39000] > [392643.491371] upowerd[30732]: segfault at 8 ip 559c184dcd50 sp > 7fffac9cd460 error 4 in upowerd[559c184bc000+39000] > [392668.986076] upowerd[30945]: segfault at 8 ip 5569d2f0ad50 sp > 7ffc0b9c03d0 error 4 in upowerd[5569d2eea000+39000] > [392694.258076] upowerd[31245]: segfault at 8 ip 561c77151d50 sp > 7fff74956fa0 error 4 in upowerd[561c77131000+39000] > [392719.508055] upowerd[31409]: segfault at 8 ip 55d251c39d50 sp > 7ffe514025c0 error 4 in upowerd[55d251c19000+39000] > [392744.757247] upowerd[31569]: segfault at 8 ip 55fadf695d50 sp > 7ffe581d4d10 error 4 in upowerd[55fadf675000+39000] > [392770.004408] upowerd[31739]: segfault at 8 ip 55dce3cc1d50 sp > 7ffe812efda0 error 4 in upowerd[55dce3ca1000+39000] > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: upower 0.99.7-2 > ProcVersionSignature: Ubuntu 4.15.0-26.28-lowlatency 4.15.18 > Uname: Linux 4.15.0-26-lowlatency x86_64 > ApportVersion: 2.20.9-0ubuntu7.3 > Architecture: amd64 > CurrentDesktop: MATE > Date: Wed Aug 1 01:55:16 2018 > SourcePackage: upower > UpgradeStatus: Upgraded to bionic on 2018-07-04 (27 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1784969/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1784969 Title: upowerd segfaults over and over again. Status in upower package in Ubuntu: Incomplete Bug description: [392516.984355] upowerd[29614]: segfault at 8 ip 55e142176d50 sp 7ffe615a51e0 error 4 in upowerd[55e142156000+39000] [392542.249963] upowerd[29775]: segfault at 8 ip 55a107c1bd50 sp 7ffd1d444f80 error 4 in upowerd[55a107bfb000+39000] [392567.755465] upowerd[29946]: segfault at 8 ip 561edaf8cd50 sp 7ffe03101330 error 4 in upowerd[561edaf6c000+39000] [392592.998110] upowerd[30107]: segfault at 8 ip 558da7db8d50 sp 7fffbcfece90 error 4 in upowerd[558da7d98000+39000] [392618.233396] upowerd[30291]: segfault at 8 ip 5652ae549d50 sp 7ffdddb529b0 error 4 in upowerd[5652ae529000+39000] [392643.491371] upowerd[30732]: segfault at 8 ip 559c184dcd50 sp 7fffac9cd460 error 4 in upowerd[559c184bc000+39000] [392668.986076] upowerd[30945]: segfault at 8 ip 5569d2f0ad50 sp 7ffc0b9c03d0 error 4 in upowerd[5569d2eea000+39000] [392694.258076] upowerd[31245]: segfault at 8 ip 561c77151d50 sp 7fff74956fa0 error 4 in upowerd[561c77131000+39000] [392719.508055] upowerd[31409]: segfault at 8 ip 55d251c39d50 sp 7ffe514025c0 error 4 in upowerd[55d251c19000+39000] [392744.757247] upowerd[31569]: segfault at 8 ip 55fadf695d50 sp 7ffe581d4d10 error 4 in upowerd[55fadf675000+39000] [392770.004408] upowerd[31739]: segfault at 8 ip 55dce3cc1d50 sp 7ffe812efda0 error 4 in upowerd[55dce3ca1000+39000]
[Desktop-packages] [Bug 1816032] Re: gtk_widget_destroy reports error
The original package noted was a mistake. The nearest I can guess at for this problem is as above. I couldn't find anything that was obvious for a problem Gtk+3.0 development ** Package changed: ubuntu => libcanberra (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error Status in libcanberra package in Ubuntu: Incomplete Bug description: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1816032/+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 1816032] Re: gtk_widget_destroy reports error
** Package changed: network-manager-applet (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error Status in libcanberra package in Ubuntu: Incomplete Bug description: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1816032/+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 1816032] [NEW] gtk_widget_destroy reports error
You have been subscribed to a public bug: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages ** Affects: libcanberra (Ubuntu) Importance: Low Status: Incomplete ** Tags: destroy gtk widget -- gtk_widget_destroy reports error https://bugs.launchpad.net/bugs/1816032 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. -- 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 1816032] Re: gtk_widget_destroy reports error
Apologies for the mess up. I was looking at a similar bug listed for the network applet. I thought I had changed it, but the first time I tried to save I had a timeout and had to re-enter the details all over. Somehow the network applet must have been set when I re-entered. It was meant to a problem with Gtk+3.0 Dev. Sample code to reproduced is attached. ** Attachment added: "test_cbox_destroy.c" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1816032/+attachment/5239013/+files/test_cbox_destroy.c -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error Status in Ubuntu: Incomplete Bug description: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1816032/+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 1816216] [NEW] audio stutter
Public bug reported: Every time I play audio in my web browser I get what can only be described as a stutter or hiccup, its very random, so not really sure if its related to firefox or not. My system is a Acer aspire XC_-603 1tb hard drive 4 g ram the sound card and video card are integrated on the mother board so i cannot replace them. its really annoying any assistance is greatly appreciated I'm no expert so my knowledge is pretty raw ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 65.0+build2-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrew 4295 F pulseaudio BuildID: 20190128173924 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 16:11:04 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-02-09 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.0.1 dev enp3s0 proto dhcp metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.8 metric 100 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=65.0/20190128173924 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-B1 dmi.board.name: Aspire XC-603 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-B1:bd06/16/2014:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Aspire XC-603 dmi.sys.vendor: Acer ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1816216 Title: audio stutter Status in firefox package in Ubuntu: New Bug description: Every time I play audio in my web browser I get what can only be described as a stutter or hiccup, its very random, so not really sure if its related to firefox or not. My system is a Acer aspire XC_-603 1tb hard drive 4 g ram the sound card and video card are integrated on the mother board so i cannot replace them. its really annoying any assistance is greatly appreciated I'm no expert so my knowledge is pretty raw ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 65.0+build2-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrew 4295 F pulseaudio BuildID: 20190128173924 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 16:11:04 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-02-09 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.0.1 dev enp3s0 proto dhcp metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.8 metric 100 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=65.0/20190128173924 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2014 dmi.bios.vendor: American Megatrends
[Desktop-packages] [Bug 1808223] Re: gnome-calendar isn't caching calendar entries
[Expired for gnome-calendar (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-calendar (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1808223 Title: gnome-calendar isn't caching calendar entries Status in gnome-calendar package in Ubuntu: Expired Bug description: As described above. After every reboot the GNOME calendar is reloading all the calendar entries which means that if you have no access to the internet your calendar entries are not there. Often makes it impossible to work with the calendar. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-calendar 3.30.0-1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 21:47:53 2018 InstallationDate: Installed on 2018-11-30 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1808223/+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 1808658] Re: display goes blank and system hangs after (and sometimes before) gdm3 login with nvidia-driver-390 and a gtx 970m
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1808658 Title: display goes blank and system hangs after (and sometimes before) gdm3 login with nvidia-driver-390 and a gtx 970m Status in gdm3 package in Ubuntu: Expired Bug description: After entering username and password, gnome3 never loads, and instead you are stuck on a blank screen. Switching tty doesn't work. Sometimes gdm3 doesn't even load and the blank screen happens before you can try to log in. Without a workaround, you are forced to boot into recovery mode and purge nvidia, reverting back to nouveau. At first glance, this seems similar to this bug: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-390/+bug/1752053/+index?comments=all However, none of the solutions listed there work and the workaround is to use lightdm instead of gdm3: sudo apt install lightdm If it doesn't ask you to set the default display manager, then do this after, and set lightdm as the default when prompted: sudo dpkg-reconfigure gdm3 After that, the system will boot and let you log in normally. This problem is happening on a Clevo laptop without Optimus, with a dedicated nvidia gtx 970m device, after installing any of the modern nvidia drivers from version 390 onward, from the official repo, from the graphics PPA, and I presume also the official driver from the nvidia site. I tested on both Ubuntu 18.04.1 + updates, and Ubuntu 18.10 + updates. I tested with nvidia driver versions 390, 396, and 415. gdm3 works fine until you install the nvidia driver. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-15 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.30.1-1ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1808658/+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 1808903] Re: cannot connect LG Smart TV using HDMI Cable
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1808903 Title: cannot connect LG Smart TV using HDMI Cable Status in gnome-shell package in Ubuntu: Expired Bug description: when I tried connecting to the LG smart TV with an HDMI cable. Display options are very limited, unlike when I connect to an LG monitor using a VGA cable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 09:55:20 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-28 (80 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808903/+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 1751479] Re: Firefox always show download "Failed" even if it downloads successfully
Hi, it's still an issue in current supported version. -- 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/1751479 Title: Firefox always show download "Failed" even if it downloads successfully Status in firefox package in Ubuntu: Incomplete Bug description: Firefox version: Installed: 58.0.2+build1-0ubuntu0.16.04.1 Candidate: 58.0.2+build1-0ubuntu0.16.04.1 Version table: *** 58.0.2+build1-0ubuntu0.16.04.1 500 500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial-updates/main arm64 Packages 500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial-security/main arm64 Packages 100 /var/lib/dpkg/status 45.0.2+build1-0ubuntu1 500 500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial/main arm64 Packages Architecture: Arm64 (aarch64) Distro (lsb_release): Ubuntu xenial 16.04.4 LTS Desktop Environment: Xfce 4.12 and Mate 1.20 Hardware: Samsung Chromebook plus with crouton (a Ubuntu Xenial chroot) installed. What I did: I want to download files in Firefox. Just open any website, click "Download" link. Actual results: I can not see my downloading items on browser panel, it just says "No downloads for this session". What's more, if I click "Show all downloads", I can see my downloading items whose status is "Failed". However, I can confirm it's downloading background successfully, and the downloaded file appears on my computer. I tried to remove my profile, say, the ".mozilla" folder, and downloaded again, but nothing improved. Expected results: It should download successfully. I just downgrade my Firefox to 57.x, everything is fine, and this downloading issue is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1751479/+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 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
Nothing about Bionic yet? Still need the "CLUTTER_DEFAULT_FPS" workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Cosmic: In Progress Bug description: Monitor is set to 144hz, but on Wayland it visually fails to go above 60Hz. I have confirmed the monitor is running at 144Hz during the Wayland session, and that is also the setting in the Settings control panel. Using the additional NVidia drivers installed using the Ubuntu software control panel. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libwayland-bin (not installed) ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 08:43:29 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070] [1462:3301] InstallationDate: Installed on 2018-03-30 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0610 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+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 1805523] Re: System Sound Events Not Playing even when enabled
It seems like only some of the sounds are triggered. Like if I add the 'empty-trash' or 'item-delete' file from the freedesktop name spec (http://0pointer.de/public/sound-naming-spec.html), non of them are played. Is there a place/setting when you can enable/disable sound for certain events? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1805523 Title: System Sound Events Not Playing even when enabled Status in libcanberra package in Ubuntu: Confirmed Bug description: Expected Behavior: Doing something like displaying a warning or error should play an error sound. Actual Behavior: Some events don't play sounds at all when they should, even though the event-sounds setting is enabled through dconf or Tweaks. The other Yaru system sounds are present in /usr/share/sounds/Yaru yet nothing still plays. Some sounds that do play is the warning that appears when closing multiple tabs in firefox, and inserting a usb device To reproduce: Do something that should produce an error or warning noise, like emptying the trash or quitting terminal with a running process open. The sound theme is installed from apt repository, yaru-theme-sound version 18.10.6 I'm not 100% certain this package is the culprit, but here's the info: libcanberra version: 0.30-6ubuntu1 Ubuntu version 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libcanberra0 0.30-6ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 27 16:49:51 2018 InstallationDate: Installed on 2018-11-25 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libcanberra UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1805523/+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 1816206] Re: ext4 partition not created as specified
I think the collage of screenshots were missing. ** Attachment added: "collage.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1816206/+attachment/5238982/+files/collage.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1816206 Title: ext4 partition not created as specified Status in gnome-disk-utility package in Ubuntu: New Bug description: I have 26GB free at the begin of the drive and create a extended partition in that area and that went OK. While trying to create a 18GB ext4 partition in that extended partition, that extended partition is completely f$$cked up. See the collage of screenshots in the annex. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Feb 15 20:14:37 2019 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1816206/+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 1816206] [NEW] ext4 partition not created as specified
Public bug reported: I have 26GB free at the begin of the drive and create a extended partition in that area and that went OK. While trying to create a 18GB ext4 partition in that extended partition, that extended partition is completely f$$cked up. See the collage of screenshots in the annex. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Feb 15 20:14:37 2019 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "collage.jpg" https://bugs.launchpad.net/bugs/1816206/+attachment/5238978/+files/collage.jpg ** Description changed: - I have 26GB free at the begin of the drive and create a extended partition in that area and that went OK. While trying to create a 128GB ext4 partition in that extended partition, that extended partition is completely f$$cked up. + I have 26GB free at the begin of the drive and create a extended partition in that area and that went OK. While trying to create a 18GB ext4 partition in that extended partition, that extended partition is completely f$$cked up. See the collage of screenshots in the annex. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Feb 15 20:14:37 2019 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1816206 Title: ext4 partition not created as specified Status in gnome-disk-utility package in Ubuntu: New Bug description: I have 26GB free at the begin of the drive and create a extended partition in that area and that went OK. While trying to create a 18GB ext4 partition in that extended partition, that extended partition is completely f$$cked up. See the collage of screenshots in the annex. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Feb 15 20:14:37 2019 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1816206/+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 1816171] Re: Show menubar by default in new terminals has no effect
Thanks for the report! I can confirm this; forwarded to: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/81 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1816171 Title: Show menubar by default in new terminals has no effect Status in gnome-terminal package in Ubuntu: Confirmed Bug description: I open a terminal window. No menubar is displayed. From the 'amburger' menu I select Preferences and 'Show menubar by default in new terminals' nothing happens and next time I open a terminal i have no menubar. If i right click on the terminal window and select 'Show menubar' i see the menubar but this option is not remembered next time i open a terminal. corrado@corrado-p6-dd-0215:~$ apt policy gnome-terminal gnome-terminal: Installed: 3.31.90-1ubuntu1 Candidate: 3.31.90-1ubuntu1 Version table: *** 3.31.90-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p6-dd-0215:~$ inxi -SCGx System: Host: corrado-p6-dd-0215 Kernel: 4.19.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco Dingo) CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.2 direct render: Yes corrado@corrado-p6-dd-0215:~$ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 19:39:13 2019 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2019-02-15 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190215) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1816171/+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 1816205] Re: When using the Gedit icons they disappear from the desktop
n this case it was possible to use ubuntu -bug -w normally to generate the report as it was available and opened on the desktop. Neste caso foi possível usar o ubuntu-bug -w normalmente para gerar o relatório. pois estava disponível e aberto na área de trabalho. ** Attachment added: "Ícones somem" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1816205/+attachment/5238977/+files/Captura%20de%20tela%20de%202019-02-15%2021-48-28.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1816205 Title: When using the Gedit icons they disappear from the desktop Status in gedit package in Ubuntu: New Bug description: Hello guys When you open Gedit and edit any text or not, and click save, the desktop icons disappear, disappear, and move from side to side. After you click save the icons reappear again. The following images are attached: * Olá Pessoal Ao abrir o Gedit e editar qualquer texto ou não, e clicarmos em salvar, os ícones da área de trabalho desaparecem, somem e se movem de um lado para o outro. Após clicar em salvar os ícones reaparecem novamente. Segue imagens em anexo: ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gedit 3.31.90-1build1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 21:46:27 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-11 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1816205/+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 1816205] Re: When using the Gedit icons they disappear from the desktop
** Attachment added: "Ícones desaparecem" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1816205/+attachment/5238976/+files/Captura%20de%20tela%20de%202019-02-15%2021-48-10.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1816205 Title: When using the Gedit icons they disappear from the desktop Status in gedit package in Ubuntu: New Bug description: Hello guys When you open Gedit and edit any text or not, and click save, the desktop icons disappear, disappear, and move from side to side. After you click save the icons reappear again. The following images are attached: * Olá Pessoal Ao abrir o Gedit e editar qualquer texto ou não, e clicarmos em salvar, os ícones da área de trabalho desaparecem, somem e se movem de um lado para o outro. Após clicar em salvar os ícones reaparecem novamente. Segue imagens em anexo: ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gedit 3.31.90-1build1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 21:46:27 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-11 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1816205/+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 1816205] [NEW] When using the Gedit icons they disappear from the desktop
Public bug reported: Hello guys When you open Gedit and edit any text or not, and click save, the desktop icons disappear, disappear, and move from side to side. After you click save the icons reappear again. The following images are attached: * Olá Pessoal Ao abrir o Gedit e editar qualquer texto ou não, e clicarmos em salvar, os ícones da área de trabalho desaparecem, somem e se movem de um lado para o outro. Após clicar em salvar os ícones reaparecem novamente. Segue imagens em anexo: ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gedit 3.31.90-1build1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 21:46:27 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-11 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1816205 Title: When using the Gedit icons they disappear from the desktop Status in gedit package in Ubuntu: New Bug description: Hello guys When you open Gedit and edit any text or not, and click save, the desktop icons disappear, disappear, and move from side to side. After you click save the icons reappear again. The following images are attached: * Olá Pessoal Ao abrir o Gedit e editar qualquer texto ou não, e clicarmos em salvar, os ícones da área de trabalho desaparecem, somem e se movem de um lado para o outro. Após clicar em salvar os ícones reaparecem novamente. Segue imagens em anexo: ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gedit 3.31.90-1build1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 21:46:27 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-11 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1816205/+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 1816202] Re: Mesa version is old
** Attachment added: "glxinfo output for both GPUs." https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1816202/+attachment/5238970/+files/glxinfo_output -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1816202 Title: Mesa version is old Status in mesa package in Ubuntu: New Bug description: https://mesamatrix.net/ shows that OpenGL version for: Intel: 4.5. R600: 4.4. However, I get 4.2 for Intel and 3.3 for AMD. I think upgrading latest available version'd solve the problem. CPU: Intel Core i 5. GPU: Radeon HD 7670. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglapi-mesa 18.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 01:38:34 2019 Dependencies: gcc-8-base 8.2.0-7ubuntu1 libc6 2.28-0ubuntu1 libgcc1 1:8.2.0-7ubuntu1 libidn2-0 2.0.5-1 libunistring2 0.9.10-1ubuntu1 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:183e] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 7670M [103c:183e] InstallationDate: Installed on 2019-02-07 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=62a6c247-4374-447e-9f08-9ff03782230d ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1816202/+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 1816202] [NEW] Mesa version is old
Public bug reported: https://mesamatrix.net/ shows that OpenGL version for: Intel: 4.5. R600: 4.4. However, I get 4.2 for Intel and 3.3 for AMD. I think upgrading latest available version'd solve the problem. CPU: Intel Core i 5. GPU: Radeon HD 7670. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglapi-mesa 18.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 01:38:34 2019 Dependencies: gcc-8-base 8.2.0-7ubuntu1 libc6 2.28-0ubuntu1 libgcc1 1:8.2.0-7ubuntu1 libidn2-0 2.0.5-1 libunistring2 0.9.10-1ubuntu1 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:183e] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 7670M [103c:183e] InstallationDate: Installed on 2019-02-07 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=62a6c247-4374-447e-9f08-9ff03782230d ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1816202 Title: Mesa version is old Status in mesa package in Ubuntu: New Bug description: https://mesamatrix.net/ shows that OpenGL version for: Intel: 4.5. R600: 4.4. However, I get 4.2 for Intel and 3.3 for AMD. I think upgrading latest available version'd solve the problem. CPU: Intel Core i 5. GPU: Radeon HD 7670. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglapi-mesa 18.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 01:38:34 2019 Dependencies: gcc-8-base 8.2.0-7ubuntu1 libc6 2.28-0ubuntu1 libgcc1 1:8.2.0-7ubuntu1 libidn2-0 2.0.5-1 libunistring2 0.9.10-1ubuntu1 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:183e] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 7670M [103c:183e] InstallationDate: Installed on 2019-02-07 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=62a6c247-4374-447e-9f08-9ff03782230d ro quiet splash vt.handoff=1
[Desktop-packages] [Bug 1816200] Re: Scrolling lag with AMD GPU
Mozilla Bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1383563. -- 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/1816200 Title: Scrolling lag with AMD GPU Status in firefox package in Ubuntu: New Status in firefox package in Fedora: New Bug description: If I start Firefox with AMD GPU and force-enabling hardware acceleration, I get scrolling delay (Page updates, after few seconds from scrolling with the touchpad). It only happens with AMD's GPU. Bug happens also with Snap version and in Fedora. Laptop: HP Pavilion g6. CPU: Intel Core i5. GPU: Radeon HD 7670. RAM: 8 GB. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox (not installed) ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 01:17:38 2019 InstallationDate: Installed on 2019-02-07 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1816200/+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 1816200] [NEW] Scrolling lag with AMD GPU
Public bug reported: If I start Firefox with AMD GPU and force-enabling hardware acceleration, I get scrolling delay (Page updates, after few seconds from scrolling with the touchpad). It only happens with AMD's GPU. Bug happens also with Snap version and in Fedora. Laptop: HP Pavilion g6. CPU: Intel Core i5. GPU: Radeon HD 7670. RAM: 8 GB. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox (not installed) ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 01:17:38 2019 InstallationDate: Installed on 2019-02-07 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Affects: firefox (Fedora) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session ** Also affects: firefox (Fedora) Importance: Undecided Status: New ** Bug watch added: Mozilla Bugzilla #1383563 https://bugzilla.mozilla.org/show_bug.cgi?id=1383563 -- 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/1816200 Title: Scrolling lag with AMD GPU Status in firefox package in Ubuntu: New Status in firefox package in Fedora: New Bug description: If I start Firefox with AMD GPU and force-enabling hardware acceleration, I get scrolling delay (Page updates, after few seconds from scrolling with the touchpad). It only happens with AMD's GPU. Bug happens also with Snap version and in Fedora. Laptop: HP Pavilion g6. CPU: Intel Core i5. GPU: Radeon HD 7670. RAM: 8 GB. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox (not installed) ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 01:17:38 2019 InstallationDate: Installed on 2019-02-07 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1816200/+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 1801540] Re: Microphone distorted sound on ALC892
i've the same Problem on Ubuntu 18.10. I'm running a Asus P9D-X (no Onboard Sound) with a Asus MIO 892 (Realtek)-Card which is detected as Intel-HDA: 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) cat /proc/asound/cards : 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xd321 irq 35 head -n 1 /proc/asound/card0/codec* : Codec: Realtek ALC892 lsmod | grep "^snd" | cut -d " " -f 1 : snd_seq_dummy snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_oxygen snd_oxygen_lib snd_mpu401_uart snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1732766] Re: firefox 57 does not display fish in fishgl.com on intel 530?
Launchpad has imported 4 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1418136. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-11-16T23:54:22+00:00 Dan Kegel wrote: Created attachment 8929233 badfish.png User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171115095126 Steps to reproduce: Downloaded firefox 57.0 from mozilla.org onto a dell 3620 running ubuntu 16.04, untarred it, used it to open http://fishgl.com (happens with ubuntu's 56 or 57, or 57 downloaded from mozilla.org; happens on two similar systems here, so it's not just one screwed up box. System info: cpu is i7-6700 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7 OpenGL core profile shading language version string: 4.50 Filed https://bugs.launchpad.net/bugs/1732766 for this problem on the ubuntu-sourced firefox 56 and 57) Actual results: After loading indicator hit 100%, it showed a static view of back wall of room (see screenshot) Expected results: Should have showed view of fish tank in room with fish swimming in it Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1732766/comments/2 On 2017-11-20T06:55:12+00:00 Bignose1007+bugzilla wrote: Could you upload your "about:support" page info here? Maybe we could find somethings wrong. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1732766/comments/5 On 2017-12-06T06:04:48+00:00 Dan Kegel wrote: Sure, here's about:support from one affected machine: http://kegel.com /firefox-fishgl/ubu1710.txt All my Intel Graphics ubuntu machines are affected. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1732766/comments/6 On 2019-02-15T22:25:01+00:00 Paul White wrote: Can confirm issue using Fedora 29 and Firefox 65 Graphics: Device-1: Intel HD Graphics 630 driver: i915 v: kernel Display: x11 server: Fedora Project X.org 1.20.3 driver: i915 resolution: 1368x768~60Hz, 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.2.8 Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1732766/comments/8 ** Changed in: firefox Status: Unknown => New ** Changed in: firefox Importance: Unknown => Medium -- 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/1732766 Title: firefox 57 does not display fish in fishgl.com on intel 530? Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: On my two intel graphics Ubuntu 16.04 systems (both Dell 3620's), firefox does not display any fish; it simply shows the back wall. OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7 OpenGL core profile shading language version string: 4.50 fishgl works fine in chrome, and on other ubuntu systems here. Affects both firefox 56.0+build6-0ubuntu0.16.04.2 and 57.0+build4-0ubuntu0.16.04.5 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 57.0+build4-0ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dank 1843 F...m pulseaudio /dev/snd/controlC0: dank 1843 F pulseaudio /dev/snd/controlC1: dank 1843 F pulseaudio BuildID: 20171115095126 Channel: Unavailable Date: Thu Nov 16 10:55:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 10.10.1.1 dev enp0s31f6 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.10.0.0/16 dev enp0s31f6 proto kernel scope link src 10.10.130.236 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. lxcbr0no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources:
[Desktop-packages] [Bug 1697890] Re: Ubuntu Modifications 3.2 disables Multi-Process electrolysis
** Package changed: firefox (Ubuntu) => ubufox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubufox in Ubuntu. https://bugs.launchpad.net/bugs/1697890 Title: Ubuntu Modifications 3.2 disables Multi-Process electrolysis Status in ubufox package in Ubuntu: Confirmed Bug description: Ubuntu Modifications 3.2 utilses the older plugin architecture that is pending deprecation in Firefox 57+ See https://developer.mozilla.org /en-US/Add- ons/Overlay_Extensions/XUL_School/Getting_Started_with_Firefox_Extensions. Enabling Ubuntu Modifications 3.2 automatically disables Multi-Process firefox for compatibility reasons. This hampers all the performance and security improvements that are part of the electrolysis project. Ubuntu Modifications 3.2 requires an update to support the new extension platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1697890/+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 1751479] Re: Firefox always show download "Failed" even if it downloads successfully
Is this still an issue with Firefox 65.0, the currently supported version? ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1751479 Title: Firefox always show download "Failed" even if it downloads successfully Status in firefox package in Ubuntu: Incomplete Bug description: Firefox version: Installed: 58.0.2+build1-0ubuntu0.16.04.1 Candidate: 58.0.2+build1-0ubuntu0.16.04.1 Version table: *** 58.0.2+build1-0ubuntu0.16.04.1 500 500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial-updates/main arm64 Packages 500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial-security/main arm64 Packages 100 /var/lib/dpkg/status 45.0.2+build1-0ubuntu1 500 500 https://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports xenial/main arm64 Packages Architecture: Arm64 (aarch64) Distro (lsb_release): Ubuntu xenial 16.04.4 LTS Desktop Environment: Xfce 4.12 and Mate 1.20 Hardware: Samsung Chromebook plus with crouton (a Ubuntu Xenial chroot) installed. What I did: I want to download files in Firefox. Just open any website, click "Download" link. Actual results: I can not see my downloading items on browser panel, it just says "No downloads for this session". What's more, if I click "Show all downloads", I can see my downloading items whose status is "Failed". However, I can confirm it's downloading background successfully, and the downloaded file appears on my computer. I tried to remove my profile, say, the ".mozilla" folder, and downloaded again, but nothing improved. Expected results: It should download successfully. I just downgrade my Firefox to 57.x, everything is fine, and this downloading issue is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1751479/+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 1732766] Re: firefox 57 does not display fish in fishgl.com on intel 530?
** Bug watch added: Mozilla Bugzilla #1418136 https://bugzilla.mozilla.org/show_bug.cgi?id=1418136 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1418136 Importance: Unknown Status: Unknown -- 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/1732766 Title: firefox 57 does not display fish in fishgl.com on intel 530? Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Confirmed Bug description: On my two intel graphics Ubuntu 16.04 systems (both Dell 3620's), firefox does not display any fish; it simply shows the back wall. OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7 OpenGL core profile shading language version string: 4.50 fishgl works fine in chrome, and on other ubuntu systems here. Affects both firefox 56.0+build6-0ubuntu0.16.04.2 and 57.0+build4-0ubuntu0.16.04.5 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 57.0+build4-0ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dank 1843 F...m pulseaudio /dev/snd/controlC0: dank 1843 F pulseaudio /dev/snd/controlC1: dank 1843 F pulseaudio BuildID: 20171115095126 Channel: Unavailable Date: Thu Nov 16 10:55:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 10.10.1.1 dev enp0s31f6 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.10.0.0/16 dev enp0s31f6 proto kernel scope link src 10.10.130.236 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. lxcbr0no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=57.0/20171115095126 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.6 dmi.board.name: 09WH54 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: Precision Tower 3620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1732766/+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 1816191] Re: Printers partially recognizes network printer, but isn't able to even print a test page
*** This bug is a duplicate of bug 1815307 *** https://bugs.launchpad.net/bugs/1815307 ** Description changed: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page Status in gnome-control-center package in Ubuntu: New Bug description: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or directory) Also driverless doesn't return anything (it says ipp://41182400.local:631/ipp/print on Ubuntu 18.04) And lpstat -e only occasionally reports seeing the printer (it works consistently on 18.04). Going to additional printer settings... and clicking on adding an ipp printer with the device URI ipp://41182400.local:631/ipp/print (which I know from 18.04 by typing driverless) and selecting the gutenprint driver for Canon Pixma iP7250 does work and prints the test page. But if I didn't know that URI (which I could not see using driverless on this vesion of Ubuntu) - I wouldn't have been able to add my printer. This is even a worse experience than in 18.04 - and the experience there was bad enough (as described in https://bugs.launchpad.net/ubuntu/+source/system-config- printer/+bug/1815307) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 20:38:48 2019 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1816191/+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 1815307] Re: ipp printer isn't shown automatically - adding it errors with a CUPS internal error
@fargoth, sorry for that comment. I was wrong. What got actually fixed was another thing which I observed during the investigations for this bug. Therefore I have re-opened https://github.com/OpenPrinting/cups-filters/issues/22 Please see my comments #5 and #6. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error Status in cups package in Ubuntu: Triaged Bug description: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenprint driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1815307/+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 1816191] Re: Printers partially recognizes network printer, but isn't able to even print a test page
*** This bug is a duplicate of bug 1815307 *** https://bugs.launchpad.net/bugs/1815307 ** This bug has been marked a duplicate of bug 1815307 ipp printer isn't shown automatically - adding it errors with a CUPS internal error -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page Status in gnome-control-center package in Ubuntu: New Bug description: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or directory) Also driverless doesn't return anything (it says ipp://41182400.local:631/ipp/print on Ubuntu 18.04) And lpstat -e only occasionally reports seeing the printer (it works consistently on 18.04). Going to additional printer settings... and clicking on adding an ipp printer with the device URI ipp://41182400.local:631/ipp/print (which I know from 18.04 by typing driverless) and selecting the gutenprint driver for Canon Pixma iP7250 does work and prints the test page. But if I didn't know that URI (which I could not see using driverless on this vesion of Ubuntu) - I wouldn't have been able to add my printer. This is even a worse experience than in 18.04 - and the experience there was bad enough (as described in https://bugs.launchpad.net/ubuntu/+source/system-config- printer/+bug/1815307) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 20:38:48 2019 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1816191/+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 1816191] Re: Printers partially recognizes network printer, but isn't able to even print a test page
*** This bug is a duplicate of bug 1815307 *** https://bugs.launchpad.net/bugs/1815307 ** Description changed: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or directory) Also driverless doesn't return anything (it says ipp://41182400.local:631/ipp/print on Ubuntu 18.04) And lpstat -e only occasionally reports seeing the printer (it works consistently on 18.04). + Going to additional printer settings... and clicking on adding an ipp + printer with the device URI ipp://41182400.local:631/ipp/print + (which I know from 18.04 by typing driverless) and selecting the + gutenprint driver for Canon Pixma iP7250 does work and prints the test + page. + + But if I didn't know that URI (which I could not see using driverless on + this vesion of Ubuntu) - I wouldn't have been able to add my printer. + This is even a worse experience than in 18.04 - and the experience there + was bad enough (as described in + https://bugs.launchpad.net/ubuntu/+source/system-config- + printer/+bug/1815307) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 20:38:48 2019 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page Status in gnome-control-center package in Ubuntu: New Bug description: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is
[Desktop-packages] [Bug 1449748] Re: gedit can't run in root terminal
** Package changed: ubuntu => gedit (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1449748 Title: gedit can't run in root terminal Status in One Hundred Papercuts: Confirmed Status in gedit package in Ubuntu: Confirmed Bug description: Folowing upgrade 14.10 -> 15.04, in a root terminal: root@adiabat:~# gedit No protocol specified ** (gedit:8757): WARNING **: Could not open X display No protocol specified gdk_mir_display_open Failed to connect to Mir: Failed to connect to server socket: No such file or directory Unable to init server: Could not connect: Connection refused (gedit:8757): Gtk-WARNING **: cannot open display: :0 root@adiabat:~# However, from a user terminal, " gedit" and "gksu gedit" both work just fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-release-upgrader-core 1:15.04.14 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Apr 28 13:55:28 2015 InstallationDate: Installed on 2014-11-04 (174 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to vivid on 2015-04-28 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1449748/+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 1815307] Re: ipp printer isn't shown automatically - adding it errors with a CUPS internal error
@till-kamppeter > The issues referenced in the previous comment are all fixed upstream now. If they were the cause for > your problem, your problem will be solved in Disco. I've just tested this using Disco, and it's even worse there - see my bug report: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1816191 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error Status in cups package in Ubuntu: Triaged Bug description: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenprint driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1815307/+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 837456] Re: XTestFakeKeyEvent changes keyboard mapping to 'us'
I can confirm this bug with Manjaro (xorg-server 1.20.3-1, KDE 5.14.5) and onboard-1.4.1-4. The Workaround 'setxkbmap de' is ok for my needs, but I'd rather help to fix the bug... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/837456 Title: XTestFakeKeyEvent changes keyboard mapping to 'us' Status in xorg-server package in Ubuntu: Confirmed Bug description: Typing with the onscreen keyboard Onboard on a system with German default layout immediately switches the keyboard layout to 'English (US)'. Touching any key on a physical keyboard switches back to the German default. This can be repeated indefinitely. Onboard uses XTestFakeKeyEvent to send key events. When switching from a physical keyboard to Onboard, the first call to this function leads to an unwanted MappingNotify event and the keyboard map changes from 'pc+de+inet(evdev)', 'German' to 'pc+us+inet(evdev)', 'English (US)'. Pressing any key on an attached USB keyboard switches back to 'pc+de+inet(evdev)', 'German'. Running any of the following temporarily fixes the problem for the current session: $ setxkbmap de $ sudo dpkg-reconfigure keyboard-configuration Restarting X brings back the unwanted layout switches. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz Date: Tue Aug 30 16:21:46 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Foxconn International, Inc. Device [105b:0df0] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110826) MachineType: OEM OEM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=3bee4cb7-392a-4347-a496-f32c7141e658 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: G31MG-S dmi.board.vendor: Foxconn dmi.board.version: FAB:1.0 dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/04/2008:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MG-S:rvrFAB1.0:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/837456/+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 1815307] Re: ipp printer isn't shown automatically - adding it errors with a CUPS internal error
A similar report got also to CUPS upstream: https://github.com/apple/cups/issues/5512 and it seems that there is either a firmware bug in the AirPrint- supporting Canon printers or some problem with the client-side IPP implementation (which is in libcups, part of CUPS). Michael Sweet, author of CUPS, will get a Canon printer on the coming Wednesday for further investigation. Moving this bug to CUPS, system-config-printer has nothing to do with it. ** Bug watch added: github.com/apple/cups/issues #5512 https://github.com/apple/cups/issues/5512 ** Package changed: system-config-printer (Ubuntu) => cups (Ubuntu) ** Changed in: cups (Ubuntu) Importance: Undecided => Medium ** Changed in: cups (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error Status in cups package in Ubuntu: Triaged Bug description: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenprint driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1815307/+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 1816191] Re: Printers partially recognizes network printer, but isn't able to even print a test page
** Description changed: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series - Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the + Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or directory) + + Also driverless doesn't return anything (it says + ipp://41182400.local:631/ipp/print on Ubuntu 18.04) + + And lpstat -e only occasionally reports seeing the printer (it works + consistently on 18.04). + ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 20:38:48 2019 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANG=C.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANG=C.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page Status in gnome-control-center package in Ubuntu: New Bug description: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or
[Desktop-packages] [Bug 1449748] [NEW] gedit can't run in root terminal
You have been subscribed to a public bug: Folowing upgrade 14.10 -> 15.04, in a root terminal: root@adiabat:~# gedit No protocol specified ** (gedit:8757): WARNING **: Could not open X display No protocol specified gdk_mir_display_open Failed to connect to Mir: Failed to connect to server socket: No such file or directory Unable to init server: Could not connect: Connection refused (gedit:8757): Gtk-WARNING **: cannot open display: :0 root@adiabat:~# However, from a user terminal, " gedit" and "gksu gedit" both work just fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-release-upgrader-core 1:15.04.14 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Apr 28 13:55:28 2015 InstallationDate: Installed on 2014-11-04 (174 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to vivid on 2015-04-28 (0 days ago) VarLogDistupgradeTermlog: ** Affects: hundredpapercuts Importance: Medium Status: Confirmed ** Affects: gedit (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-bug dist-upgrade vivid -- gedit can't run in root terminal https://bugs.launchpad.net/bugs/1449748 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. -- 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 1816191] [NEW] Printers partially recognizes network printer, but isn't able to even print a test page
Public bug reported: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or directory) Also driverless doesn't return anything (it says ipp://41182400.local:631/ipp/print on Ubuntu 18.04) And lpstat -e only occasionally reports seeing the printer (it works consistently on 18.04). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 20:38:48 2019 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page Status in gnome-control-center package in Ubuntu: New Bug description: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or directory) Also driverless doesn't return anything (it says ipp://41182400.local:631/ipp/print on Ubuntu 18.04) And lpstat -e only occasionally reports seeing the printer (it works consistently on 18.04). ProblemType: Bug
[Desktop-packages] [Bug 1801161] Re: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Solution: remove libreoffice-gtk2 and install libreoffice-gtk3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1801161 Title: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Status in libreoffice package in Ubuntu: Expired Bug description: Using LibreOffice Calc I was editing a filter on a pivot table and all LibreOffice windows hung. What appeared in /var/log/syslog was: Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Unknown sequence number while processing queue Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Aborting, sorry about that. Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Nov 1 13:32:27 santiago gnome-shell[8288]: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. 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. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice-calc 1:6.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 13:39:03 2018 InstallationDate: Installed on 2018-10-29 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161/+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 1815395] Re: GVFS-SMB write problems to SMB2 shares
Well, I'm not sure what the issue or fix was, but this issue can be closed. I posted the bug to the GVFS list and, amongst other suggestions, one of the maintainers noticed an error in the GVFS debug log of 2 malformed parameters in smb.conf min client protocol and max client protocol (vs the correct client min protocol and client max protocol). These nonsense parameters were also both set to SMB3 so the first thing I did was remove them from smb.conf before doing the other tests recommended. However, now my repeatable "issue" scenario writes the files properly (and the traces show a perfectly good response to the file info request that repeatedly returned access denied errors before, BUT the file creation parameter values are now different for no reason I can figure out). I tried adding the parameter lines back, as they were before, but I still can't recreate the issue. I also tried "fixing" those bad parameter lines and it prevented me from connecting to my SMB2 share at all, which I would expect when the client side is locked to SMB3. So after I pulled the lines again to let the client side negotiate naturally, I can't get the issue to happen again after repeated tests with different programs, some of which had consistent write problems and some of which had intermittent write problems. I didn't do any updates to the system in between when I posted this and when I "fixed" it and the one change I DID make I reversed, but it didn't cause the problem to recur. I suppose this is why I wanted to see if anyone could replicate this. I would bet now that they couldn't but I doubt I'll ever know what the actual issue was, now. Anyway, I'm closing this bug. Sorry for the false alarm. :) Thanks, Scott -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1815395 Title: GVFS-SMB write problems to SMB2 shares Status in gvfs package in Ubuntu: New Bug description: Summary: I believe there’s a bug in GVFS-SMB (or its implementation in Nautilus) that manifests when writing to SMB2 shares. It occurs inconsistently (but enough to be annoying) in everyday use, but it can be replicated consistently with a simple echo command redirected to a file on the share. This doesn’t happen when using the ‘mount’ command to connect to SMB2 shares. It also doesn’t happen when making an SMB1 connection through Nautilus OR mount. I’ve also tested this against 2 different SMB servers (a Synology DS216J and a share on a Win7 Pro system) and the results are consistent so I don’t believe it’s a server side issue. I don’t know enough about this part of the system to identify where the issue is or fix it, but I’ve included data below to show the basis for my assertions above. The workaround is either going back to SMB1 or mounting my shares with the mount command, but I was hoping someone could take this on and fix it long-term. As Microsoft progressively phases out SMB1, I think this will eventually become a wider scale problem so now would be an opportune time to address it. If there’s any further data I can provide, please let me know. Also, I’m sorry this bug report is so long, but I’m erring on the side of too much detail rather than too little. Detail: On my Ubuntu 18.04 system, when I attempt to echo a string into a file on a GVFS mounted share (left hand nav of Nautilus + Other Locations) and that share is configured to SMB1 (client side left to negotiate, server side locked to SMB1) this works as expected. I tested against SMB shares on both a Synology Diskstation DS216J NAS and a Windows 7 Professional workstation. When I was on Ubuntu 16.04 that was SMB1 only out of the box I didn’t know this problem even existed. Now that I’m on Ubuntu 18.04 and my share was willing to make connection at SMB2 I started to have weird, inconsistent disk problems. Much troubleshooting and analysis later, I can recreate this issue consistently with a simple echo command to a file on the share. To the SMB share on a Synology Diskstation NAS set to SMB1: echo "This is a test." > /run/user/1000/gvfs/smb- share\:server\=diskstation\,share\=fileshare/Test-File-SMB1-GVFS- NAS.txt The command executes with no feedback (other than the return of the prompt awaiting the next command) and the file of the name specified with the contents specified appears at the root of the NAS file share. To the SMB share on a Windows 7 Professional workstation set to SMB1: echo "This is a test." > /run/user/1000/gvfs/smb- share\:server\=hp_laptop\,share\=videos/Test-File-SMB1-GVFS-Win7.txt The command also executes with no feedback (other than the return of the prompt awaiting the next command) and the file of the name specified with the contents specified appears at the root of the “videos” file share on the Win7 workstation. I also took
[Desktop-packages] [Bug 1815395] Re: GVFS-SMB write problems to SMB2 shares
Sorry, spoke too soon. I'm not sure which status to change this to. It was never confirmed by anyone else, but the traces definitely showed something bad happening. Any suggestions what I should set the status to in order to properly file it away? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1815395 Title: GVFS-SMB write problems to SMB2 shares Status in gvfs package in Ubuntu: New Bug description: Summary: I believe there’s a bug in GVFS-SMB (or its implementation in Nautilus) that manifests when writing to SMB2 shares. It occurs inconsistently (but enough to be annoying) in everyday use, but it can be replicated consistently with a simple echo command redirected to a file on the share. This doesn’t happen when using the ‘mount’ command to connect to SMB2 shares. It also doesn’t happen when making an SMB1 connection through Nautilus OR mount. I’ve also tested this against 2 different SMB servers (a Synology DS216J and a share on a Win7 Pro system) and the results are consistent so I don’t believe it’s a server side issue. I don’t know enough about this part of the system to identify where the issue is or fix it, but I’ve included data below to show the basis for my assertions above. The workaround is either going back to SMB1 or mounting my shares with the mount command, but I was hoping someone could take this on and fix it long-term. As Microsoft progressively phases out SMB1, I think this will eventually become a wider scale problem so now would be an opportune time to address it. If there’s any further data I can provide, please let me know. Also, I’m sorry this bug report is so long, but I’m erring on the side of too much detail rather than too little. Detail: On my Ubuntu 18.04 system, when I attempt to echo a string into a file on a GVFS mounted share (left hand nav of Nautilus + Other Locations) and that share is configured to SMB1 (client side left to negotiate, server side locked to SMB1) this works as expected. I tested against SMB shares on both a Synology Diskstation DS216J NAS and a Windows 7 Professional workstation. When I was on Ubuntu 16.04 that was SMB1 only out of the box I didn’t know this problem even existed. Now that I’m on Ubuntu 18.04 and my share was willing to make connection at SMB2 I started to have weird, inconsistent disk problems. Much troubleshooting and analysis later, I can recreate this issue consistently with a simple echo command to a file on the share. To the SMB share on a Synology Diskstation NAS set to SMB1: echo "This is a test." > /run/user/1000/gvfs/smb- share\:server\=diskstation\,share\=fileshare/Test-File-SMB1-GVFS- NAS.txt The command executes with no feedback (other than the return of the prompt awaiting the next command) and the file of the name specified with the contents specified appears at the root of the NAS file share. To the SMB share on a Windows 7 Professional workstation set to SMB1: echo "This is a test." > /run/user/1000/gvfs/smb- share\:server\=hp_laptop\,share\=videos/Test-File-SMB1-GVFS-Win7.txt The command also executes with no feedback (other than the return of the prompt awaiting the next command) and the file of the name specified with the contents specified appears at the root of the “videos” file share on the Win7 workstation. I also took PCAPs of this occurring (attached). What they show is about what I would expect for this operation. Client SMB pings the server in packet 1 who responds in packet 2, queries info on the folder in packet 4 and gets some basic info back in packet 5, queries the filename (to make sure it doesn’t already exist) several times (not sure why), each time getting a name not found reply in packets 6 through 17, then creates the file in packet 18, gets back a success message in packet 19, queries info on the new file in packet 20, gets a success response in packet 21, writes the contents in packet 22, gets a good response in packet 23, queries the file one more time (presumably to make sure the new size is good) in packet 24, gets a response with the info in packet 25, requests the handle be closed in packet 26, and gets an OK to that in packet 27. This is all wonderful. Perhaps slightly inefficient, but I don’t know what’s going on under the hood, so who am I to judge? When I switch to SMB2 on the server side and reconnect via GVFS using Nautilus, things fall apart. To the SMB share on a Synology Diskstation NAS set to SMB2: echo "This is a test." > /run/user/1000/gvfs/smb- share\:server\=diskstation\,share\=fileshare/Test-File-SMB2-GVFS- NAS.txt returns bash: /run/user/1000/gvfs/smb-share:server=diskstation,share=fileshare /Test-File-SMB2-GVFS-NAS.txt: Invalid argument The file is where I expected it, but it is 0
[Desktop-packages] [Bug 1795702] Re: snap-store reports incorrect OS to odrs
Request for auto connecting system-observe https://forum.snapcraft.io/t /request-to-allow-snap-store-to-auto-connect-to-the-system-observe- interface/9987 ** Changed in: gnome-software (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1795702 Title: snap-store reports incorrect OS to odrs Status in gnome-software package in Ubuntu: Fix Committed Bug description: Install snap-store - "snap install snap-store" Snap store - "snap run snap-store" Find an application (I opened Wire) Scroll down and click "Write a review" Write a review. Find your review on ODRS https://odrs.gnome.org Note the "Distro" says "Ubuntu Core". This is not correct, as I am on KDE Neon right now. Here is mine. https://odrs.gnome.org/admin/review/9621 In case the content changes I have attached a screenshot. This error is likely because snap-store is a confined snap application. /etc/os-release is allowed in the default template. Note this will be of the core/base snap, not the host. To read the host, you can use the system-observe interface which exposes /var/lib/snapd/hostfs/etc/os- release to the snap from the host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1795702/+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 1795702] Re: snap-store reports incorrect OS to odrs
Note it does require connecting to the system-observe interface -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1795702 Title: snap-store reports incorrect OS to odrs Status in gnome-software package in Ubuntu: Fix Committed Bug description: Install snap-store - "snap install snap-store" Snap store - "snap run snap-store" Find an application (I opened Wire) Scroll down and click "Write a review" Write a review. Find your review on ODRS https://odrs.gnome.org Note the "Distro" says "Ubuntu Core". This is not correct, as I am on KDE Neon right now. Here is mine. https://odrs.gnome.org/admin/review/9621 In case the content changes I have attached a screenshot. This error is likely because snap-store is a confined snap application. /etc/os-release is allowed in the default template. Note this will be of the core/base snap, not the host. To read the host, you can use the system-observe interface which exposes /var/lib/snapd/hostfs/etc/os- release to the snap from the host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1795702/+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 1795702] Re: snap-store reports incorrect OS to odrs
This is fixed in the candidate channel now. ** Attachment added: "odrs_os-release.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1795702/+attachment/5238919/+files/odrs_os-release.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1795702 Title: snap-store reports incorrect OS to odrs Status in gnome-software package in Ubuntu: Fix Committed Bug description: Install snap-store - "snap install snap-store" Snap store - "snap run snap-store" Find an application (I opened Wire) Scroll down and click "Write a review" Write a review. Find your review on ODRS https://odrs.gnome.org Note the "Distro" says "Ubuntu Core". This is not correct, as I am on KDE Neon right now. Here is mine. https://odrs.gnome.org/admin/review/9621 In case the content changes I have attached a screenshot. This error is likely because snap-store is a confined snap application. /etc/os-release is allowed in the default template. Note this will be of the core/base snap, not the host. To read the host, you can use the system-observe interface which exposes /var/lib/snapd/hostfs/etc/os- release to the snap from the host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1795702/+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 1816171] Re: Show menubar by default in new terminals has no effect
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1816171 Title: Show menubar by default in new terminals has no effect Status in gnome-terminal package in Ubuntu: Confirmed Bug description: I open a terminal window. No menubar is displayed. From the 'amburger' menu I select Preferences and 'Show menubar by default in new terminals' nothing happens and next time I open a terminal i have no menubar. If i right click on the terminal window and select 'Show menubar' i see the menubar but this option is not remembered next time i open a terminal. corrado@corrado-p6-dd-0215:~$ apt policy gnome-terminal gnome-terminal: Installed: 3.31.90-1ubuntu1 Candidate: 3.31.90-1ubuntu1 Version table: *** 3.31.90-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p6-dd-0215:~$ inxi -SCGx System: Host: corrado-p6-dd-0215 Kernel: 4.19.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco Dingo) CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.2 direct render: Yes corrado@corrado-p6-dd-0215:~$ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 19:39:13 2019 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2019-02-15 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190215) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1816171/+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 1725588] Re: [regression] borders around tabs in preferences are invisible
100% reproducible with Xubuntu 18.04 regardless of theme (over 20 installed). Looking for an upstream report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1725588 Title: [regression] borders around tabs in preferences are invisible Status in thunderbird package in Ubuntu: Confirmed Bug description: Potentially related with [1]. Reproducible in TB 1:52.4.0+build1-0ubuntu2 with default theme for both TB and Ubuntu. Screenshot attached. [1] https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1725588/+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 1738164] Re: [snap] U2F doesn't work with yubikey
This works now with core and chromium on the stable branches. Olivier, I don't see u2f in GNOME Software's Permissions dialog for Chromium. Also, are you intending to ask Security if u2f can be auto-connected for Chromium? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1738164 Title: [snap] U2F doesn't work with yubikey Status in chromium-browser package in Ubuntu: Fix Committed Bug description: (initially reported by Daniel at https://forum.snapcraft.io/t/call- for-testing-chromium-62-0-3202-62/2569/50) « U2F (Universal 2nd Factor) isn’t working when signing into my gmail account trying to use my yubikey. This is a USB device which IIRC chromium needs bidirectional communication with. » This requires investigation, but the yubikey I have is too old and doesn't support U2F. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+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 1725588] Re: [regression] borders around tabs in preferences are invisible
Here is a screenshot of mine - running with Ambiance. DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS" 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "screenshot" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1725588/+attachment/5238910/+files/Screenshot%20from%202019-02-15%2013-47-17.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1725588 Title: [regression] borders around tabs in preferences are invisible Status in thunderbird package in Ubuntu: Confirmed Bug description: Potentially related with [1]. Reproducible in TB 1:52.4.0+build1-0ubuntu2 with default theme for both TB and Ubuntu. Screenshot attached. [1] https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1725588/+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 1792329] Re: Firefox freezes continuously on Ubuntu 16.04
** Changed in: firefox (Ubuntu) Status: Incomplete => New -- 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/1792329 Title: Firefox freezes continuously on Ubuntu 16.04 Status in firefox package in Ubuntu: New Bug description: FireFox 62 freezes continuously. (64 bit Ubuntu 16.04.5) Lock mouse and keyboard on Ubuntu, I have to switch off with the On / Off button. Minor defect, but appeared simultaneously, I open a second / third page, do not load, I go back to the previous one and is no longer loaded, you only see the wheel of time. In this case, restart Firefox. glxinfo | grep "OpenGL version" OpenGL version string: 3.0 Mesa 18.0.5 WM_CLASS(STRING) = "Navigator", "Firefox" Description: Ubuntu 16.04.5 LTS Release: 16.04 Intel® Celeron(R) CPU N2840 @ 2.16GHz × 2 Intel® Bay Trail --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stefano1933 F...m pulseaudio /dev/snd/controlC0: stefano1933 F pulseaudio BuildID: 20181023214907 Channel: Unavailable CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-12 (59 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.3 metric 600 Locales: extensions.sqlite corrupt or missing Package: firefox 63.0+build2-0ubuntu0.16.04.2 PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Profiles: Profile0 (Default) - LastVersion=63.0/20181023214907 (In use) RunningIncompatibleAddons: False Tags: xenial Themes: extensions.sqlite corrupt or missing Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1792329/+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 1816171] [NEW] Show menubar by default in new terminals has no effect
Public bug reported: I open a terminal window. No menubar is displayed. >From the 'amburger' menu I select Preferences and 'Show menubar by default in >new terminals' nothing happens and next time I open a terminal i have no >menubar. If i right click on the terminal window and select 'Show menubar' i see the menubar but this option is not remembered next time i open a terminal. corrado@corrado-p6-dd-0215:~$ apt policy gnome-terminal gnome-terminal: Installed: 3.31.90-1ubuntu1 Candidate: 3.31.90-1ubuntu1 Version table: *** 3.31.90-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p6-dd-0215:~$ inxi -SCGx System: Host: corrado-p6-dd-0215 Kernel: 4.19.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco Dingo) CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.2 direct render: Yes corrado@corrado-p6-dd-0215:~$ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 19:39:13 2019 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2019-02-15 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190215) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco terminal ** Attachment added: "Screenshot from 2019-02-15 19-38-37.png" https://bugs.launchpad.net/bugs/1816171/+attachment/5238911/+files/Screenshot%20from%202019-02-15%2019-38-37.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1816171 Title: Show menubar by default in new terminals has no effect Status in gnome-terminal package in Ubuntu: New Bug description: I open a terminal window. No menubar is displayed. From the 'amburger' menu I select Preferences and 'Show menubar by default in new terminals' nothing happens and next time I open a terminal i have no menubar. If i right click on the terminal window and select 'Show menubar' i see the menubar but this option is not remembered next time i open a terminal. corrado@corrado-p6-dd-0215:~$ apt policy gnome-terminal gnome-terminal: Installed: 3.31.90-1ubuntu1 Candidate: 3.31.90-1ubuntu1 Version table: *** 3.31.90-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p6-dd-0215:~$ inxi -SCGx System: Host: corrado-p6-dd-0215 Kernel: 4.19.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco Dingo) CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.2 direct render: Yes corrado@corrado-p6-dd-0215:~$ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 19:39:13 2019 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2019-02-15 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190215) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1816171/+subscriptions -- Mailing list: https://launchpad.net/
[Desktop-packages] [Bug 1725588] Re: [regression] borders around tabs in preferences are invisible
I tested Thunderbird 60.4 in an Ubuntu 16.04.5 live session with both Ambiance and Radiance and found the tab borders to be very faint but they were there. The border of the selected tab was definitely visible but admittedly not to the extent of when using the Adwaita theme which is what I normally use. Setting back to confirmed for now. ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1725588 Title: [regression] borders around tabs in preferences are invisible Status in thunderbird package in Ubuntu: Confirmed Bug description: Potentially related with [1]. Reproducible in TB 1:52.4.0+build1-0ubuntu2 with default theme for both TB and Ubuntu. Screenshot attached. [1] https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1725588/+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 1815752] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build
Hello. Once agains - I'm sorry for writing post by post, but there is a very interesting comment I found, while checking patches/fixes in Linux v4.4.0-143.169 version (see '1.'). This is excatly the same error, that happened when I updated kernel to the latest '-proposed' release etc. In both cases, it's about "Processing triggers for linux- image-4.4.0-143-generic" and bad return status for 'nvidia' module build. So, maybe the whole problem with building 'nvidia' module is related with "signing: only install a signed kernel (LP: #1764794)" (see '2.')? Thanks, best regards. _ [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764794/comments/6 [2] https://launchpad.net/ubuntu/+source/linux/4.4.0-143.169 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815752 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: I installed new kernel from xenial-proposed and this happened. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.104-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 318706/1281120 files, 2426738/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.4.0-143-generic Date: Wed Feb 13 12:18:21 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.104/build/nv-linux.h:2161:9: error: too many arguments to function ‘get_user_pages’ GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1179 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal PackageVersion: 340.104-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 13 12:57:38 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log
[Desktop-packages] [Bug 1814949] Re: gnome-control-center refuses to open if you try to open the Details panels
The fix is in disco-proposed, https://launchpad.net/ubuntu/+source /gnome-control-center/1:3.31.90-1ubuntu3 ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1814949 Title: gnome-control-center refuses to open if you try to open the Details panels Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: Workaround == Run this command in your terminal: gsettings reset org.gnome.ControlCenter last-panel and then avoid opening the Details panels Issue = If you try to open the Details panel, gnome-control-center will crash. It will then refuse to open. Upstream Bug Report === https://gitlab.gnome.org/GNOME/gnome-control-center/issues/285 See also https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/387 Original Bug Report === Segmentation fault while trying to run via cli , the gnome setting doesn't working when click on setting menu ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 14:38:32 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-05-04 (643 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f783f52232d <__GI___libc_free+29>: mov -0x8(%rdi),%rax PC (0x7f783f52232d) ok source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___libc_free (mem=0x1) at malloc.c:3085 g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: Upgraded to disco on 2018-11-06 (92 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1814949/+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 1721282] Re: upowerd/gnome-power-statistics crash; high CPU, memory consumption
But isn't this a sufficiently severe bug for a LTS release, considering that currenntly supported kernels cause this (so I would say it's a regression) and that when this happens the system battery is drained and the user may even hardly realise why? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1721282 Title: upowerd/gnome-power-statistics crash; high CPU, memory consumption Status in upower package in Ubuntu: Fix Released Bug description: Not sure if necessary here since same bug is already on: https://bugzilla.redhat.com/show_bug.cgi?id=1427621 https://bugs.freedesktop.org/show_bug.cgi?id=100626 https://bugzilla.gnome.org/show_bug.cgi?id=781088 Tested on Ubuntu 16.04.3, 4.12.0-041200rc3-generic Steps to reproduce: 1. have a system with a recent kernel (4.10.x or later) 2. start gnome-power-statistics 3. go to Pprocessor tab 4. have a look at gnome-system-monitor or htop Result: - On Processor section, Wakeups tab: "Processor wakeups pers second: GDBus.Error:org.freedesktop.UPower.GeneralError: cannot enable timerstats." - High CPU usage of /usr/lib/upower/upowerd - Crash gnome-power-statistics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1721282/+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 1815323] Re: After Cheese update does not work
** Changed in: cheese (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1815323 Title: After Cheese update does not work Status in cheese package in Ubuntu: Fix Released Bug description: Hello guys After updating the version of Cheese 3.31.90-1 on Ubuntu Disk 19.04 this week it stopped working and the following error message appears as attached image. obs: The guvcview works normally and opens the webcam, since the cheese has failed. Here's the error message when opening the cheese from the terminal: edson@edson-p6540br:~$ cheese (cheese:13425): Clutter-WARNING **: 01:33:18.872: Whoever translated default:LTR did so wrongly. (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_object_unref: assertion 'object != NULL' failed (cheese:13425): cheese-CRITICAL **: 01:33:19.206: cheese_camera_set_error_element_not_found: assertion 'error == NULL || *error == NULL' failed ** Message: 01:33:19.206: cheese-application.vala:211: Error during camera setup: Um ou mais elementos necessários do GStreamer estão faltando: Um ou mais elementos necessários do GStreamer estão faltando: effects_valve. (cheese:13425): GStreamer-CRITICAL **: 01:33:19.229: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.229: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_object_unref: assertion 'object != NULL' failed *** Olá Pessoal Após atualização da versão do Cheese 3.31.90-1 no Ubuntu Disco 19.04 esta semana o mesmo deixou de funcionar e aparece a seguinte mensagem de erro conforme imagem em anexo. obs: O guvcview funciona normalmente e abre a webcam, já o cheese falhou. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1815323/+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 1816090] Re: Firefox does not play YouTube anymore after some update
Just found out, that you can make Firefox play that video by pressing 'Pause' and afterwards 'Play', when it halts. I think, it looks like a timing issue in Firefox itself. Still it is very confusing for a user and I had the same problem trying to play voice maWhatsapp -- 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/1816090 Title: Firefox does not play YouTube anymore after some update Status in firefox package in Ubuntu: New Bug description: After some update Firefox 65.0 does not play YouTube videos anymore in some virtual machines of Virtualbox 6.04. The following VM were tested and found wrong Xubuntu 18.04.2, Ubuntu Mate 18.04.2 both with Linux 4.18 and Ubuntu 16.04 with Linux 4.15. The same Firefox release does play those video correctly using real hardware with Ubuntu Mate 18.04.2 and Linux 4.15 and in the Virtual machines of Linux Mint 19.1 and Peppermint 9, both with Linux 4.15. Also the Firefox Development 66.0b7 edition has that same problem. Opera, Chrome and Chromium still do play those videos correctly in the Virtual Machines, which do not play with Firefox. On starting the YouTube video, it starts, it buffers to get the normal 2 minutes. But after a approx. 9 frames, it halts displaying the video. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 65.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bertadmin 1776 F pulseaudio /dev/snd/pcmC0D0p: bertadmin 1776 F...m pulseaudio /dev/snd/timer: bertadmin 1776 f pulseaudio BuildID: 20190128144255 Channel: Unavailable CurrentDesktop: MATE Date: Fri Feb 15 10:55:10 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev enp0s3 proto dhcp metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 192.168.0.0/24 dev enp0s3 proto kernel scope link src 192.168.0.109 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile0 - LastVersion=66.0/20190211185957 (Out of date) Profile1 (Default) - LastVersion=65.0/20190128144255 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1816090/+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 1815317] Re: Update gnome-online-accounts to 3.31.90
This bug was fixed in the package gnome-online-accounts - 3.31.90-1ubuntu1 --- gnome-online-accounts (3.31.90-1ubuntu1) disco; urgency=medium * Resynchronize on Debian (LP: #1815317), remaining changes: + debian/rules: - Make sure that gnome-online-accounts.pot is refreshed so the strings from 0001-ubuntu-sso-provider.patch are included (LP: #1759251). - Build with --enable-ubuntu-sso + debian/control.*: - Add b-d on libsnapd-glib-dev - depends on python3 and python3-macaroonbakery for the ubuntu sso provider. + debian/gnome-online-accounts.install: install usr/share/goa-1.0/scripts/lpa_helper.py + debian/libgoa-backend-1.0-1.symbols: Add goa_ubuntu_sso_provider_get_type + Ubuntu-specific patches: - debian/patches/0001-ubuntu-sso-provider.patch - debian/patches/0002-livepatch-auth.patch * debian/patches/0001-ubuntu-sso-provider.patch: - Move from binary icons to svg ones. * debian/patches/0001-Add-Ubuntu-Single-Sign-on-icons.patch: - Drop the patch because no longer required. The icons are now included in the above d/p/0001-ubuntu-sso-provider.patch as svg (non binary) images. * debian/patches/0002-livepatch-auth.patch: - Refreshed using gbp pq rebase. * debian/source/include-binaries: - Drop as no longer required. Binary images have been removed from distro patches. gnome-online-accounts (3.31.90-1) experimental; urgency=medium * New upstream development release * debian/libgoa-backend-1.0-1.symbols: Update * Build-Depend on dh-sequence-gir and dh-sequence-gnome * Drop google-Only-request-the-email-filed.patch: Applied in new release -- Andrea Azzarone Wed, 13 Feb 2019 16:25:24 + ** Changed in: gnome-online-accounts (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1815317 Title: Update gnome-online-accounts to 3.31.90 Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: We should update gnome-online-accounts to 3.31.90 (Debian experimental has the update). GNOME has dropped its .png icons and replaced them with 128px .svg's. If we did the same, we could drop our binary patch since an .svg isn't a binary file. GNOME also includes a 16px symbolic .svg but I don't think those are used right now. So although getting the 128px .svg from Canonical Design isn't technically a blocker, I think it would be nice to get it for consistency (and simplifying our patches a bit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1815317/+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 1725779] Re: Gnome network manager cannot find authentication binary
I found this to work with openvpn via the network manager: I don't know if the message is directly telling you this (it doesn't seem to), but it turns out that for some reason the Network Settings doesn't save your password. Look in /etc/NetworkManager/system- connections/ for a file that matches the name you gave your vpn in the settings. In my case it was just called 'client'. Open it as root in an editor. sudo emacs /etc/NetworkManager/system-connections/client Then change this line in the [vpn] section: password-flags=1 to password-flags=0 Then add this section. [vpn-secrets] password="your-password" Where "your-password" is your vpn password. The quotation marks around your password are required. From: https://necromuralist.github.io/posts/openvpn-on-ubuntu-1804/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1725779 Title: Gnome network manager cannot find authentication binary Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-ssh package in Ubuntu: Confirmed Status in network-manager-vpnc package in Ubuntu: Confirmed Bug description: From logs: Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7424] audit: op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" name="Library" pid=2510 uid=1000 result="success" Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7473] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Started the VPN service, PID 6934 Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7518] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Saw the service appear; activating connection Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7698] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Failed to request VPN secrets #3: No agents were available for t his request. Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7708] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: VPN plugin: state changed: stopped (6) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager-pptp-gnome 1.2.4-4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 21 14:07:06 2017 InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-pptp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+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 1815323] Re: After Cheese update does not work
Hi, Sebastian This problem I solved with the CLEAN reinstallation of Ubuntu Disk 19.04 for the second time. Every time we are in an "example" version Ubuntu 18.10 and we move on to a subsequent 19.04 these problems occur most of the time. This is when there is no error in installing the new version. Ubuntu does not offer an updated reconfiguration of the app list of the new Ubuntu distribution, switching from bionic to Disk automatically causing several flaws. Ubuntu does not offer an application diagnostics option on your installation CD to restore the default application pattern in the event of a failure. These two possibilities above would be great (!) Obs. At the moment I ended up using the disk-proposed version and with that everything is working normally, except for VIM. I will return to the normal version when it is next to the official Ubuntu 19.04 release. In the meantime, when possible, I'll be sending in whatever flaws I find. Thanks for listening Edson Santos * Hi, Sebastian Este problema resolvi com a reinstalação LIMPA do Ubuntu Disco 19.04 pela II vez. Toda vez que estamos numa versão "exemplo" Ubuntu 18.10 e passamos para uma subsequente 19.04 ocorrem estes problemas na grande maioria das vezes. Isso quando não ocorre erro na instalação da nova versão. O Ubuntu não oferece uma reconfiguração atualizada da lista app da distribuição nova do Ubuntu, mudando de bionic para Disco automaticamente ocasionando diversas falhas. O Ubuntu não oferece em seu CD de instalação uma opção de diagnostico dos aplicativos para restabelecer o padrão dos aplicativos originais em caso de falhas. Estas duas possibilidades acima seriam ótimas (!) Obs. No momento acabei utilizando a versão disco-proposed e com isso tudo está funcionando normalmente, com exceção do VIM. Voltarei a versão normal quando estiver próximo do lançamento Oficial do Ubuntu 19.04. Enquanto isso, quando possível estarei enviando as falhas que encontrar. Obrigado pela atenção Edson Santos -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1815323 Title: After Cheese update does not work Status in cheese package in Ubuntu: Incomplete Bug description: Hello guys After updating the version of Cheese 3.31.90-1 on Ubuntu Disk 19.04 this week it stopped working and the following error message appears as attached image. obs: The guvcview works normally and opens the webcam, since the cheese has failed. Here's the error message when opening the cheese from the terminal: edson@edson-p6540br:~$ cheese (cheese:13425): Clutter-WARNING **: 01:33:18.872: Whoever translated default:LTR did so wrongly. (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_object_unref: assertion 'object != NULL' failed (cheese:13425): cheese-CRITICAL **: 01:33:19.206: cheese_camera_set_error_element_not_found: assertion 'error == NULL || *error == NULL' failed ** Message: 01:33:19.206: cheese-application.vala:211: Error during camera setup: Um ou mais elementos necessários do GStreamer estão faltando: Um ou mais elementos necessários do GStreamer estão faltando: effects_valve. (cheese:13425): GStreamer-CRITICAL **: 01:33:19.229: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.229: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_object_unref: assertion 'object != NULL' failed *** Olá Pessoal Após atualização da versão do Cheese
[Desktop-packages] [Bug 1816090] [NEW] Firefox does not play YouTube anymore after some update
Public bug reported: After some update Firefox 65.0 does not play YouTube videos anymore in some virtual machines of Virtualbox 6.04. The following VM were tested and found wrong Xubuntu 18.04.2, Ubuntu Mate 18.04.2 both with Linux 4.18 and Ubuntu 16.04 with Linux 4.15. The same Firefox release does play those video correctly using real hardware with Ubuntu Mate 18.04.2 and Linux 4.15 and in the Virtual machines of Linux Mint 19.1 and Peppermint 9, both with Linux 4.15. Also the Firefox Development 66.0b7 edition has that same problem. Opera, Chrome and Chromium still do play those videos correctly in the Virtual Machines, which do not play with Firefox. On starting the YouTube video, it starts, it buffers to get the normal 2 minutes. But after a approx. 9 frames, it halts displaying the video. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 65.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bertadmin 1776 F pulseaudio /dev/snd/pcmC0D0p: bertadmin 1776 F...m pulseaudio /dev/snd/timer: bertadmin 1776 f pulseaudio BuildID: 20190128144255 Channel: Unavailable CurrentDesktop: MATE Date: Fri Feb 15 10:55:10 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev enp0s3 proto dhcp metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 192.168.0.0/24 dev enp0s3 proto kernel scope link src 192.168.0.109 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile0 - LastVersion=66.0/20190211185957 (Out of date) Profile1 (Default) - LastVersion=65.0/20190128144255 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1816090 Title: Firefox does not play YouTube anymore after some update Status in firefox package in Ubuntu: New Bug description: After some update Firefox 65.0 does not play YouTube videos anymore in some virtual machines of Virtualbox 6.04. The following VM were tested and found wrong Xubuntu 18.04.2, Ubuntu Mate 18.04.2 both with Linux 4.18 and Ubuntu 16.04 with Linux 4.15. The same Firefox release does play those video correctly using real hardware with Ubuntu Mate 18.04.2 and Linux 4.15 and in the Virtual machines of Linux Mint 19.1 and Peppermint 9, both with Linux 4.15. Also the Firefox Development 66.0b7 edition has that same problem. Opera, Chrome and Chromium still do play those videos correctly in the Virtual Machines, which do not play with Firefox. On starting the YouTube video, it starts, it buffers to get the normal 2 minutes. But after a approx. 9 frames, it halts displaying the video. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 65.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bertadmin 1776 F pulseaudio /dev/snd/pcmC0D0p:
[Desktop-packages] [Bug 1721282] Re: upowerd/gnome-power-statistics crash; high CPU, memory consumption
That was fixed with that commit https://gitlab.freedesktop.org/upower/upower/commit/798588a4 The power statistic is not a main feature and Xenial is not the current LTS, that's rather low priority for a SRU in that serie ** Package changed: gnome-power-manager (Ubuntu) => upower (Ubuntu) ** Changed in: upower (Ubuntu) Importance: Undecided => High ** Changed in: upower (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1721282 Title: upowerd/gnome-power-statistics crash; high CPU, memory consumption Status in upower package in Ubuntu: Fix Released Bug description: Not sure if necessary here since same bug is already on: https://bugzilla.redhat.com/show_bug.cgi?id=1427621 https://bugs.freedesktop.org/show_bug.cgi?id=100626 https://bugzilla.gnome.org/show_bug.cgi?id=781088 Tested on Ubuntu 16.04.3, 4.12.0-041200rc3-generic Steps to reproduce: 1. have a system with a recent kernel (4.10.x or later) 2. start gnome-power-statistics 3. go to Pprocessor tab 4. have a look at gnome-system-monitor or htop Result: - On Processor section, Wakeups tab: "Processor wakeups pers second: GDBus.Error:org.freedesktop.UPower.GeneralError: cannot enable timerstats." - High CPU usage of /usr/lib/upower/upowerd - Crash gnome-power-statistics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1721282/+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 1651041] Re: Bad version in Recommends
Sorry but that looks like a disk corruption problem and not a bug in the package ** Changed in: upower (Ubuntu) Importance: Undecided => Low ** Changed in: upower (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1651041 Title: Bad version in Recommends Status in upower package in Ubuntu: Invalid Bug description: not really sure what to say am a novice ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-httplib2 0.9.1+dfsg-1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Sun Dec 18 23:25:18 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-12-14 (4 days ago) InstallationMedia: PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: python-httplib2 Title: package python-httplib2 0.9.1+dfsg-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1651041/+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 1784969] Re: upowerd segfaults over and over again.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: upower (Ubuntu) Importance: Undecided => High ** Changed in: upower (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1784969 Title: upowerd segfaults over and over again. Status in upower package in Ubuntu: Incomplete Bug description: [392516.984355] upowerd[29614]: segfault at 8 ip 55e142176d50 sp 7ffe615a51e0 error 4 in upowerd[55e142156000+39000] [392542.249963] upowerd[29775]: segfault at 8 ip 55a107c1bd50 sp 7ffd1d444f80 error 4 in upowerd[55a107bfb000+39000] [392567.755465] upowerd[29946]: segfault at 8 ip 561edaf8cd50 sp 7ffe03101330 error 4 in upowerd[561edaf6c000+39000] [392592.998110] upowerd[30107]: segfault at 8 ip 558da7db8d50 sp 7fffbcfece90 error 4 in upowerd[558da7d98000+39000] [392618.233396] upowerd[30291]: segfault at 8 ip 5652ae549d50 sp 7ffdddb529b0 error 4 in upowerd[5652ae529000+39000] [392643.491371] upowerd[30732]: segfault at 8 ip 559c184dcd50 sp 7fffac9cd460 error 4 in upowerd[559c184bc000+39000] [392668.986076] upowerd[30945]: segfault at 8 ip 5569d2f0ad50 sp 7ffc0b9c03d0 error 4 in upowerd[5569d2eea000+39000] [392694.258076] upowerd[31245]: segfault at 8 ip 561c77151d50 sp 7fff74956fa0 error 4 in upowerd[561c77131000+39000] [392719.508055] upowerd[31409]: segfault at 8 ip 55d251c39d50 sp 7ffe514025c0 error 4 in upowerd[55d251c19000+39000] [392744.757247] upowerd[31569]: segfault at 8 ip 55fadf695d50 sp 7ffe581d4d10 error 4 in upowerd[55fadf675000+39000] [392770.004408] upowerd[31739]: segfault at 8 ip 55dce3cc1d50 sp 7ffe812efda0 error 4 in upowerd[55dce3ca1000+39000] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2 ProcVersionSignature: Ubuntu 4.15.0-26.28-lowlatency 4.15.18 Uname: Linux 4.15.0-26-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: MATE Date: Wed Aug 1 01:55:16 2018 SourcePackage: upower UpgradeStatus: Upgraded to bionic on 2018-07-04 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1784969/+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 1729579] Re: package gir1.2-upowerglib-1.0 0.99.4-2ubuntu0.3 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de inte
** Changed in: upower (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1729579 Title: package gir1.2-upowerglib-1.0 0.99.4-2ubuntu0.3 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. Status in upower package in Ubuntu: Invalid Bug description: Makes the computer run very slowly (sorry, newbie here). ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gir1.2-upowerglib-1.0 0.99.4-2ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Thu Nov 2 12:23:45 2017 DpkgTerminalLog: dpkg: error al procesar el paquete gir1.2-upowerglib-1.0 (--remove): el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. ErrorMessage: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. InstallationDate: Installed on 2016-12-28 (309 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: upower Title: package gir1.2-upowerglib-1.0 0.99.4-2ubuntu0.3 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1729579/+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 1725779] Re: Gnome network manager cannot find authentication binary
> sudo dpkg-reconfigure network-manager-pptp-gnome > on my 18.04 instance with no success. > running openvpn directly off the command line however does work. pptp and openvpn are different things. Those having the issue, what Ubuntu version/desktop environment/connection type|plugin are you using? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1725779 Title: Gnome network manager cannot find authentication binary Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-ssh package in Ubuntu: Confirmed Status in network-manager-vpnc package in Ubuntu: Confirmed Bug description: From logs: Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7424] audit: op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" name="Library" pid=2510 uid=1000 result="success" Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7473] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Started the VPN service, PID 6934 Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7518] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Saw the service appear; activating connection Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7698] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Failed to request VPN secrets #3: No agents were available for t his request. Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7708] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: VPN plugin: state changed: stopped (6) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager-pptp-gnome 1.2.4-4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 21 14:07:06 2017 InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-pptp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+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 1814949] Re: gnome-control-center refuses to open if you try to open the Details panels
Same bug for me. (Disco) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1814949 Title: gnome-control-center refuses to open if you try to open the Details panels Status in gnome-control-center package in Ubuntu: Triaged Bug description: Workaround == Run this command in your terminal: gsettings reset org.gnome.ControlCenter last-panel and then avoid opening the Details panels Issue = If you try to open the Details panel, gnome-control-center will crash. It will then refuse to open. Upstream Bug Report === https://gitlab.gnome.org/GNOME/gnome-control-center/issues/285 See also https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/387 Original Bug Report === Segmentation fault while trying to run via cli , the gnome setting doesn't working when click on setting menu ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 14:38:32 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-05-04 (643 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f783f52232d <__GI___libc_free+29>: mov -0x8(%rdi),%rax PC (0x7f783f52232d) ok source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___libc_free (mem=0x1) at malloc.c:3085 g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: Upgraded to disco on 2018-11-06 (92 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1814949/+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 1815742] Re: latest network-manager segfaults in disco
Upstream fixed it now in
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/5923a30c
** Changed in: network-manager (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Fix Committed
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1584875] Re: /usr/bin/cheese:5:cheese_application_real_startup:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit:g_application_register
There has been no report after 16.10, closing ** Changed in: cheese (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1584875 Title: /usr/bin/cheese:5:cheese_application_real_startup:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit:g_application_register Status in cheese package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding cheese. This problem was most recently seen with version 3.18.1-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/26eae44eb6f93dfa68761c446f431c1280e7c594 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1584875/+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 1601973] Re: /usr/bin/cheese:11:v4l2_ioctl:gst_v4l2_allocator_qbuf:gst_v4l2_buffer_pool_qbuf:gst_v4l2_buffer_pool_release_buffer:gst_buffer_pool_release_buffer
There has been no report since 17.10, closing ** Changed in: cheese (Ubuntu) Importance: Undecided => Low ** Changed in: cheese (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1601973 Title: /usr/bin/cheese:11:v4l2_ioctl:gst_v4l2_allocator_qbuf:gst_v4l2_buffer_pool_qbuf:gst_v4l2_buffer_pool_release_buffer:gst_buffer_pool_release_buffer Status in cheese package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding cheese. This problem was most recently seen with version 3.20.2-0ubuntu1~ubuntu16.04.1, the problem page at https://errors.ubuntu.com/problem/1b19fddd965379826cf6c921bf1833d052573f84 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1601973/+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 1604194] Re: /usr/bin/cheese:11:gtk_application_impl_inhibit:gtk_application_inhibit:cheese_application_on_camera_state_flags_changed:_cheese_application_on_camera_state_flags_
There has been no report of versions newer than 3.18, closing ** Changed in: cheese (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1604194 Title: /usr/bin/cheese:11:gtk_application_impl_inhibit:gtk_application_inhibit:cheese_application_on_camera_state_flags_changed:_cheese_application_on_camera_state_flags_changed_cheese_camera_state_flags_changed:g_cclosure_marshal_VOID__ENUMv Status in cheese package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding cheese. This problem was most recently seen with version 3.18.1-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c407f9770419fc13a122afa21272b3992f3a9c48 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1604194/+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 1723426] Re: cheese crashed with SIGSEGV in wl_proxy_add_listener()
that's a wayland issue not a cheese one ** Changed in: cheese (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1723426 Title: cheese crashed with SIGSEGV in wl_proxy_add_listener() Status in cheese package in Ubuntu: Invalid Bug description: Started cheese on fresh 17.10 beta install, it crashed. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cheese 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 13 16:24:43 2017 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2017-10-11 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: EXOPC EXOPG06411 ProcCmdline: cheese RelatedPackageVersions: cheese3.26.0-0ubuntu1 cheese-common 3.26.0-0ubuntu1 SegvAnalysis: Segfault happened at: 0x7f73668c777c : testb $0x4,0x28(%rdi) PC (0x7f73668c777c) ok source "$0x4" ok destination "0x28(%rdi)" (0x0028) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: linux StacktraceTop: wl_proxy_add_listener () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 cogl_onscreen_swap_buffers_with_damage () from /usr/lib/x86_64-linux-gnu/libcogl.so.20 Title: cheese crashed with SIGSEGV in wl_proxy_add_listener() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Lucid-CE-133 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EXOPG06411 dmi.board.vendor: EXOPC dmi.board.version: R2.0/R1.1 dmi.chassis.type: 1 dmi.chassis.vendor: EXOPC dmi.chassis.version: R2.0/R1.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrLucid-CE-133:bd11/22/2010:svnEXOPC:pnEXOPG06411:pvrR2.0/R1.1:rvnEXOPC:rnEXOPG06411:rvrR2.0/R1.1:cvnEXOPC:ct1:cvrR2.0/R1.1: dmi.product.family: Series-11.6 dmi.product.name: EXOPG06411 dmi.product.version: R2.0/R1.1 dmi.sys.vendor: EXOPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1723426/+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 1715121] Re: cheese error message
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: cheese (Ubuntu) Importance: Undecided => Low ** Changed in: cheese (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1715121 Title: cheese error message Status in cheese package in Ubuntu: Incomplete Bug description: "there was an error playing video from webcam" ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-94.117~14.04.1-generic 4.4.83 Uname: Linux 4.4.0-94-generic i686 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Sep 5 13:26:57 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2017-06-27 (69 days ago) InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. 945GCMX-S2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=2370472e-b9a6-4cb1-b26e-385e3d2f83bd ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: 945GCMX-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/24/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GCMX-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCMX-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 945GCMX-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Sep 5 13:24:20 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSEMICCHIP Usb Mouse MOUSE, id 8 inputWebcam C170 KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12309 vendor DEL xserver.version: 2:1.18.3-1ubuntu2.3~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1715121/+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 1750457] Re: /usr/bin/cheese:11:g_value_object_collect_value:g_object_set_valist:g_object_set:cheese_camera_setup:cheese_application_setup_camera
The error tracker has no report since 17.10, closing ** Changed in: cheese (Ubuntu) Importance: Undecided => Low ** Changed in: cheese (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1750457 Title: /usr/bin/cheese:11:g_value_object_collect_value:g_object_set_valist:g_object_set:cheese_camera_setup:cheese_application_setup_camera Status in cheese package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding linux. This problem was most recently seen with package version 3.24.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6a59d211acff6c6b8f62994174d67fcb1a42926e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1750457/+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 1815326] Re: Totem does not work on Ubuntu 19.04
*** This bug is a duplicate of bug 1815323 *** https://bugs.launchpad.net/bugs/1815323 ** This bug has been marked a duplicate of bug 1815323 After Cheese update does not work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1815326 Title: Totem does not work on Ubuntu 19.04 Status in totem package in Ubuntu: New Bug description: Hi guys Totem crashed and informs you that you need to install plugin, but it does not tell you which plugin to install as attached image. If the totem knows that a plugin is missing because it does not tell you which one needs to be installed? The totem stopped working after updating Cheese 3.31.90-1. Cheese also stopped working. follows the error message by opening the totem through the terminal: edson@edson-p6540br:~$ totem (totem:4996): Clutter-WARNING **: 01:11:27.077: Whoever translated default:LTR did so wrongly. (totem:4996): GLib-GObject-CRITICAL **: 01:11:27.181: g_object_set: assertion 'G_IS_OBJECT (object)' failed (totem:4996): GStreamer-CRITICAL **: 01:11:27.181: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (totem:4996): GStreamer-CRITICAL **: 01:11:27.181: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (totem:4996): GStreamer-CRITICAL **: 01:11:27.182: gst_object_unref: assertion 'object != NULL' failed (totem:4996): GStreamer-CRITICAL **: 01:11:27.186: gst_bin_add_many: assertion 'GST_IS_ELEMENT (element_1)' failed (totem:4996): GStreamer-CRITICAL **: 01:11:27.186: gst_element_link_many: assertion 'GST_IS_ELEMENT (element_1)' failed (totem:4996): GStreamer-CRITICAL **: 01:11:27.186: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (totem:4996): GStreamer-CRITICAL **: 01:11:27.186: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (totem:4996): GStreamer-CRITICAL **: 01:11:27.186: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (totem:4996): GStreamer-CRITICAL **: 01:11:27.186: gst_object_unref: assertion 'object != NULL' failed GnomeDesktop-Message: 01:11:28.581: got a preview thumbnail (totem:4996): GLib-GObject-CRITICAL **: 01:11:28.581: g_object_ref: assertion 'G_IS_OBJECT (object)' failed ** (totem:4996): WARNING **: 01:17:05.422: can't find typefind element, decodebin will not work (totem:4996): Totem-WARNING **: 01:17:09.284: Failed to reset the playback rate to 1.0 See attached image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1815326/+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 1721282] Re: upowerd/gnome-power-statistics crash; high CPU, memory consumption
I'm experiencing high CPU usage by upowerd in Linux Mint 18.3 KDE (based on Ubuntu 16.04) with 4.15 kernel. I'm not using gnome-power-statistics, but I see the error message about missing /proc/timer_stats in my syslog. I think it's bug https://bugs.freedesktop.org/show_bug.cgi?id=100626 Why the fix hasn't been applied to Xenial? ** Bug watch added: freedesktop.org Bugzilla #100626 https://bugs.freedesktop.org/show_bug.cgi?id=100626 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1721282 Title: upowerd/gnome-power-statistics crash; high CPU, memory consumption Status in gnome-power-manager package in Ubuntu: Confirmed Bug description: Not sure if necessary here since same bug is already on: https://bugzilla.redhat.com/show_bug.cgi?id=1427621 https://bugs.freedesktop.org/show_bug.cgi?id=100626 https://bugzilla.gnome.org/show_bug.cgi?id=781088 Tested on Ubuntu 16.04.3, 4.12.0-041200rc3-generic Steps to reproduce: 1. have a system with a recent kernel (4.10.x or later) 2. start gnome-power-statistics 3. go to Pprocessor tab 4. have a look at gnome-system-monitor or htop Result: - On Processor section, Wakeups tab: "Processor wakeups pers second: GDBus.Error:org.freedesktop.UPower.GeneralError: cannot enable timerstats." - High CPU usage of /usr/lib/upower/upowerd - Crash gnome-power-statistics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1721282/+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 1805068] Re: [SIT][Ubuntu][GLK]The image hangs intermittently during recording a video via Cheese.
Thank you for your bug report, could you send that upstream as well on https://gitlab.gnome.org/GNOME/cheese/issues ? What do you mean by 'Can not duplicate the issue when play the video after finishing recording.'? That the recording is fine/not having the issue you saw on screen? ** Changed in: cheese (Ubuntu) Importance: Undecided => Low ** Changed in: cheese (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1805068 Title: [SIT][Ubuntu][GLK]The image hangs intermittently during recording a video via Cheese. Status in cheese package in Ubuntu: Incomplete Bug description: The image hangs intermittently during recording a video via Cheese. OS: Ubuntu 18.04.1 LTS Fail Rate: 2/2 units Fail Frequency: 10 out of 10 times(each sku test 5 times) Note: 1.Can not duplicate the issue when play the video after finishing recording. 2.Also can duplicate the issue when I click video item and then idle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1805068/+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 1815323] Re: After Cheese update does not work
Thank you for your bug report. That seems an issue with your gstreamer installation, what's the output of those commands? - dpkg -l | grep gstreamer - gst-inspect-1.0 valve ** Changed in: cheese (Ubuntu) Importance: Undecided => Low ** Changed in: cheese (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1815323 Title: After Cheese update does not work Status in cheese package in Ubuntu: Incomplete Bug description: Hello guys After updating the version of Cheese 3.31.90-1 on Ubuntu Disk 19.04 this week it stopped working and the following error message appears as attached image. obs: The guvcview works normally and opens the webcam, since the cheese has failed. Here's the error message when opening the cheese from the terminal: edson@edson-p6540br:~$ cheese (cheese:13425): Clutter-WARNING **: 01:33:18.872: Whoever translated default:LTR did so wrongly. (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_object_unref: assertion 'object != NULL' failed (cheese:13425): cheese-CRITICAL **: 01:33:19.206: cheese_camera_set_error_element_not_found: assertion 'error == NULL || *error == NULL' failed ** Message: 01:33:19.206: cheese-application.vala:211: Error during camera setup: Um ou mais elementos necessários do GStreamer estão faltando: Um ou mais elementos necessários do GStreamer estão faltando: effects_valve. (cheese:13425): GStreamer-CRITICAL **: 01:33:19.229: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.229: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_object_unref: assertion 'object != NULL' failed *** Olá Pessoal Após atualização da versão do Cheese 3.31.90-1 no Ubuntu Disco 19.04 esta semana o mesmo deixou de funcionar e aparece a seguinte mensagem de erro conforme imagem em anexo. obs: O guvcview funciona normalmente e abre a webcam, já o cheese falhou. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1815323/+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 1725779] Re: Gnome network manager cannot find authentication binary
I tried sudo dpkg-reconfigure network-manager-pptp-gnome on my 18.04 instance with no success. running openvpn directly off the command line however does work. I am thinking there is some issue with the network manager implementation, perhaps not directly but it certainly exhibits the error when used. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1725779 Title: Gnome network manager cannot find authentication binary Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-ssh package in Ubuntu: Confirmed Status in network-manager-vpnc package in Ubuntu: Confirmed Bug description: From logs: Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7424] audit: op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" name="Library" pid=2510 uid=1000 result="success" Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7473] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Started the VPN service, PID 6934 Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7518] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Saw the service appear; activating connection Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7698] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Failed to request VPN secrets #3: No agents were available for t his request. Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7708] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: VPN plugin: state changed: stopped (6) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager-pptp-gnome 1.2.4-4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 21 14:07:06 2017 InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-pptp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
> The new stable version indicate the fix mentioned by seb128 is there but no > indication has been made in > the debian/changelog to automatically change the status, which breaks the SRU > machinery for this > particular bug. @Eric, I didn't handle it ine SRU because I don't understand the issue enough to be confident it's fixed in that update, I was just adding a side comment because the change looks like it could impact on the behaviour described there. Did you confirm the SRU does address the problem and that it's indeed fix commited? (and that it's really resolved in newer series) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Committed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1816043] [NEW] libreoffice snap package not displaying all unicode emojis
Public bug reported: libreoffice 6.2 snap package is not displaying all unicode emojis, while the *.deb download from libreoffice.org is displaying them all. tested in calc & writer. Talking about these particular emojis: ⏳ ⚠ See attachment for comparison between current snap and deb package. Using Ubuntu 18.04. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: snap ** Attachment added: "lo dev vs snap.png" https://bugs.launchpad.net/bugs/1816043/+attachment/5238874/+files/lo%20dev%20vs%20snap.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1816043 Title: libreoffice snap package not displaying all unicode emojis Status in libreoffice package in Ubuntu: New Bug description: libreoffice 6.2 snap package is not displaying all unicode emojis, while the *.deb download from libreoffice.org is displaying them all. tested in calc & writer. Talking about these particular emojis: ⏳ ⚠ See attachment for comparison between current snap and deb package. Using Ubuntu 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1816043/+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 1816004] Re: GLVND: AARCH64 : Fix address passed to clear cache
** Changed in: libglvnd (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1816004
Title:
GLVND: AARCH64 : Fix address passed to clear cache
Status in libglvnd package in Ubuntu:
New
Bug description:
[Impact]
A new fix has been merged to NVIDIA libglvnd repo at
https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e
We need to include it in bionic.
It would be ok to just include this fix even without updating to the latest
glvnd version.
This change fixes a crash seen in some GLX apps while calling
glXGetProcAddress.
Source Package :
https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2
Can we get this fix merged in current LTS 18.04 as "-updates"
[Test app]
To reproduce this failure: Install python-pyglet on 18.04 ubuntu.
And run a small test app with this piece of code.
void *handle = dlopen("libGLX.so.0", 2);
glXGetProcAddressARB = (GLXextFuncPtr (*)(const GLubyte*))dlsym(handle,
"glXGetProcAddressARB");
glXGetProcAddressARB("glXAllocateMemoryMESA");
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1816004/+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 1816032] Re: gtk_widget_destroy reports error
Thank you for your bug report, but how is that a bug in the network indicator? Also you didn't attach the example you mentioned? ** Changed in: network-manager-applet (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager-applet (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error Status in network-manager-applet package in Ubuntu: Incomplete Bug description: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1816032/+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 1816032] [NEW] gtk_widget_destroy reports error
Public bug reported: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: destroy gtk widget -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error Status in network-manager-applet package in Ubuntu: New Bug description: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1816032/+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 1778069] Re: [xfce] nautilus don't open files if set as default file manager
I assume that adding the exo package to the Affects list should do. The upstream report has already been linked. ** Also affects: exo (Ubuntu) Importance: Undecided Status: New ** Changed in: exo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778069 Title: [xfce] nautilus don't open files if set as default file manager Status in exo: Confirmed Status in exo package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in xubuntu-default-settings package in Ubuntu: Fix Released Status in nautilus package in Debian: New Bug description: If Nautilus is set as the preferred file manager with exo-preferred- applications, it no longer opens files. It opens only directories, .desktop files and executable files. Trying to open a file, be using Enter or with double mouse click, as a text file or a video makes Nautilus window blink for a instant and nothing happens. To be able to open the files, it's needed to choose to open with another application and then choose the application. Once Nautilus is unset as the default file manager (Thunar is chosen, for example), it starts to work fine again, opening files properly. Nautilus' Debian Sid version do not have this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 Uname: Linux 4.17.2-041702-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jun 21 10:55:41 2018 InstallationDate: Installed on 2017-06-13 (372 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/exo/+bug/1778069/+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 1816027] Re: Aborted Scanning in SimpleScan and later xubuntu freeses
** Package changed: xfce4-terminal (Ubuntu) => simple-scan (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1816027 Title: Aborted Scanning in SimpleScan and later xubuntu freeses Status in simple-scan package in Ubuntu: New Bug description: I don't have much information. - My xubuntu system 18.04 freeses and the last thing I did was aborting scanning while scanning was started some seconds ago. Some time later I could not use SimpleScan anymore and soon it was getting worse. - The top panel containing my started applications doesn't respond, clicking doesn't help - Will have to hard reset my system. TODO: Type Alt + F2 and type ubuntu-bug nameofprogram. ... After running one of the above commands, Ubuntu will gather information about the bug. ... A new web browser tab will open to continue processing the bug data. ... After logging in to Launchpad, enter a description of the problem in the summary field. Result: Alt-F2 and selected SimpleScan in drop down Nothing happened, no new browser tab with info generated Then I did : ubuntu-bug -x ===> Don't see extra info Got message : Extra debug information will be added to the bug report automatically. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xfce4-terminal 0.8.7.4-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Feb 15 11:37:20 2019 ExecutablePath: /usr/bin/xfce4-terminal InstallationDate: Installed on 2018-04-15 (305 days ago) InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xfce4-terminal UpgradeStatus: Upgraded to bionic on 2018-08-02 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1816027/+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 1816027] [NEW] Aborted Scanning in SimpleScan and later xubuntu freeses
You have been subscribed to a public bug: I don't have much information. - My xubuntu system 18.04 freeses and the last thing I did was aborting scanning while scanning was started some seconds ago. Some time later I could not use SimpleScan anymore and soon it was getting worse. - The top panel containing my started applications doesn't respond, clicking doesn't help - Will have to hard reset my system. TODO: Type Alt + F2 and type ubuntu-bug nameofprogram. ... After running one of the above commands, Ubuntu will gather information about the bug. ... A new web browser tab will open to continue processing the bug data. ... After logging in to Launchpad, enter a description of the problem in the summary field. Result: Alt-F2 and selected SimpleScan in drop down Nothing happened, no new browser tab with info generated Then I did : ubuntu-bug -x ===> Don't see extra info Got message : Extra debug information will be added to the bug report automatically. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xfce4-terminal 0.8.7.4-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Feb 15 11:37:20 2019 ExecutablePath: /usr/bin/xfce4-terminal InstallationDate: Installed on 2018-04-15 (305 days ago) InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xfce4-terminal UpgradeStatus: Upgraded to bionic on 2018-08-02 (196 days ago) ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- Aborted Scanning in SimpleScan and later xubuntu freeses https://bugs.launchpad.net/bugs/1816027 You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. -- 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 1796979]
Michal, I'm assigning this to you just to get it off the triage list, leaving UNCONFIRMED. Feel free to revert or anything you seem more fit for this bug. Thanks. -- 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/1796979 Title: Intermittently can't connect to the server Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Intermittently while browsing old and new sites, I run into a Server Not Found, "Hmm. We’re having trouble finding that site.", "We can’t connect to the server" page. To workaround I will often hold down the enter key to rapidly re-attempt to get to the page or close the tab, try again, and repeat until I get through. The latter is successful much more often than the former. Running in a new Firefox profile and in safe mode seems to make no difference. I had mistakenly made a submission to launchpad without running ubuntu-bug firefox. This is the submission using ubuntu-bug. The old submission is here: https://bugs.launchpad.net/bugs/1792402 Linux Mint 18.3 Cinnamon apt-cache policy firefox firefox: Installed: 63.0~b13+build1-0ubuntu0.16.04.1 ProblemType: Bug DistroRelease: Linux 18.3 Package: firefox 63.0~b13+build1-0ubuntu0.16.04.1 [modified: usr/lib/firefox/browser/defaults/preferences/vendor-firefox.js usr/lib/firefox/distribution/distribution.ini] [origin: LP-PPA-mozillateam-firefox-next] ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rex3357 F pulseaudio BuildID: 20181009094547 Channel: beta CurrentDesktop: X-Cinnamon Date: Tue Oct 9 15:54:39 2018 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePlugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-12 (635 days ago) InstallationMedia: Linux Mint 17.2 "Rafaela" - Release amd64 20150627 IpRoute: default via 192.168.103.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.103.0/24 dev wlan0 proto kernel scope link src 192.168.103.222 metric 600 MostRecentCrashID: bp-392336ee-2be7-4d6e-89e0-e40350180301 Profile0BrokenPermissions: browser-extension-data/ublo...@raymondhill.net/storage.js.corrupt (0o600, wrong owner) extension-settings.json.corrupt (0o600, wrong owner) saved-telemetry-pings/ba50588c-e150-45ec-9d22-916c98101815 (0o600, wrong owner) saved-telemetry-pings/f50808ab-da4a-421b-8acd-2795287134d8 (0o600, wrong owner) Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) Profile0PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile0 - LastVersion=62.0/20180911150120 (Out of date) Profile1 (Default) - LastVersion=63.0/20181009094547 (In use) RelatedPackageVersions: adobe-flashplugin 1:20181009.1-0ubuntu0.16.04.1 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-392336ee-2be7-4d6e-89e0-e40350180301 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 165A dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058D11244620001620100:rvnHewlett-Packard:rn165A:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dv7 Notebook PC
[Desktop-packages] [Bug 1810574] Re: Audio is low pitched/deeper on AMD GPU
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1810574 Title: Audio is low pitched/deeper on AMD GPU Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a dual screen set up, a Display Port Monitor and a HDMI monitor on Ubuntu 18.04.1 ALSA driver k4.15.0-43-generic. The display port monitor has speakers so I used as my main speakers, but, the audio of any source sounds deeper/slower than it should be. Even videos of any source last longer. For example, 10 "seconds" of any video in my computer are 12.5 seconds in my phone stopwatch. I'm using a radeon r9 280x. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diego 1586 F pulseaudio /dev/snd/pcmC1D3p: diego 1586 F...m pulseaudio /dev/snd/controlC1: diego 1586 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 4 21:31:30 2019 InstallationDate: Installed on 2019-01-03 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Tahiti HDMI Audio [Radeon HD 7870 XT / 7950/7970] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd02/04/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1810574/+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 1810574] Re: Audio is low pitched/deeper on AMD GPU
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1810574 Title: Audio is low pitched/deeper on AMD GPU Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a dual screen set up, a Display Port Monitor and a HDMI monitor on Ubuntu 18.04.1 ALSA driver k4.15.0-43-generic. The display port monitor has speakers so I used as my main speakers, but, the audio of any source sounds deeper/slower than it should be. Even videos of any source last longer. For example, 10 "seconds" of any video in my computer are 12.5 seconds in my phone stopwatch. I'm using a radeon r9 280x. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diego 1586 F pulseaudio /dev/snd/pcmC1D3p: diego 1586 F...m pulseaudio /dev/snd/controlC1: diego 1586 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 4 21:31:30 2019 InstallationDate: Installed on 2019-01-03 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Tahiti HDMI Audio [Radeon HD 7870 XT / 7950/7970] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd02/04/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1810574/+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 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
** Description changed: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR; I have today logged the memory consumption while I was handling some bills and linked is a log of constantly increasing Xorg memory usage. So it goes until it chokes the machine and only a hard reboot is possible. My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see how the Xorg usage creeps up. https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0 + + I should add that this bug seems specific to Kubuntu, and (I guess) + associated with running under Virtualbox. I have another Ubuntu 18.04 + (i.e. not _K_ubuntu) running on bare metal and it is not having any + problems. Please advise what additional information I should post to have this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Feb 13 01:00:13 2019 DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2015-10-22 (1209 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815693 Title: Kubuntu 18.10 Xorg severe memory leak Status in xorg package in Ubuntu: New Bug description: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than
[Desktop-packages] [Bug 1816021] [NEW] package bubblewrap 0.2.1-1ubuntu0.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su con
Public bug reported: 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bubblewrap 0.2.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Feb 15 10:11:51 2019 DpkgTerminalLog: dpkg: error al procesar el paquete bubblewrap (--configure): El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2019-02-13 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: bubblewrap Title: package bubblewrap 0.2.1-1ubuntu0.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bubblewrap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/1816021 Title: package bubblewrap 0.2.1-1ubuntu0.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. Status in bubblewrap package in Ubuntu: New Bug description: 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bubblewrap 0.2.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Feb 15 10:11:51 2019 DpkgTerminalLog: dpkg: error al procesar el paquete bubblewrap (--configure): El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2019-02-13 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: bubblewrap Title: package bubblewrap 0.2.1-1ubuntu0.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1816021/+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 1771943] Re: nautilus accessing samba shares doesn't use cached credentials
Debug version uploaded to https://launchpad.net/~ubuntu- desktop/+archive/ubuntu/ppa/+build/16391488 you need to download the debs corresponding to the ones you have installed (dpkg -l | grep gvfs) and install them with dpkg -i *.deb then restart your user session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1771943 Title: nautilus accessing samba shares doesn't use cached credentials Status in gvfs package in Ubuntu: Triaged Bug description: I don't know if the bug is in nautilus or other package but accessing samba shares in a samba domain membership authentication using winbind, nautilus doesn't try to use cached credentials to access network shares. Before the upgrade to ubuntu bionic (18.04) all works as expected. I have configured winbind bind module for samba authentication on a samba server and all seems works flawless. I have enabled winbind offline logon (in smb.conf) and cached credentials (in /etc/security/pam_winbind.conf). Offline logon seems to work but when I access samba shares, nautilus ask me for a username and password even if I log on using a valid domain account and this valid account can access the samba share. If you need some more info please ask me Have a great day Piviul ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Fri May 18 08:19:06 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'855x550+65+24'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2012-05-17 (2191 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-05-03 (15 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1771943/+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 1801898] Re: Only one of two external (displayport) displays is working without hotplug
Thanks for the status update, closing then ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1801898 Title: Only one of two external (displayport) displays is working without hotplug Status in xorg-server package in Ubuntu: Fix Released Bug description: After upgrading to Ubuntu 18.10 from Ubuntu 18.04, when logging in one of my two external displays will not be activated without hotplugging the other external display. The display settings app shows the second display as inactive, and when trying to activate it the settings app states that some hardware limitation stops it from being possible to apply the change. The laptop lid is closed, the internal laptop display is not active. Hotplugging the other external display solves the problem - after hotplug both external displays are active. This makes the bug annoying but workaroundable. I am not sure if this bug belongs to the Xorg package or the linux package. Hardware: Thinkpad t430s laptop sitting in a Thinkpad 4338 docking station, with two external displays connected through displayport (via docking station). $ sudo lspci -v 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f000 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 6000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu8 Candidate: 1:7.7+19ubuntu8 Version table: *** 1:7.7+19ubuntu8 500 500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy linux-image-4.18.0-10-generic linux-image-4.18.0-10-generic: Installed: 4.18.0-10.11 Candidate: 4.18.0-10.11 Version table: *** 4.18.0-10.11 500 500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-10-24 10:23:47,912 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroRelease: Ubuntu 18.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: hsize = 2 vsize = 2 GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb] InstallationDate: Installed on 2016-06-06 (883 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 2356FW4 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/vg_avin-lv_root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Tags: cosmic ubuntu Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-24 (14 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356FW4 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: R9TW1K9 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2356FW4:pvrThinkPadT430s:rvnLENOVO:rn2356FW4:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2356FW4 dmi.product.sku: LENOVO_MT_2356 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
[Desktop-packages] [Bug 1769991] Re: [16.04] Unable to import OpenVPN configuration into Network Manager
Thanks, closing for the current serie then. ** Changed in: network-manager-openvpn (Ubuntu) Status: Incomplete => Fix Released ** Also affects: network-manager-openvpn (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1769991 Title: [16.04] Unable to import OpenVPN configuration into Network Manager Status in network-manager-openvpn package in Ubuntu: Fix Released Status in network-manager-openvpn source package in Xenial: New Bug description: In 16.04, it is currently not possible to import OpenVPN configurations. Specifically, imports fail with the error of: The file 'filename.ovpn' could not be read or does not contain recognized VPN connection information. Error: Key file contains line 'client' which is not a key-value pair, group, or comment. -- An example configuration that fails to import is as follows (with some critical components excluded, like a proper remote address, or a proper x509 name); this is a config that otherwise works with a Sophos XG Firewall-based SSL VPN system client dev tun persist-tun persist-key proto tcp verify-x509-name "" route remote_host 255.255.255.255 net_gateway resolv-retry infinite remote 1.2.3.4 8443 tcp ca ca.crt cert client.crt key client.key auth-user-pass cipher AES-256-CBC auth SHA512 comp-lzo no route-delay 4 verb 3 reneg-sec 0 -- This same exact configuration works with a direct call of `openvpn ./filename.ovpn`. Why Network Manager is unable to parse or import the OpenVPN configuration is beyond my ability to comprehend. Note that the same configuration made by hand in the new VPN window works fine, but the import function fails. (Which is a pretty severe bug) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-openvpn 1.1.93-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 8 14:59:54 2018 InstallationDate: Installed on 2016-12-20 (503 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769991/+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 1815694] Re: GLib-CRITICAL and does not start
1) I installed this package: sudo apt install adwaita-icon-theme-full 2) I tried: /snap/bin/inkscape Inkscape started and works!!! version 1.0alpha (ee17174538, 2019-02-13) Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1815694 Title: GLib-CRITICAL and does not start Status in Inkscape: Triaged Status in inkscape package in Ubuntu: Confirmed Bug description: 1) I try: /snap/bin/inkscape 2) but terminal showed me: ** Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Icon 'image-missing' not present in theme Mint-Y (gtk-icon-theme-error-quark, 0) Emergency save activated! (inkscape:6503): GLib-CRITICAL **: 02:12:42.305: g_path_get_dirname: assertion 'file_name != NULL' failed Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. Gtk-Message: 02:12:42.314: GtkDialog mapped without a transient parent. This is discouraged. 3) Application does not start 4) I use: Linux Mint 19, Cinnamon, 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1815694/+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 1794033]
The problematic tests have been disabled in mesa ci since June 2018. If you think this is fixed, than I can re-enable them. Mesa CI updated it's kernels to 4.19 recently, but otherwise there has been no change to affect this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Incomplete Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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 1794033]
Last seen this issue on our CI system is 8 months, 3 weeks / 4968 runs ago. Can we close this issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Incomplete Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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
