[Desktop-packages] [Bug 859060] Re: totem-plugin-viewer crashed with SIGSEGV in g_type_check_instance_is_a()
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- 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/859060 Title: totem-plugin-viewer crashed with SIGSEGV in g_type_check_instance_is_a() Status in gstreamer0.10 package in Ubuntu: Expired Status in totem package in Ubuntu: Expired Bug description: Totem crashed when clicking the small play button to preview a sound file in the itunes store preview thingy... more specifically this address http://itunes.apple.com/us/album/nine-oclock- single/id465976129?ls=1 Description: Ubuntu oneiric (development branch) Release: 11.10 libgstreamer0.10-0: Installed: 0.10.35-1 Candidate: 0.10.35-1 Version table: *** 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-plugins-base: Installed: 0.10.35-1 Candidate: 0.10.35-1 Version table: *** 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-plugins-good: Installed: 0.10.30-1ubuntu7 Candidate: 0.10.30-1ubuntu7 Version table: *** 0.10.30-1ubuntu7 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-alsa: Installed: 0.10.35-1 Candidate: 0.10.35-1 Version table: *** 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-audiosink: Installed: (none) Candidate: (none) Version table: gstreamer0.10-plugins-bad: Installed: 0.10.22-2ubuntu4 Candidate: 0.10.22-2ubuntu4 Version table: *** 0.10.22-2ubuntu4 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-plugins-ugly: Installed: 0.10.18-3ubuntu1 Candidate: 0.10.18-3ubuntu1 Version table: *** 0.10.18-3ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-ffmpeg: Installed: 0.10.12-1ubuntu1 Candidate: 0.10.12-1ubuntu1 Version table: *** 0.10.12-1ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-pulse: Installed: (none) Candidate: (none) Version table: gstreamer0.10-gconf: Installed: 0.10.30-1ubuntu7 Candidate: 0.10.30-1ubuntu7 Version table: *** 0.10.30-1ubuntu7 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-tools: Installed: 0.10.35-1 Candidate: 0.10.35-1 Version table: *** 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-audiosource: Installed: (none) Candidate: (none) Version table: gstreamer0.10-doc: Installed: (none) Candidate: 0.10.35-1 Version table: 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages libgstreamer0.10-dev: Installed: (none) Candidate: 0.10.35-1 Version table: 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages gstreamer0.10-videosink: Installed: (none) Candidate: (none) Version table: gstreamer0.10-videosource: Installed: (none) Candidate: (none) Version table: gstreamer0.10-gnonlin: Installed: (none) Candidate: 0.10.17-2 Version table: 0.10.17-2 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages gstreamer0.10-gnonlin-dbg: Installed: (none) Candidate: 0.10.17-2 Version table: 0.10.17-2 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages gstreamer0.10-gnonlin-doc: Installed: (none) Candidate: 0.10.17-2 Version table: 0.10.17-2 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages gstreamer0.10-nice: Installed: 0.1.0-2ubuntu1 Candidate: 0.1.0-2ubuntu1 Version table: *** 0.1.0-2ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-plugins-base-apps: Installed: 0.10.35-1 Candidate: 0.10.35-1 Version table: *** 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-plugins-base-dbg: Installed: (none) Candidate: 0.10.35-1 Version table: 0.10.35-1 0 500
[Desktop-packages] [Bug 716395] Re: shows a progress bar waiting forever
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- 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/716395 Title: shows a progress bar waiting forever Status in thunderbird package in Ubuntu: Expired Bug description: Binary package hint: thunderbird In Mozilla Thunderbird, in the status bar at the bottom of the window, on the right side, there is a progress bar that usually shows the progress when you are downloading messages, sending a message, etc. When thunderbird is connecting to the server or waiting for something, it shows a "waiting" animation (bar of fixed size moving from left to right cyclically). When no operation is in progress, this bar should stay idle and empty. Since I added an IMAP account, this bar ALWAYS shows a never ending "waiting" animation forever and ever even when the program isn't doing anything. My IMAP account works correctly and downloads messages when there are messages to download. It is only the animation that never stops. I attach a screenshot. Note that on the left part of the status bar there is no message saying "waiting for this"/"doing that", which is correct since thunderbird is not doing anything nor waiting for anything. Before I added the IMAP account, this never happened; the status bar used to work fine and only used to show the animation or progress bar when it was appropriate. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12 Uname: Linux 2.6.32-28-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu Feb 10 13:29:39 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/716395/+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 1307011] Re: totem-plugin-viewer crashed with SIGABRT in __kernel_vsyscall()
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- 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/1307011 Title: totem-plugin-viewer crashed with SIGABRT in __kernel_vsyscall() Status in totem package in Ubuntu: Expired Bug description: no idea ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: totem 3.0.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 CasperVersion: 1.287 CrashCounter: 1 Date: Sat Apr 12 13:34:19 2014 ExecutablePath: /usr/lib/totem/totem-plugin-viewer LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcCmdline: /usr/lib/totem/totem-plugin-viewer --plugin-type cone --user-agent Mozilla/5.0\ (X11;\ Linux\ i686;\ rv:7.0.1)\ Gecko/20100101\ Firefox/7.0.1 --referrer http://www.mp3-meditation-club.com/mp3files/cosmic_ordering_cO24s_320.mp3 --mimetype audio/mpeg ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: totem StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: totem-plugin-viewer crashed with SIGABRT in __kernel_vsyscall() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1307011/+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 953513] Re: totem-video-thumbnailer crashed with SIGSEGV in gst_buffer_is_metadata_writable() .
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- 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/953513 Title: totem-video-thumbnailer crashed with SIGSEGV in gst_buffer_is_metadata_writable() . Status in totem package in Ubuntu: Expired Bug description: The program crashed when trying to mute the sound. Plays the file in flv format. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: totem 3.0.1-0ubuntu19 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 12 23:36:05 2012 ExecutablePath: /usr/bin/totem-video-thumbnailer InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcCmdline: /usr/bin/totem-video-thumbnailer -s 128 file:///home/username/Wideo/Inne/sins/g2.flv /tmp/.gnome_desktop_thumbnail.Z8NIAW ProcEnviron: LANG=pl_PL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f64a71b4d45 : cmpl $0x1,0x8(%rdi) PC (0x7f64a71b4d45) ok source "$0x1" ok destination "0x8(%rdi)" (0x0008) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: gst_buffer_is_metadata_writable () from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0 gst_buffer_make_metadata_writable () from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstbase-0.10.so.0 gst_pad_push () from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstcoreelements.so Title: totem-video-thumbnailer crashed with SIGSEGV in gst_buffer_is_metadata_writable() UpgradeStatus: Upgraded to precise on 2012-03-12 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/953513/+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 859060] Re: totem-plugin-viewer crashed with SIGSEGV in g_type_check_instance_is_a()
[Expired for gstreamer0.10 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gstreamer0.10 (Ubuntu) Status: Incomplete => Expired -- 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/859060 Title: totem-plugin-viewer crashed with SIGSEGV in g_type_check_instance_is_a() Status in gstreamer0.10 package in Ubuntu: Expired Status in totem package in Ubuntu: Expired Bug description: Totem crashed when clicking the small play button to preview a sound file in the itunes store preview thingy... more specifically this address http://itunes.apple.com/us/album/nine-oclock- single/id465976129?ls=1 Description: Ubuntu oneiric (development branch) Release: 11.10 libgstreamer0.10-0: Installed: 0.10.35-1 Candidate: 0.10.35-1 Version table: *** 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-plugins-base: Installed: 0.10.35-1 Candidate: 0.10.35-1 Version table: *** 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-plugins-good: Installed: 0.10.30-1ubuntu7 Candidate: 0.10.30-1ubuntu7 Version table: *** 0.10.30-1ubuntu7 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-alsa: Installed: 0.10.35-1 Candidate: 0.10.35-1 Version table: *** 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-audiosink: Installed: (none) Candidate: (none) Version table: gstreamer0.10-plugins-bad: Installed: 0.10.22-2ubuntu4 Candidate: 0.10.22-2ubuntu4 Version table: *** 0.10.22-2ubuntu4 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-plugins-ugly: Installed: 0.10.18-3ubuntu1 Candidate: 0.10.18-3ubuntu1 Version table: *** 0.10.18-3ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-ffmpeg: Installed: 0.10.12-1ubuntu1 Candidate: 0.10.12-1ubuntu1 Version table: *** 0.10.12-1ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-pulse: Installed: (none) Candidate: (none) Version table: gstreamer0.10-gconf: Installed: 0.10.30-1ubuntu7 Candidate: 0.10.30-1ubuntu7 Version table: *** 0.10.30-1ubuntu7 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-tools: Installed: 0.10.35-1 Candidate: 0.10.35-1 Version table: *** 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-audiosource: Installed: (none) Candidate: (none) Version table: gstreamer0.10-doc: Installed: (none) Candidate: 0.10.35-1 Version table: 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages libgstreamer0.10-dev: Installed: (none) Candidate: 0.10.35-1 Version table: 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages gstreamer0.10-videosink: Installed: (none) Candidate: (none) Version table: gstreamer0.10-videosource: Installed: (none) Candidate: (none) Version table: gstreamer0.10-gnonlin: Installed: (none) Candidate: 0.10.17-2 Version table: 0.10.17-2 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages gstreamer0.10-gnonlin-dbg: Installed: (none) Candidate: 0.10.17-2 Version table: 0.10.17-2 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages gstreamer0.10-gnonlin-doc: Installed: (none) Candidate: 0.10.17-2 Version table: 0.10.17-2 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages gstreamer0.10-nice: Installed: 0.1.0-2ubuntu1 Candidate: 0.1.0-2ubuntu1 Version table: *** 0.1.0-2ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-plugins-base-apps: Installed: 0.10.35-1 Candidate: 0.10.35-1 Version table: *** 0.10.35-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status gstreamer0.10-plugins-base-dbg: Installed: (none) Candidate: 0.10.35-1 Version table: 0.10.35-1 0
[Desktop-packages] [Bug 1027564] Re: when using imap against gmail, drafts are stored multiple times and not removed
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- 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/1027564 Title: when using imap against gmail, drafts are stored multiple times and not removed Status in thunderbird package in Ubuntu: Expired Bug description: When composing mail in thunderbird with (imap, gmail), drafts are correctly stored in [Google Mail]/Drafts. But a single message may be stored multiple times as multiple message drafts instead of multiple times as the same message. And on sending, the draft is often not deleted, resulting in a Drafts folder with quite a lot of garbage in it. Somewhat worse, the garbage incorrectly gives the impression that the original mails were not sent. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: thunderbird 13.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeff 2476 F pulseaudio BuildID: 20120615181619 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 22' Mixer name : 'Realtek ALC882' Components : 'HDA:10ec0882,10eca201,00100101' Controls : 45 Simple ctrls : 21 Channel: release Date: Sun Jul 22 09:01:33 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) IpRoute: default via 192.168.1.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. MostRecentCrashID: bp-4d8bfb66-c42a-40e3-b054-083342120401 PciNetwork: PrefSources: /etc/thunderbird/syspref.js prefs.js user.js ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=13.0.1/20120615181619 (In use) RelatedPackageVersions: gnome-shell 3.4.1-0ubuntu2 rhythmbox-mozilla 2.96-0ubuntu4.1 totem-mozilla 3.0.1-0ubuntu21 RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-4d8bfb66-c42a-40e3-b054-083342120401 bp-5a6c6702-1af2-4747-87ac-7e5152120203 UpgradeStatus: Upgraded to precise on 2012-05-03 (80 days ago) WifiSyslog: dmi.bios.date: 09/11/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: FN27V10 dmi.board.vendor: Shuttle Inc dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/11/2006:svnShuttleInc:pnSN27V10:pvr:rvnShuttleInc:rnFN27V10:rvr:cvn:ct3:cvr: dmi.product.name: SN27V10 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1027564/+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 953564] Re: Foward or backward in progress bar often causes the disappearance of legends
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- 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/953564 Title: Foward or backward in progress bar often causes the disappearance of legends Status in totem package in Ubuntu: Expired Bug description: Reproduced: 1) Open Video (.avi) + legend (.srt) in the same name 2) Click in progress bar sometimes The legends disappear. --- ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 CheckboxSubmission: 622b42fa9ef9d3b69804517c9688ce18 CheckboxSystem: 6a51181f3da22e0f4cddc1735a0ba0ba DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) NonfreeKernelModules: fglrx Package: totem 3.0.1-0ubuntu20 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 Tags: precise Uname: Linux 3.2.0-18-generic-pae i686 UpgradeStatus: Upgraded to precise on 2012-03-13 (2 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/953564/+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 1828649] Re: Wayland session freezes
[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/1828649 Title: Wayland session freezes Status in gnome-shell package in Ubuntu: Expired Bug description: When I switch to wayland the gnome desktop locks up before I see my desktop. It doesn't lock up when I have my laptop closed and only one display connected. When I connect up the second display, it locks up every time. I tried deleting my monitors.xml file.. that doesn't make any difference. I was able to get it to work by connecting one display via DisplayPort. When I connect the second display, via active HDMI to DisplayPort on dock, it doesn't work if I select Wayland. This wire configuration works fine with Xorg. Additionally, when I lift my laptop screen, one of my monitors goes out and re-enabling it causes another to go off. Linux kernel is not smart enough to drive the 3 displays. I am able to drive two monitors and have my laptop screen open in Windows just fine. Of importance is that my DisplayPort to HDMI adaptor is ACTIVE. If I was to use a PASSIVE adaptor, I cannot drive two external displays and the laptop display. With my laptop screen closed, I was able to drive both displays in Wayland just fine in 18.10 so this is a regression. The GNU/Linux kernel has always (as far as I know) been lacking in smarts to drive all three displays. This work system is has Intel 4000 Integrated video (Lenovo ThinkPad laptop). Main screen is 2560x1600 via DisplayPort to laptop. Secondary screen is 1920x1200 via DisplayPort to laptop dock. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 10 16:55:27 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time 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:2203] InstallationDate: Installed on 2019-03-25 (46 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=7e84182c-37f4-407a-91ca-1b6bbec80a00 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GCETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCETB2WW(2.72):bd11/15/2018:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.sku: LENOVO_MT_3435 dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828649/+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 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
I have tried to follow the instructions, but not sure if I did it correctly. Does this link help? https://errors.ubuntu.com/oops/d2e06dde- a9d9-11e9-a2e9-fa163e6cac46 -- 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/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc Status in xorg-server package in Ubuntu: Incomplete Status in xorg package in Fedora: Unknown Bug description: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837081/+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 1835863] Re: Screens do not stay off when blanking
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1835863 Title: Screens do not stay off when blanking Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: After some idle period (5-15 minutes) the screens are supposed to blank and power off. They appear to do this once but then come right back on and stay on. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 9 00:09:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.0.0-19-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.0.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT / Grenada XT [Radeon R9 290X/390X] [1002:67b0] (rev 80) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon R9 390X [1043:04df] InstallationDate: Installed on 2019-06-21 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=df9fe4e8-eacc-47f5-9df4-85a524802645 ro quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2704 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97I-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2704:bd02/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97I-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1835863/+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 1835863] Re: Screens do not stay off when blanking
** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1835863 Title: Screens do not stay off when blanking Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: After some idle period (5-15 minutes) the screens are supposed to blank and power off. They appear to do this once but then come right back on and stay on. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 9 00:09:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.0.0-19-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.0.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT / Grenada XT [Radeon R9 290X/390X] [1002:67b0] (rev 80) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon R9 390X [1043:04df] InstallationDate: Installed on 2019-06-21 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=df9fe4e8-eacc-47f5-9df4-85a524802645 ro quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2704 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97I-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2704:bd02/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97I-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1835863/+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 1835863] Re: Screens do not stay off when blanking
Why is this still marked incomplete? What other info is necessary? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1835863 Title: Screens do not stay off when blanking Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: After some idle period (5-15 minutes) the screens are supposed to blank and power off. They appear to do this once but then come right back on and stay on. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 9 00:09:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.0.0-19-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.0.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT / Grenada XT [Radeon R9 290X/390X] [1002:67b0] (rev 80) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon R9 390X [1043:04df] InstallationDate: Installed on 2019-06-21 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=df9fe4e8-eacc-47f5-9df4-85a524802645 ro quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2704 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97I-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2704:bd02/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97I-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1835863/+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 1836881] Re: gnome-shell freeze
OK I missed some steps there sorry... The command: apport-cli --hanging -P PID will give you a link to help you complete creation of a new bug. You then need to follow that link, on any machine. Don't send us that link. After you have created a new bug, please tell us its ID. If that didn't work then please look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. -- 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/1836881 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: My gnome session freezes, mouse works fine but cannot start applications. I am able to enter one of the tty terminals and kill the session. This happens a few times a day and started a week ago probably. Douglas ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 12:29:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 4.15.0-52-generic, x86_64: installed nvidia, 418.56, 4.15.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1208] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1207] InstallationDate: Installed on 2018-01-13 (550 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 002: ID 0461:4e81 Primax Electronics, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator PH317-51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=455417ef-94fe-4ab8-97b7-0b992c951267 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienna_KLS dmi.board.vendor: KBL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnPredatorPH317-51:pvrV1.05:rvnKBL:rnSienna_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH317-51 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 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/ubuntu/+source/gnome-shell/+bug/1836881/+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 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
To confirm we have the right stack trace, please follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc Status in xorg-server package in Ubuntu: Incomplete Status in xorg package in Fedora: Unknown Bug description: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837081/+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 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)
** Changed in: mesa (Ubuntu)
Status: Incomplete => Confirmed
--
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/1836772
Title:
Xorg crash on 3d-enabled virgl (Haswell host)
Status in mesa package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Invalid
Bug description:
I am running a KVM virtual machine with 3D acceleration (virgl). The
host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
session started crashing just after the login. In xorg logs, I see
this:
[15.338] (WW) modeset(0): Page flip failed: Invalid argument
[15.338] (EE) modeset(0): present flip failed
[15.397] (WW) modeset(0): Page flip failed: Invalid argument
[15.397] (EE) modeset(0): present flip failed
[15.418] (WW) modeset(0): Page flip failed: Invalid argument
[15.419] (EE) modeset(0): present flip failed
[15.440] (WW) modeset(0): Page flip failed: Invalid argument
[15.440] (EE) modeset(0): present flip failed
[15.460] (WW) modeset(0): Page flip failed: Invalid argument
[15.460] (EE) modeset(0): present flip failed
[15.975] (WW) modeset(0): Page flip failed: Invalid argument
[15.976] (EE) modeset(0): present flip failed
[16.039] (WW) modeset(0): Page flip failed: Invalid argument
[16.040] (EE) modeset(0): present flip failed
[16.064] (WW) modeset(0): Page flip failed: Invalid argument
[16.064] (EE) modeset(0): present flip failed
[16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
0:11(2): error: value of type vec4 cannot be assigned to variable of type
error
0:12(2): error: `color1' undeclared
0:12(2): error: value of type vec4 cannot be assigned to variable of type
error
[16.096] Program source:
#ifdef GL_ES
precision mediump float;
#endif
#define ATLAS_DIM_INV 0.0009765625
varying vec2 glyph_pos;
uniform vec4 fg;
uniform sampler2D atlas;
void main() {
vec4 mask = texture2D(atlas, glyph_pos);
vec4 source = fg;
color0 = source * mask;
color1 = source.a * mask;
}
[16.096] (EE)
Fatal server error:
[16.096] (EE) GLSL compile failure
Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
18.0.0~rc5-1ubuntu1 helps.
Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.
On the host, the GPU is Intel Haswell:
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon
E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
[8086:0412] (rev 06)
The CPU is Intel(R) Core(TM) i7-4770S CPU.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 16 20:52:03 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.12.0-20181126_142135-anatol
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-4.0
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-4.0
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this
[Desktop-packages] [Bug 1836805] Re: screen frozen after reboot
Please go to step 2 in: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- 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/1836805 Title: screen frozen after reboot Status in xorg-server package in Ubuntu: Incomplete Bug description: After I installed Ubuntu 19.04 (fresh install with hard drive erasing), I was able to login once just after install. But then after reboot, the screen freezes in the middle of the boot process and I never get the login banner. I was able to launch the recovery mode and get some information through journalctl command and it seems that the problem is related to a Wayland server crash. I don't really know if the problem comes from Wayland or Gnome. The first worrying error message is : "gnome_shell[1165]: Failed to apply DRM plane transform 0: Permission non accordée" (ie, Permission denied in french) Thanks to the recovery mode I was able to upgrade via "apt-get update" and "apt-get upgrade", but the symptoms were the same after a reboot I uncommented the "Enable=true" flag of the [debug] section of /etc/gdm3/custom.conf and I provide and extract of the journalctl output related to the error as an attachment to this report (journalctl_extract.txt part). I also provide some system information (system.txt pat). I hope this may help to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-07-15 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gdm3 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-07-18T07:25:10.575513 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+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 1837160] Re: Syslog filled with millions of entries per hour with stack trace ending in clutter_actor_get_child_at_index and clutter_actor_get_n_children, called from animation
Please run this command to send us more information about the machine: apport-collect 1837160 Please also be sure to uninstall all extensions, not just disable them. ** Summary changed: - Syslog Filled with Millions of Entries per Hour with Stack Trace Ending in /org/gnome/shell/ui/animation.js and /org/gnome/gjs/modules/_legacy.js + Syslog filled with millions of entries per hour with stack trace ending in clutter_actor_get_child_at_index and clutter_actor_get_n_children, called from animation.js:53/57/59 ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Tags added: bionic ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1837160 Title: Syslog filled with millions of entries per hour with stack trace ending in clutter_actor_get_child_at_index and clutter_actor_get_n_children, called from animation.js:53/57/59 Status in gnome-shell package in Ubuntu: Incomplete Bug description: [Sys Info] Description: Ubuntu 18.04.2 LTS Release: 18.04 gnome-shell: Installed: 3.28.4-0ubuntu18.04.1 [Description] I'm seeing several GB/day of syslog entries by org.gnome.Shell.desktop /gnome-shell, causing the / partition to eventually run out of space (which is how I found out about this). It is a repetition of the following block over and over again. [Reproduciblity] So far as I can tell, simply logging in to the GNOME desktop starts the logging sequence. Disabling shell extensions via Tweaks has no effect. [From /var/log/syslog -- N.B. disregard "trusty", I'm running bionic] Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8904d70), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8904d70), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8904d70), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8905ab0), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8905ab0), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8905ab0), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611cd002a30), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611cd002a30), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such
[Desktop-packages] [Bug 1837087] Re: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right
** Summary changed: - /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. + gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags added: radeon -- 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/1837087 Title: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/a72ac96e774740ca840ce2bfc8a7bfe99c6d68f3 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/gnome-shell/+bug/1837087/+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 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
** Description changed: - I’m not exactly sure if this belongs here, libva, mesa, or upstream - somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that program - is. + Buggy as Kodi is, this seems to be a problem specifically with mesa-va- + drivers. Kodi has worked just fine on my system, as recently as July 6th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to- desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- - XBMC PPA) since its release in June, but in between July 7th and 16th, I - did upgrade Nouveau: - - 2019-07-07 06:50:36 upgrade libdrm-nouveau2:amd64 2.4.95-1~18.04.1 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:50:36 status half-configured libdrm-nouveau2:amd64 2.4.95-1~18.04.1 - 2019-07-07 06:50:36 status unpacked libdrm-nouveau2:amd64 2.4.95-1~18.04.1 - 2019-07-07 06:50:36 status half-configured libdrm-nouveau2:i386 2.4.95-1~18.04.1 - 2019-07-07 06:50:36 status half-installed libdrm-nouveau2:amd64 2.4.95-1~18.04.1 - 2019-07-07 06:50:37 status half-installed libdrm-nouveau2:amd64 2.4.95-1~18.04.1 - 2019-07-07 06:50:37 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:50:37 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:50:37 upgrade libdrm-nouveau2:i386 2.4.95-1~18.04.1 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:50:37 status half-configured libdrm-nouveau2:i386 2.4.95-1~18.04.1 - 2019-07-07 06:50:37 status unpacked libdrm-nouveau2:i386 2.4.95-1~18.04.1 - 2019-07-07 06:50:37 status half-installed libdrm-nouveau2:i386 2.4.95-1~18.04.1 - 2019-07-07 06:50:38 status half-installed libdrm-nouveau2:i386 2.4.95-1~18.04.1 - 2019-07-07 06:50:38 status unpacked libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:50:38 status unpacked libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 - - 2019-07-07 06:51:44 configure libdrm-nouveau2:amd64 2.4.97-ubuntu1~18.04.1 - 2019-07-07 06:51:44 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:51:44 status half-configured libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:51:44 status installed libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:51:44 configure libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:51:44 status unpacked libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:51:44 status half-configured libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 - 2019-07-07 06:51:44 status installed libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 - - (Another reason I’m guessing this is a Nouveau problem is because I - later tried switching to the official NVidia drivers, didn’t get this - bug, and then later encountered a distinct yet worse bug that locks up - the whole system. So, now I’m back to using Nouveau.) + XBMC PPA) since its release in June, but in between July 6th and 16th, I + did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2 + 19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers” package + to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates Bionic + repository), however, Kodi works again, without even requiring me to + restart my machine. So, this is likely a problem with “mesa-va-drivers”. I tried looking in Xorg.0.log: [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620 [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines: [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz eP) …that’s all that appears in the log when I try to load Kodi and a crash happens. I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if you need more information, I’ve attached a hardinfo report, too. I hope this bug can get fixed, soon. Thanks! ** No longer affects: xserver-xorg-video-nouveau (Ubuntu) -- 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/1836979 Title: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed” Status in mesa package in Ubuntu: New Bug description: Buggy as Kodi is, this seems to be a problem specifically with mesa- va-drivers. Kodi has worked just fine on my
[Desktop-packages] [Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
Sweet mother of the Muses, I just downgraded the mesa-va-drivers package to 18.0.0~rc5-1ubuntu1 (since that’s the one from the non-updates Bionic repository) and Kodi works again! Then, this is a problem specifically with the mesa-va-drivers package. I’ll have to update the description accordingly. -- 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/1836979 Title: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed” Status in mesa package in Ubuntu: New Bug description: Buggy as Kodi is, this seems to be a problem specifically with mesa- va-drivers. Kodi has worked just fine on my system, as recently as July 6th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to-desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- XBMC PPA) since its release in June, but in between July 6th and 16th, I did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers” package to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates Bionic repository), however, Kodi works again, without even requiring me to restart my machine. So, this is likely a problem with “mesa-va- drivers”. I tried looking in Xorg.0.log: [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620 [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines: [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz eP) …that’s all that appears in the log when I try to load Kodi and a crash happens. I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if you need more information, I’ve attached a hardinfo report, too. I hope this bug can get fixed, soon. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+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 1828663] Re: policykit failures due to internal user id mismatch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: polkit-qt-1 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1828663 Title: policykit failures due to internal user id mismatch Status in PolicyKit: New Status in lubuntu-meta package in Ubuntu: Invalid Status in lxqt-policykit package in Ubuntu: Invalid Status in policykit-1 package in Ubuntu: Confirmed Status in polkit-qt-1 package in Ubuntu: Confirmed Bug description: After adding a second user to the sudo group any authentication in the QT applications menu fails, till I manually remove the second user from the sudo group by issuing deluser chiara sudo in terminal window. Lubuntu 19.04 (fresh install, in italian) 1)open the preferences/LXQt settins/user and groups menu from the application menu 2)add new user, before saving add it to sudo group; save (password asked for user currently logged on, as expected - then new user password asked, user created -all ok) 3)restart system 4) log in as newly created user; open the same interface preferences/LXQt settins/user and groups; try changing the full name field (properties of your own user): logged user password asked (and... why? User two is changing himself) 5)popup showed: "Error executing command as another user: Not authorized" & user unchanged. 6)if you exit session, reenter with the first user, also him is now unable to use interface ti change users via interface 7)using terminal, delete second user from sudo group 8)restart system 9)athenticated interface working again. It happened me both at home on a phisical laptop and on a virtual machine at office, where I could do it all twice. By the way, also plasma-discover tells me I haven't the right to update/install when I have two sudoers (tried at home to remove second sudoer to fix it, and it worked) So it seems that the authentication mechanism of the QT graphical interface fails when there are more then one sudoer on the system - but only for applications started from the application menu. Launching the same application via terminal (sudo plasma-discovery) works. commands issued by the interface (which lead to "unauthorized" error: --change user pkexec --disable-internal-agent lxqt-admin-user-helper usermod -c marco marcop --plasma-discover polkit-agent-helper-1 marcop To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1828663/+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 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
There was an update to Mesa over in the Ubuntu-X-Swat PPA today (by which I mean the “Updates” one), from 19.0.2-1ubuntu1.1~18.04.1 to 19.0.8-0ubuntu0~18.04.1. …Sadly, as I discovered—after installing the updates, then restarting and trying Kodi again—this bug is still present and still works exactly the same. (While I’m here, does anyone know how I would file a bug with the nvidia-340 package? I mean, I don’t know how much we can do about that driver, given its proprietary nature, but I want to try, at least. I just want one of my graphics drivers working so I can use my media player again… (sigh)) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1836979 Title: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed” Status in mesa package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I’m not exactly sure if this belongs here, libva, mesa, or upstream somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that program is. Kodi has worked just fine on my system, as recently as July 6th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to-desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- XBMC PPA) since its release in June, but in between July 7th and 16th, I did upgrade Nouveau: 2019-07-07 06:50:36 upgrade libdrm-nouveau2:amd64 2.4.95-1~18.04.1 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:50:36 status half-configured libdrm-nouveau2:amd64 2.4.95-1~18.04.1 2019-07-07 06:50:36 status unpacked libdrm-nouveau2:amd64 2.4.95-1~18.04.1 2019-07-07 06:50:36 status half-configured libdrm-nouveau2:i386 2.4.95-1~18.04.1 2019-07-07 06:50:36 status half-installed libdrm-nouveau2:amd64 2.4.95-1~18.04.1 2019-07-07 06:50:37 status half-installed libdrm-nouveau2:amd64 2.4.95-1~18.04.1 2019-07-07 06:50:37 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:50:37 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:50:37 upgrade libdrm-nouveau2:i386 2.4.95-1~18.04.1 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:50:37 status half-configured libdrm-nouveau2:i386 2.4.95-1~18.04.1 2019-07-07 06:50:37 status unpacked libdrm-nouveau2:i386 2.4.95-1~18.04.1 2019-07-07 06:50:37 status half-installed libdrm-nouveau2:i386 2.4.95-1~18.04.1 2019-07-07 06:50:38 status half-installed libdrm-nouveau2:i386 2.4.95-1~18.04.1 2019-07-07 06:50:38 status unpacked libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:50:38 status unpacked libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 configure libdrm-nouveau2:amd64 2.4.97-ubuntu1~18.04.1 2019-07-07 06:51:44 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status half-configured libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status installed libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 configure libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status unpacked libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status half-configured libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status installed libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 (Another reason I’m guessing this is a Nouveau problem is because I later tried switching to the official NVidia drivers, didn’t get this bug, and then later encountered a distinct yet worse bug that locks up the whole system. So, now I’m back to using Nouveau.) I tried looking in Xorg.0.log: [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620 [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines: [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz eP) …that’s all that appears in the log when I try to load Kodi and a crash happens. I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if you need more information, I’ve attached a hardinfo report, too. I hope this bug can
[Desktop-packages] [Bug 1837087] Re: /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && b
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1837087 Title: /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/a72ac96e774740ca840ce2bfc8a7bfe99c6d68f3 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/gnome-shell/+bug/1837087/+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 1837160] Re: Syslog Filled with Millions of Entries per Hour with Stack Trace Ending in /org/gnome/shell/ui/animation.js and /org/gnome/gjs/modules/_legacy.js
** Summary changed: - Syslog Filled with Millions of Entires per Hour with Stack Trace Ending in /org/gnome/gjs/modules/_legacy.js + Syslog Filled with Millions of Entries per Hour with Stack Trace Ending in /org/gnome/shell/ui/animation.js and /org/gnome/gjs/modules/_legacy.js -- 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/1837160 Title: Syslog Filled with Millions of Entries per Hour with Stack Trace Ending in /org/gnome/shell/ui/animation.js and /org/gnome/gjs/modules/_legacy.js Status in gnome-shell package in Ubuntu: New Bug description: [Sys Info] Description: Ubuntu 18.04.2 LTS Release: 18.04 gnome-shell: Installed: 3.28.4-0ubuntu18.04.1 [Description] I'm seeing several GB/day of syslog entries by org.gnome.Shell.desktop /gnome-shell, causing the / partition to eventually run out of space (which is how I found out about this). It is a repetition of the following block over and over again. [Reproduciblity] So far as I can tell, simply logging in to the GNOME desktop starts the logging sequence. Disabling shell extensions via Tweaks has no effect. [From /var/log/syslog -- N.B. disregard "trusty", I'm running bionic] Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8904d70), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8904d70), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8904d70), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8905ab0), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8905ab0), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8905ab0), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611cd002a30), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611cd002a30), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611cd002a30), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or
[Desktop-packages] [Bug 1837160] [NEW] Syslog Filled with Millions of Entries per Hour with Stack Trace Ending in /org/gnome/shell/ui/animation.js and /org/gnome/gjs/modules/_legacy.js
Public bug reported: [Sys Info] Description:Ubuntu 18.04.2 LTS Release:18.04 gnome-shell: Installed: 3.28.4-0ubuntu18.04.1 [Description] I'm seeing several GB/day of syslog entries by org.gnome.Shell.desktop /gnome-shell, causing the / partition to eventually run out of space (which is how I found out about this). It is a repetition of the following block over and over again. [Reproduciblity] So far as I can tell, simply logging in to the GNOME desktop starts the logging sequence. Disabling shell extensions via Tweaks has no effect. [From /var/log/syslog -- N.B. disregard "trusty", I'm running bionic] Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8904d70), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8904d70), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8904d70), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8905ab0), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8905ab0), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c8905ab0), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611cd002a30), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611cd002a30), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_n_children: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611cd002a30), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c81d9f00), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: clutter_actor_get_child_at_index: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 18 18:47:50 robyn-trusty gnome-shell[18929]: Object Clutter.Actor (0x5611c81d9f00), has been already deallocated - impossible to access it. This might be caused by
[Desktop-packages] [Bug 1836805] Re: screen frozen after reboot
Generated the prevboot.txt (see attached). I did not find any file related to wayland crash in /var/crash. I did find though an xorg crash file dated from this morning. I sent it through ubuntu-bug though I was not asked a bug number (I am not sure it worked). I do not really understand what happened this morning as the xorg config ended up working. I don't know if this new fact may help solving the issue or is rather disturbing... ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+attachment/5277936/+files/prevboot.txt -- 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/1836805 Title: screen frozen after reboot Status in xorg-server package in Ubuntu: Incomplete Bug description: After I installed Ubuntu 19.04 (fresh install with hard drive erasing), I was able to login once just after install. But then after reboot, the screen freezes in the middle of the boot process and I never get the login banner. I was able to launch the recovery mode and get some information through journalctl command and it seems that the problem is related to a Wayland server crash. I don't really know if the problem comes from Wayland or Gnome. The first worrying error message is : "gnome_shell[1165]: Failed to apply DRM plane transform 0: Permission non accordée" (ie, Permission denied in french) Thanks to the recovery mode I was able to upgrade via "apt-get update" and "apt-get upgrade", but the symptoms were the same after a reboot I uncommented the "Enable=true" flag of the [debug] section of /etc/gdm3/custom.conf and I provide and extract of the journalctl output related to the error as an attachment to this report (journalctl_extract.txt part). I also provide some system information (system.txt pat). I hope this may help to solve the issue. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-07-15 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gdm3 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-07-18T07:25:10.575513 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+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 1836659] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox again
I was getting this error as well. However, i typically use Gnome fallback, and decided to try using regular Ubuntu desktop. When I do, I no longer get the error - password fields behave as expected. -- 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/1836659 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox again Status in firefox package in Ubuntu: Incomplete Bug description: On an uptodate Ubuntu 18.04.2 LTS system I am observing the same symptoms as in bug https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 When I focus a password field in Firefox, it starts focusing and unfocusing rapidly, making it difficult to type passwords. Also, CPU usage goes up with the 4 processes eating most: %Cpu(s): 25,3 us, 11,0 sy, 0,0 ni, 63,5 id Xorg 60% gnome-flashback 21% firefox 20% ibus-daemon 4% Launching Firefox with GTK_IM_MODULE=xim firefox makes it go away. This started several (~7) days ago. $ apt list gnome-shell ibus firefox Listing... Done firefox/bionic-updates,bionic-security,now 68.0+build3-0ubuntu0.18.04.1 amd64 [installed] gnome-shell/bionic-updates,now 3.28.4-0ubuntu18.04.1 amd64 [installed] ibus/bionic,now 1.5.17-3ubuntu4 amd64 [installed] $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1836659/+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 1835297] Re: Precision 7730 smart card reader does not work out of box
The link is not working. Skip that. I have the following commands in case it helps: *-usb description: Mass storage device product: DataTraveler 3.0 vendor: Kingston physical id: 1 bus info: usb@2:1 logical name: scsi0 version: 0.01 serial: 0026186871D2F02178471906 capabilities: usb-3.00 scsi emulated scsi-host configuration: driver=usb-storage maxpower=296mA speed=5000Mbit/s *-disk description: SCSI Disk product: DataTraveler 3.0 vendor: Kingston physical id: 0.0.0 bus info: scsi@0:0.0.0 logical name: /dev/sda serial: 0 size: 7377MiB (7736MB) capabilities: removable configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512 *-medium physical id: 0 logical name: /dev/sda size: 7377MiB (7736MB) capabilities: partitioned partitioned:dos configuration: signature=06593661 *-storage description: Non-Volatile memory controller product: Toshiba America Info Systems vendor: Toshiba America Info Systems physical id: 0 bus info: pci@:02:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: storage pciexpress pm msi msix nvm_express bus_master cap_list configuration: driver=nvme latency=0 resources: irq:16 memory:b050-b0503fff Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 00:00.0 Host bridge: Intel Corporation Device 3ec4 (rev 07) 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Device 3e94 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 07) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device a379 (rev 10) 00:14.0 USB controller: Intel Corporation Device a36d (rev 10) 00:14.2 RAM memory: Intel Corporation Device a36f (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10) 00:16.0 Communication controller: Intel Corporation Device a360 (rev 10) 00:1b.0 PCI bridge: Intel Corporation Device a32c (rev f0) 00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0) 00:1c.5 PCI bridge: Intel Corporation Device a33d (rev f0) 00:1c.6 PCI bridge: Intel Corporation Device a33e (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10) 00:1f.3 Audio device: Intel Corporation Device a348 (rev 10) 00:1f.4 SMBus: Intel Corporation Device a323 (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a324 (rev 10) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM (rev 10) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Polaris10] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 580] 02:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 0116 6e:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5260 (rev 01) 6f:00.0 Network controller: Intel Corporation Device 2526 (rev 29) Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x0951 Kingston Technology idProduct 0x1666 DataTraveler G4 bcdDevice0.01 iManufacturer 1 Kingston iProduct2 DataTraveler 3.0 iSerial 3 0026186871D2F02178471906 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 74mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5
[Desktop-packages] [Bug 1824409] Re: Client side decoration in Firefox with Pop theme has a slight imperfection
** Changed in: firefox (Ubuntu) Importance: Undecided => Low ** Changed in: firefox (Ubuntu) Status: New => Triaged -- 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/1824409 Title: Client side decoration in Firefox with Pop theme has a slight imperfection Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Triaged Bug description: With Firefox new client-side decoration, when using Pop theme, there is a small white line upon the first tab that looks unclean. Also, don't use the whole title bar height, which might look cleaner, or not :-) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0.3+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 3795 F pulseaudio /dev/snd/pcmC1D0c: franck 3795 F...m pulseaudio /dev/snd/controlC0: franck 3795 F pulseaudio BuildID: 20190410124846 Channel: Unavailable CurrentDesktop: GNOME Date: Thu Apr 11 20:44:57 2019 EcryptfsInUse: Yes 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) IpRoute: default via 10.0.0.1 dev enp0s25 proto dhcp metric 100 default via 10.0.0.1 dev wlp3s0 proto dhcp metric 600 10.0.0.0/24 dev enp0s25 proto kernel scope link src 10.0.0.14 metric 100 10.0.0.0/24 dev wlp3s0 proto kernel scope link src 10.0.0.246 metric 600 10.204.48.0/24 dev lxdbr0 proto kernel scope link src 10.204.48.1 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0.3/20190410124846 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) 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: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1824409/+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 1836659] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox again
Affects me too. $ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 $ apt list gnome-shell ibus firefox Listing... Done firefox/bionic-updates,bionic-security,now 68.0+build3-0ubuntu0.18.04.1 amd64 [installed] gnome-shell/bionic-updates 3.28.4-0ubuntu18.04.1 amd64 [upgradable from: 3.28.3+git20190124-0ubuntu18.04.2] ibus/bionic,now 1.5.17-3ubuntu4 amd64 [installed] $ echo $GTK_IM_MODULE ibus The Ubuntu One sign-in page is affected, amongst others; I had to copy and paste my password to log in to make this comment! ( https://launchpad.net/+login ) -- 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/1836659 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox again Status in firefox package in Ubuntu: Incomplete Bug description: On an uptodate Ubuntu 18.04.2 LTS system I am observing the same symptoms as in bug https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 When I focus a password field in Firefox, it starts focusing and unfocusing rapidly, making it difficult to type passwords. Also, CPU usage goes up with the 4 processes eating most: %Cpu(s): 25,3 us, 11,0 sy, 0,0 ni, 63,5 id Xorg 60% gnome-flashback 21% firefox 20% ibus-daemon 4% Launching Firefox with GTK_IM_MODULE=xim firefox makes it go away. This started several (~7) days ago. $ apt list gnome-shell ibus firefox Listing... Done firefox/bionic-updates,bionic-security,now 68.0+build3-0ubuntu0.18.04.1 amd64 [installed] gnome-shell/bionic-updates,now 3.28.4-0ubuntu18.04.1 amd64 [installed] ibus/bionic,now 1.5.17-3ubuntu4 amd64 [installed] $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1836659/+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 1835297] Re: Precision 7730 smart card reader does not work out of box
Following https://help.ubuntu.com/community/CommonAccessCard Does not work to get the smartcard reader working. pcsc_scan returns 'Waiting for first reader' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1835297 Title: Precision 7730 smart card reader does not work out of box Status in pcsc-lite package in Ubuntu: New Bug description: The Canonical certified smart card reader will not function until the following commands are run: sudo mkdir /tmp/USH cd /tmp/USH sudo mkdir debs cd debs sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite- dev_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/libpcsclite1_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/pcscd_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc- tools_1.5.4-1_amd64.deb cd .. sudo apt-get -f install -y sudo apt purge lib-pcsc* pcscd* -y sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get install libusb-1.0-0-dev sudo wget https://alioth- archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2 sudo tar xvfj ccid-*.tar.bz2 cd ccid-1.4.25/ ./configure sudo make sudo make install sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/ sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan Additionally, the following commands, which do the same thing as the above in a cleaner way, do NOT resolve the issue in both the OEM and public image: sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1 sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1835297] Re: Precision 7730 smart card reader does not work out of box
The information Nick previously provided was how they got around the issue using the Kali opensource drivers. Would you like us to follow https://pcsclite.alioth.debian.org/ccid.html#support to get you that information. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1835297 Title: Precision 7730 smart card reader does not work out of box Status in pcsc-lite package in Ubuntu: New Bug description: The Canonical certified smart card reader will not function until the following commands are run: sudo mkdir /tmp/USH cd /tmp/USH sudo mkdir debs cd debs sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite- dev_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/libpcsclite1_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/pcscd_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc- tools_1.5.4-1_amd64.deb cd .. sudo apt-get -f install -y sudo apt purge lib-pcsc* pcscd* -y sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get install libusb-1.0-0-dev sudo wget https://alioth- archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2 sudo tar xvfj ccid-*.tar.bz2 cd ccid-1.4.25/ ./configure sudo make sudo make install sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/ sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan Additionally, the following commands, which do the same thing as the above in a cleaner way, do NOT resolve the issue in both the OEM and public image: sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1 sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- 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/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc Status in xorg-server package in Ubuntu: New Status in xorg package in Fedora: Unknown Bug description: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837081/+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 1835297] Re: Precision 7730 smart card reader does not work out of box
Does this cert indicate only Realtek is certified? The lsusb output is: Bus 001 Device 002: ID 0a5c:5832 Broadcom Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0a5c Broadcom Corp. idProduct 0x5832 bcdDevice1.01 iManufacturer 1 Broadcom Corp iProduct2 5880 iSerial 3 0123456789ABCD bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 139 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 254 Application Specific Interface bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 4 Broadcom USH ** UNRECOGNIZED: 10 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 5 Contacted SmartCard ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 7 5.0V 3.0V 1.8V dwProtocols 3 T=0 T=1 dwDefaultClock 4000 dwMaxiumumClock 4000 bNumClockSupported 0 dwDataRate 9600 bps dwMaxDataRate 25 bps bNumDataRatesSupp. 0 dwMaxIFSD 247 dwSyncProtocols dwMechanical dwFeatures 000102BA Auto configuration based on ATR Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID NAD value other than 0x00 accepted TPDU level exchange dwMaxCCIDMsgLen 271 bClassGetResponse 00 bClassEnvelope 00 wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes
[Desktop-packages] [Bug 1828102] Re: Regression in ModemManager
> I've sponsored this for disco lol, looks like we collided :) since our uploads are identical (I assume) it shouldn't matter which the ubuntu-sru team approves. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1828102 Title: Regression in ModemManager Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in modemmanager source package in Cosmic: Won't Fix Status in modemmanager source package in Disco: In Progress Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] ModemManager disconnects from CDMA modem after 30 sec failing to check signal status due to incorrect error handling [Test case] connect to a cdma device without an extra AT channel (Eg. Samsung brightside phone) and modemmanager will terminate the connection [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1835297] Re: Precision 7730 smart card reader does not work out of box
To add to this the following URL suggests the support and drivers should be bundled: https://certification.ubuntu.com/hardware/201803-26164/ The Dell OEM image does not house the drivers, nor does the Canonical image. Is this expected? Should there be documentation on how to get this working without using opensource drivers since it is certified? What does the certification mean? Is there anything we need to do at Dell to get canonical and Dell to work on getting the Kati.org pcscd* drivers bundled? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1835297 Title: Precision 7730 smart card reader does not work out of box Status in pcsc-lite package in Ubuntu: New Bug description: The Canonical certified smart card reader will not function until the following commands are run: sudo mkdir /tmp/USH cd /tmp/USH sudo mkdir debs cd debs sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite- dev_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/libpcsclite1_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/pcscd_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc- tools_1.5.4-1_amd64.deb cd .. sudo apt-get -f install -y sudo apt purge lib-pcsc* pcscd* -y sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get install libusb-1.0-0-dev sudo wget https://alioth- archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2 sudo tar xvfj ccid-*.tar.bz2 cd ccid-1.4.25/ ./configure sudo make sudo make install sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/ sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan Additionally, the following commands, which do the same thing as the above in a cleaner way, do NOT resolve the issue in both the OEM and public image: sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1 sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
I am sorry about suggesting to delete the extension. One can also turn off the extension until the developer has found a fix. It seems that the use of MPRIS and Pulseaudio may be causing a conflict with Chrome and Chromium version 75 and newer. Any older versions seem not to be affected by the use of Laine. -- 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/1835623 Title: Google Chrome Linux version 75 freezes and then crashes when trying to play any video Status in chromium-browser package in Ubuntu: Invalid Bug description: (upstream bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=983203) Ubuntu 18.04 I expect Chrome to play videos. When I try to play any video on Google Chrome for Linux, any version of 75 or higher, Google Chrome freezes. Chrome 75 will allow sound but no video. All mouse clicks become unresponsive. Attempting to close Chrome after many mouse clicks causes Chrome to crash. Even worse it often also crashes Ubuntu 18.04. Google Chrome 74 or lower work without any problems playing videos. It is a Google Chrome Linux version 75 or higher problem. I cannot believe that neither Google or Ubuntu or any other Linux OS seem to completely ignore this extremely serious problem. I am forced to install Google Chrome 71 to fix video playback problem. I posted on Ubuntu ask, and show over 90 views but no comments. One answer confirms that he has the exact same problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: DistroRelease: Ubuntu 18.04 Env: 'None' 'None' InstallationDate: Installed on 2019-05-02 (66 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181019) Load-Avg-1min: 1.47 Load-Processes-Running-Percent: 0.1% MachineType: MSI MS-7641 NonfreeKernelModules: nvidia_modeset nvidia Package: chromium-browser 75.0.3770.90-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=7181ee96-0bd0-4b3c-9100-fa205ef6bd1d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-55-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm adm cdrom cdrom dip dip lpadmin lpadmin plugdev plugdev sambashare sambashare sudo sudo _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.1 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 760GMA-P34(FX) (MS-7641) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.1:bd04/20/2015:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7641 dmi.product.version: 5.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1835623/+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 1603430] Re: Firefox dropdowns in wrong location
I am also experiencing this on Ubuntu 18.10 Could you please give an update on this issue? 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/1603430 Title: Firefox dropdowns in wrong location Status in Linux Mint: New Status in cinnamon-desktop-environment package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: On Mint 17.3 Cinnamon 64bit. Steps to reproduce: * Do a fresh install. * Run mintupdate and update all packages. * Run firefox. * Start right clicking on the page to open the context menu. Resize the window and perhaps move it around the screen a couple of times. Right click some more. * Observer that, eventually, the context menu will start to appear in incorrect locations on the screen. The same also happens with the search bar, text fields and any other dropdown box. In the worst embodiment of the bug, the menu opens underneath the pointer and treats the release of the mouse button as a click, and so does things the user does not want to do. I believe the root cause is the following bug in GTK+ 3.10.8. Firefox switched over to using GTK+3 in version 46 which is when this bug appeared and has been there ever since. https://bugzilla.gnome.org/show_bug.cgi?id=758609 https://bugzilla.mozilla.org/show_bug.cgi?id=1022241 Mozilla aren't going to fix it because it's a GTK bug. GTK have already fixed it. But Mint 17.3 remains on GTK+ 3.10.8 which does not have the patch. Please roll out the patch for us 17.3 users who cannot upgrade. I can confirm that the problem is solved in Mint 18. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1603430/+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 1834517] Re: Update gnome-shell to 3.32.2
This SRU has now been removed from -proposed due to the failed verification. However, the referenced regression looks like it has been root-caused to mutter rather than gnome-shell, so it's possible this SRU is actually ok to release (possibly only after a fixed mutter has been uploaded). If so, please comment on this bug with the appropriate details and ask an SRU team member on IRC to resurrect this package. -- 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/1834517 Title: Update gnome-shell to 3.32.2 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Committed Bug description: [ Description ] The second stable release in the 3.32 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Mostly crash fixes, possibly regression in the menus popping ups, images textures aspect ratio, Network interface names, world-clocks in calendar, dialog texts, widgets style change [ Related bugs ] https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722886 https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834517 https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831555 https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827953 https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809788 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834517/+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 1827953] Proposed package removed from archive
The version of gnome-shell in the proposed pocket of Disco that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. ** Changed in: gnome-shell (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1827953 Title: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Won't Fix Bug description: [ Description ] Gnome Shell crashes just after login, creating a “login loop” where the user is locked out of their computer. [ Test case ] Configure some “world clocks” in Gnome Clocks (or maybe using some other tool). Expected behaviour (how it worked in cosmic & before): Gnome Shell shows the time for the cities you configured when you click on the date at the top centre. [ Regression potential ] World clocks are not shown for some places To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1827953/+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 1827953] Proposed package removed from archive
The version of gnome-shell in the proposed pocket of Disco that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- 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/1827953 Title: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Won't Fix Bug description: [ Description ] Gnome Shell crashes just after login, creating a “login loop” where the user is locked out of their computer. [ Test case ] Configure some “world clocks” in Gnome Clocks (or maybe using some other tool). Expected behaviour (how it worked in cosmic & before): Gnome Shell shows the time for the cities you configured when you click on the date at the top centre. [ Regression potential ] World clocks are not shown for some places To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1827953/+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 1824507] Re: unity-menubar.patch+global menu plasmoid+CSD causing inconsistant UI under KDE
** Attachment added: "binary-build-with-csd.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1824507/+attachment/5277895/+files/binary-build-with-csd.png -- 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/1824507 Title: unity-menubar.patch+global menu plasmoid+CSD causing inconsistant UI under KDE Status in firefox package in Ubuntu: New Bug description: Without unity-menubar.patch, aka. an official binary build of firefox wouldn't export its traditional menu to global menu plasmoid, nor the unity menu addon. The applied patch works fine on its purpose: to export the menu to a global retriever, whether the DE is. However, it fails to stay the browser consist when Mozilla introduced native client-side decoration (CSD) support on KDE. When we don't use global menu plasmoid but disable titlebar (enable CSD), the window stays slim, and the tab bar stay tightly on top of the window left to the window control icons, but when we add the global menu plasmoid, the window gives a blank area where there is the window control icons on top right, then the opened tab bar. IMHO, it should stay on top like there is no the menu holder plasmoid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1824507/+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 1824507] Re: unity-menubar.patch+global menu plasmoid+CSD causing inconsistant UI under KDE
** Attachment added: "expected.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1824507/+attachment/5277898/+files/expected.png -- 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/1824507 Title: unity-menubar.patch+global menu plasmoid+CSD causing inconsistant UI under KDE Status in firefox package in Ubuntu: New Bug description: Without unity-menubar.patch, aka. an official binary build of firefox wouldn't export its traditional menu to global menu plasmoid, nor the unity menu addon. The applied patch works fine on its purpose: to export the menu to a global retriever, whether the DE is. However, it fails to stay the browser consist when Mozilla introduced native client-side decoration (CSD) support on KDE. When we don't use global menu plasmoid but disable titlebar (enable CSD), the window stays slim, and the tab bar stay tightly on top of the window left to the window control icons, but when we add the global menu plasmoid, the window gives a blank area where there is the window control icons on top right, then the opened tab bar. IMHO, it should stay on top like there is no the menu holder plasmoid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1824507/+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 1824507] Re: unity-menubar.patch+global menu plasmoid+CSD causing inconsistant UI under KDE
** Attachment added: "unity-bar-with-csd.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1824507/+attachment/5277897/+files/unity-bar-with-csd.png -- 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/1824507 Title: unity-menubar.patch+global menu plasmoid+CSD causing inconsistant UI under KDE Status in firefox package in Ubuntu: New Bug description: Without unity-menubar.patch, aka. an official binary build of firefox wouldn't export its traditional menu to global menu plasmoid, nor the unity menu addon. The applied patch works fine on its purpose: to export the menu to a global retriever, whether the DE is. However, it fails to stay the browser consist when Mozilla introduced native client-side decoration (CSD) support on KDE. When we don't use global menu plasmoid but disable titlebar (enable CSD), the window stays slim, and the tab bar stay tightly on top of the window left to the window control icons, but when we add the global menu plasmoid, the window gives a blank area where there is the window control icons on top right, then the opened tab bar. IMHO, it should stay on top like there is no the menu holder plasmoid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1824507/+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 1824507] Re: unity-menubar.patch+global menu plasmoid+CSD causing inconsistant UI under KDE
** Attachment added: "unity-without-csd.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1824507/+attachment/5277896/+files/unity-without-csd.png -- 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/1824507 Title: unity-menubar.patch+global menu plasmoid+CSD causing inconsistant UI under KDE Status in firefox package in Ubuntu: New Bug description: Without unity-menubar.patch, aka. an official binary build of firefox wouldn't export its traditional menu to global menu plasmoid, nor the unity menu addon. The applied patch works fine on its purpose: to export the menu to a global retriever, whether the DE is. However, it fails to stay the browser consist when Mozilla introduced native client-side decoration (CSD) support on KDE. When we don't use global menu plasmoid but disable titlebar (enable CSD), the window stays slim, and the tab bar stay tightly on top of the window left to the window control icons, but when we add the global menu plasmoid, the window gives a blank area where there is the window control icons on top right, then the opened tab bar. IMHO, it should stay on top like there is no the menu holder plasmoid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1824507/+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 1824507] Re: unity-menubar.patch+global menu plasmoid+CSD causing inconsistant UI under KDE
** Attachment added: "binary-build-without-csd.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1824507/+attachment/5277894/+files/binary-build-without-csd.png -- 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/1824507 Title: unity-menubar.patch+global menu plasmoid+CSD causing inconsistant UI under KDE Status in firefox package in Ubuntu: New Bug description: Without unity-menubar.patch, aka. an official binary build of firefox wouldn't export its traditional menu to global menu plasmoid, nor the unity menu addon. The applied patch works fine on its purpose: to export the menu to a global retriever, whether the DE is. However, it fails to stay the browser consist when Mozilla introduced native client-side decoration (CSD) support on KDE. When we don't use global menu plasmoid but disable titlebar (enable CSD), the window stays slim, and the tab bar stay tightly on top of the window left to the window control icons, but when we add the global menu plasmoid, the window gives a blank area where there is the window control icons on top right, then the opened tab bar. IMHO, it should stay on top like there is no the menu holder plasmoid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1824507/+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 1835922] Re: missing gl* symbols in version 19.0.2
Tested 19.0.8 from ppa:ubuntu-x-swat/updates locally and the fix works. Any idea when the fix will be available in the ubuntu repo for Bionic release? I haven't found any way to install from ppa on Heroku. -- 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/1835922 Title: missing gl* symbols in version 19.0.2 Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: New Status in mesa source package in Disco: New Bug description: Linking with libosmesa6-dev version 19.0.2 will fail because all the gl* symbols are missing: ``` [100%] Linking CXX executable bin/minko-converter ../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o): In function `jas_stream_tmpfile': jas_stream.c:(.text+0x6fd): warning: the use of `tmpnam' is dangerous, better use `mkstemp' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::clear(unsigned int, float, float, float, float, float, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0xb3): undefined reference to `glDepthMask' OpenGLES2Context.cpp:(.text+0xd9): undefined reference to `glClearDepth' OpenGLES2Context.cpp:(.text+0xe7): undefined reference to `glClearColor' OpenGLES2Context.cpp:(.text+0xfc): undefined reference to `glClearStencil' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, unsigned int, int)': OpenGLES2Context.cpp:(.text+0x120): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, int)': OpenGLES2Context.cpp:(.text+0x153): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadVertexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x191): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadIndexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x1db): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x297): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x2aa): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x2b9): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteIndexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x332): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x345): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x354): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::setVertexBufferAt(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0x527): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x559): undefined reference to `glVertexAttribPointer' OpenGLES2Context.cpp:(.text+0x59a): undefined reference to `glDisableVertexAttribArray' OpenGLES2Context.cpp:(.text+0x61e): undefined reference to `glEnableVertexAttribArray' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::createVertexAttributeArray()': OpenGLES2Context.cpp:(.text+0x65f): undefined reference to `glGenVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexAttributeArray(unsigned int)': OpenGLES2Context.cpp:(.text+0x6b3): undefined reference to `glDeleteVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadCubeTextureData(unsigned int, minko::render::CubeTexture::Face, unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x6e4): undefined reference to `glBindTexture' OpenGLES2Context.cpp:(.text+0x736): undefined reference to `glTexImage2D' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In
[Desktop-packages] [Bug 1828102] Re: Regression in ModemManager
I've sponsored this for disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1828102 Title: Regression in ModemManager Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in modemmanager source package in Cosmic: Won't Fix Status in modemmanager source package in Disco: In Progress Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] ModemManager disconnects from CDMA modem after 30 sec failing to check signal status due to incorrect error handling [Test case] connect to a cdma device without an extra AT channel (Eg. Samsung brightside phone) and modemmanager will terminate the connection [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1828102] Re: Regression in ModemManager
Cosmic has reached EOL, today: https://lists.ubuntu.com/archives/ubuntu-announce/2019-July/000246.html However, I uploaded this for disco. Note to sru reviewers, this patch was applied to bionic already in bug 1819615 ** Also affects: modemmanager (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: modemmanager (Ubuntu Bionic) Status: New => Fix Released ** Changed in: modemmanager (Ubuntu Cosmic) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1828102 Title: Regression in ModemManager Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in modemmanager source package in Cosmic: Won't Fix Status in modemmanager source package in Disco: In Progress Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] ModemManager disconnects from CDMA modem after 30 sec failing to check signal status due to incorrect error handling [Test case] connect to a cdma device without an extra AT channel (Eg. Samsung brightside phone) and modemmanager will terminate the connection [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1834375] Re: Gaia.com videos unsupported
I did not understand how to comply with this request: " Also, please run the following command in a terminal to attachadditional information to the bug report: apport-collect 1834375" Also, I have a Hantek PC-Oscilloscope which requires Window 7 or XP. Any hope to use it on Ubuntu, ever? Thanks,Bob James On Thursday, June 27, 2019, 04:30:47 AM EDT, Olivier Tilloy wrote: Just tested in an up-to-date 18.04 virtual machine, and I can play the sample videos on gaia.com's home page. What exactly is not working? Streaming videos maybe? Can you share the exact error message that you get? Also, please run the following command in a terminal to attach additional information to the bug report: apport-collect 1834375 Thanks! ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1834375 Title: Gaia.com videos unsupported Status in firefox package in Ubuntu: Incomplete Bug description: Firefox could not play videos on Gaia.com. The error message blamed the browser. So I downloaded and installed the browser Opera, with the same results and message. Both browsers would play Youtube videos. Please enable Gaia.com videos. Thanks. I downloaded the latest Ubuntu release today. 18.04...something ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 26 17:57:24 2019 DistUpgraded: 2019-06-26 11:14:51,559 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] InstallationDate: Installed on 2019-06-25 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=dfa2862a-4da8-414d-9f41-cecde30f67c6 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-06-26 (0 days ago) dmi.bios.date: 06/23/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G2 v02.02 dmi.board.name: 3048h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G2v02.02:bd06/23/2011:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jun 26 10:11:57 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1834375/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1834375 Title: Gaia.com videos unsupported Status in firefox package in Ubuntu: Incomplete Bug description: Firefox could not play videos on Gaia.com. The error message blamed the browser. So I downloaded and installed the browser Opera, with the same results and message. Both browsers would play Youtube videos. Please enable Gaia.com videos. Thanks. I downloaded the latest Ubuntu release today. 18.04...something ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
[Desktop-packages] [Bug 1837098] Re: Can't print in monochrome, only in colour
To add a bit of clarity, I can't *choose* to print in monochrome from and of the UI. The system print dialog shows no options to select monochrome. -- 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/1837098 Title: Can't print in monochrome, only in colour Status in cups package in Ubuntu: New Bug description: Printer is a Samsung C430W connected over wifi and using driverless printing. Everything is discovered and I can print in colour just fine. In Bionic I was able to toggle in to monochrome, but in Disco I am not. I now have to print everything in colour. $ lpoptions -l PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal ISOB5 Legal Letter Custom.WIDTHxHEIGHT MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton Archive ColorModel/Print Color Mode: *RGB cupsPrintQuality/Print Quality: *4 print-scaling/Print Scaling: *auto auto-fit fill fit none I have also attached the output of ipptool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1824409] Re: Client side decoration in Firefox with Pop theme has a slight imperfection
Bug filled upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1567246 ** Bug watch added: Mozilla Bugzilla #1567246 https://bugzilla.mozilla.org/show_bug.cgi?id=1567246 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1567246 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/1824409 Title: Client side decoration in Firefox with Pop theme has a slight imperfection Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: New Bug description: With Firefox new client-side decoration, when using Pop theme, there is a small white line upon the first tab that looks unclean. Also, don't use the whole title bar height, which might look cleaner, or not :-) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0.3+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 3795 F pulseaudio /dev/snd/pcmC1D0c: franck 3795 F...m pulseaudio /dev/snd/controlC0: franck 3795 F pulseaudio BuildID: 20190410124846 Channel: Unavailable CurrentDesktop: GNOME Date: Thu Apr 11 20:44:57 2019 EcryptfsInUse: Yes 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) IpRoute: default via 10.0.0.1 dev enp0s25 proto dhcp metric 100 default via 10.0.0.1 dev wlp3s0 proto dhcp metric 600 10.0.0.0/24 dev enp0s25 proto kernel scope link src 10.0.0.14 metric 100 10.0.0.0/24 dev wlp3s0 proto kernel scope link src 10.0.0.246 metric 600 10.204.48.0/24 dev lxdbr0 proto kernel scope link src 10.204.48.1 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0.3/20190410124846 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) 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: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1824409/+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 1837098] [NEW] Can't print in monochrome, only in colour
Public bug reported: Printer is a Samsung C430W connected over wifi and using driverless printing. Everything is discovered and I can print in colour just fine. In Bionic I was able to toggle in to monochrome, but in Disco I am not. I now have to print everything in colour. $ lpoptions -l PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal ISOB5 Legal Letter Custom.WIDTHxHEIGHT MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton Archive ColorModel/Print Color Mode: *RGB cupsPrintQuality/Print Quality: *4 print-scaling/Print Scaling: *auto auto-fit fill fit none I have also attached the output of ipptool. ** Affects: cups (Ubuntu) Importance: Undecided Assignee: Till Kamppeter (till-kamppeter) Status: New ** Attachment added: "out.txt" https://bugs.launchpad.net/bugs/1837098/+attachment/5277893/+files/out.txt -- 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/1837098 Title: Can't print in monochrome, only in colour Status in cups package in Ubuntu: New Bug description: Printer is a Samsung C430W connected over wifi and using driverless printing. Everything is discovered and I can print in colour just fine. In Bionic I was able to toggle in to monochrome, but in Disco I am not. I now have to print everything in colour. $ lpoptions -l PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal ISOB5 Legal Letter Custom.WIDTHxHEIGHT MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton Archive ColorModel/Print Color Mode: *RGB cupsPrintQuality/Print Quality: *4 print-scaling/Print Scaling: *auto auto-fit fill fit none I have also attached the output of ipptool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1824657] Re: GNOME shell crash
I also have problems with the GNOME desktop randomly crashing after upgrading to Ubuntu 19.04. Here is an output of /var/crash: rwxrwsrwt 2 root whoopsie 4096 Jul 18 13:25 . -rw--- 1 whoopsie whoopsie 37 Jul 18 13:25 _usr_lib_tracker_tracker-extract.1001.uploaded -rw--- 1 whoopsie whoopsie 37 Jul 18 13:25 _usr_share_hplip_uiscan.py.1001.uploaded -rw--- 1 whoopsie whoopsie 37 Jul 18 13:24 _usr_lib_xorg_Xorg.1001.uploaded -rw--- 1 whoopsie whoopsie 37 Jul 18 13:24 _usr_bin_nemo.1001.uploaded -rw--- 1 whoopsie whoopsie 37 Jul 18 13:24 _usr_share_terminator_terminator.1001.uploaded -rwxrwxrwx 1 root whoopsie0 Jul 18 13:03 .lock -rw-r- 1 watkec whoopsie 269182 Jul 16 17:24 _usr_share_terminator_terminator.1001.crash -rw-r--r-- 1 watkec whoopsie0 Jul 16 17:24 _usr_share_terminator_terminator.1001.upload -rw-r- 1 watkec whoopsie 22136200 Jul 16 14:22 _usr_share_hplip_uiscan.py.1001.crash -rw-r--r-- 1 watkec whoopsie0 Jul 16 14:22 _usr_share_hplip_uiscan.py.1001.upload -rw-r- 1 watkec whoopsie 4028361 Jul 16 13:50 _usr_lib_tracker_tracker-extract.1001.crash -rw-r--r-- 1 watkec whoopsie0 Jul 16 13:50 _usr_lib_tracker_tracker-extract.1001.upload -rw-r- 1 watkec whoopsie 12628223 Jul 15 15:34 _usr_lib_xorg_Xorg.1001.crash -rw-r--r-- 1 watkec whoopsie0 Jul 15 15:34 _usr_lib_xorg_Xorg.1001.upload -rw-r- 1 watkec whoopsie 44300035 Jul 15 14:48 _usr_bin_nemo.1001.crash -rw-r--r-- 1 watkec whoopsie0 Jul 15 14:48 _usr_bin_nemo.1001.upload drwxr-xr-x 16 root root 4096 May 21 14:28 .. Thanks for working on this. -- 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/1824657 Title: GNOME shell crash Status in gnome-shell package in Ubuntu: Expired Bug description: I was watching a video on youtube with the Chromium snap browser, suddenly the GNOME shell crashed, no possibility to click for Chromium or other closure, but I managed to access a tty4 session, by pressing the keys: ctrl + alt + f4. Using Ubuntu 19.04 from the beginning of development, first with KDE, after I install GNOME with the metapackage: sudo apt install ubuntu-desktop, eliminating any KDE package, until now I have had no problem. full update, proposed repository disabled. I attach the logs from the time I had the problem, about 10:50 pm, I started with the logs at 10:40 pm with this command: journalctl --since "2019-04-13 22:40:00" ( if it is wrong, let him know) From the logs I see many gnome-shell errors, but obviously I can't decipher them if it was the cause of the problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 23:07:59 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'enabled-extensions' b"['move_cl...@jonathan.bluemosh.com', 'openweather-extens...@jenslody.de', 'sound-output-device-choo...@kgshank.net', 'apps-m...@gnome-shell-extensions.gcampax.github.com', 'applications_m...@rmy.pobox.com', 'gsconn...@andyholmes.github.io', 'move_cl...@rmy.pobox.com', 'desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'enable-animations' b'false' InstallationDate: Installed on 2019-02-18 (53 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash 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/1824657/+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 1837087] Re: /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && b
When I returned to my computer (AMD RX580 graphics, amdgpu) after a while (the screen had entered power saving mode), the gnome-shell process (on XWayland) failed. Unfortunately this crash was not automatically reported by whoopsie / apport and required manual re-submission (bug 1792643). If this was also so for the other (to date only) three reporters, this would explain the low number of reports on errors.ubuntu.com. -- 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/1837087 Title: /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/a72ac96e774740ca840ce2bfc8a7bfe99c6d68f3 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/gnome-shell/+bug/1837087/+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 1837087] [NEW] /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 &
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/a72ac96e774740ca840ce2bfc8a7bfe99c6d68f3 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- 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/1837087 Title: /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/a72ac96e774740ca840ce2bfc8a7bfe99c6d68f3 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/gnome-shell/+bug/1837087/+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 1828102] Re: Regression in ModemManager
Added description changes from comment #5. Please could someone with appropriate rights sponsor the uploads of the attached debdiffs (SRUs)? Thanks. It would be great if at least the SRU for Disco could get uploaded and rolled out. Cosmic is very close before EOL, so it can easily happen that the SRU does not get published in time, so Disco is much more important. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1828102 Title: Regression in ModemManager Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Cosmic: In Progress Status in modemmanager source package in Disco: In Progress Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] ModemManager disconnects from CDMA modem after 30 sec failing to check signal status due to incorrect error handling [Test case] connect to a cdma device without an extra AT channel (Eg. Samsung brightside phone) and modemmanager will terminate the connection [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1828102] Re: Regression in ModemManager
** Description changed: [Impact] + ModemManager disconnects from CDMA modem after 30 sec failing to check + signal status due to incorrect error handling + [Test case] + + connect to a cdma device without an extra AT channel (Eg. Samsung + brightside phone) and modemmanager will terminate the connection [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1828102 Title: Regression in ModemManager Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Cosmic: In Progress Status in modemmanager source package in Disco: In Progress Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] ModemManager disconnects from CDMA modem after 30 sec failing to check signal status due to incorrect error handling [Test case] connect to a cdma device without an extra AT channel (Eg. Samsung brightside phone) and modemmanager will terminate the connection [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
https://bugzilla.redhat.com/show_bug.cgi?id=1652274 is a duplicate ** Bug watch added: Red Hat Bugzilla #1652274 https://bugzilla.redhat.com/show_bug.cgi?id=1652274 ** Also affects: xorg (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1652274 Importance: Unknown Status: Unknown -- 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/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc Status in xorg package in Ubuntu: New Status in xorg package in Fedora: Unknown Bug description: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1837081/+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 1837081] [NEW] xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
Public bug reported: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ubuntu -- 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/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc Status in xorg package in Ubuntu: New Bug description: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz:
[Desktop-packages] [Bug 1766192] Re: [snap] cannot save file under $HOME
Just installed LibreOffice 6.3.0.1 with no change. -- 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/1766192 Title: [snap] cannot save file under $HOME Status in snapd: Triaged Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: (this was initially reported on the forum: https://forum.snapcraft.io/t/libreoffice-6-0-3-not-so-stable/5032) When trying to save a file under $HOME (not a subdirectory), the user is presented with an error dialog: --- Error --- Error saving the document Untitled 1: Object not accessible. The object cannot be accessed due to insufficient user rights. [OK] This is because libreoffice tries to create a lock file of the form: "$HOME/.~lock.Untitled 1.odt", and the home interface doesn't allow writing hidden files (those with a filename that starts with a dot) under $HOME. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)" DESKTOP_SESSION=ubuntu GTK_MODULES=gail:atk-bridge HOME=/home/osomon/snap/libreoffice/59 LANG=fr_FR.UTF-8 LC_MONETARY=fr_FR.UTF-8 LC_NAME=fr_FR.UTF-8 LC_NUMERIC=fr_FR.UTF-8 LC_TIME=fr_FR.UTF-8 LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu::/snap/libreoffice/59/lib:/snap/libreoffice/59/usr/lib:/snap/libreoffice/59/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa PATH=/snap/libreoffice/59/usr/sbin:/snap/libreoffice/59/usr/bin:/snap/libreoffice/59/sbin:/snap/libreoffice/59/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games SNAP=/snap/libreoffice/59 SNAP_ARCH=amd64 SNAP_COMMON=/var/snap/libreoffice/common SNAP_DATA=/var/snap/libreoffice/59 SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void SNAP_NAME=libreoffice SNAP_REEXEC= SNAP_REVISION=59 SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common SNAP_USER_DATA=/home/osomon/snap/libreoffice/59 SNAP_VERSION=6.0.3.2 TEMPDIR=/tmp TMPDIR=/run/user/1000/snap.libreoffice XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg XDG_CURRENT_DESKTOP=ubuntu:GNOME XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice XDG_SESSION_DESKTOP=ubuntu XDG_SESSION_TYPE=x11 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1766192/+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 1837068] Re: libssh armhf autopkgtest failure on valgrind unhandled instruction: 0xEBAD 0x1CCA
It's unclear to me why that only started to me a problem but if it can be fixed from the valgrind side that would make sense, could foundations look if that patch makes sense/could be applied to the Ubuntu package maybe? ** Also affects: libssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1837068 Title: libssh armhf autopkgtest failure on valgrind unhandled instruction: 0xEBAD 0x1CCA Status in libssh package in Ubuntu: New Status in valgrind package in Ubuntu: New Bug description: The libssh 0.9 armhf eoan tests are failing http://autopkgtest.ubuntu.com/packages/libs/libssh/eoan/armhf The error is 'disInstr(thumb): unhandled instruction: 0xEBAD 0x1CCA ==1127== valgrind: Unrecognised instruction at address 0x4b9c93d. ==1127==at 0x4B9C93C: ??? (in /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.1)' Looking upstream to valgrind bug there is one matching with an (unreviewed) patch https://bugs.kde.org/show_bug.cgi?id=385262 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1837068/+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 1834866] Re: Stop building and remove firefox-globalmenu
** Changed in: firefox (Ubuntu) Status: In Progress => Fix Committed -- 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/1834866 Title: Stop building and remove firefox-globalmenu Status in firefox package in Ubuntu: Fix Committed Bug description: firefox-globalmenu is an empty transitional package that was needed on Ubuntu 14.04. Now that trusty is EOL, it can be safely removed (see https://bazaar.launchpad.net/~mozillateam/firefox/firefox- trunk.head/view/head:/debian/control.in#L132). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1834866/+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 1834866] Re: Stop building and remove firefox-globalmenu
** Branch linked: lp:~mozillateam/firefox/firefox-beta.eoan -- 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/1834866 Title: Stop building and remove firefox-globalmenu Status in firefox package in Ubuntu: Fix Committed Bug description: firefox-globalmenu is an empty transitional package that was needed on Ubuntu 14.04. Now that trusty is EOL, it can be safely removed (see https://bazaar.launchpad.net/~mozillateam/firefox/firefox- trunk.head/view/head:/debian/control.in#L132). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1834866/+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 1834866] Re: Stop building and remove firefox-globalmenu
** Changed in: firefox (Ubuntu) Status: Triaged => In Progress -- 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/1834866 Title: Stop building and remove firefox-globalmenu Status in firefox package in Ubuntu: Fix Committed Bug description: firefox-globalmenu is an empty transitional package that was needed on Ubuntu 14.04. Now that trusty is EOL, it can be safely removed (see https://bazaar.launchpad.net/~mozillateam/firefox/firefox- trunk.head/view/head:/debian/control.in#L132). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1834866/+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 1834866] Re: Stop building and remove firefox-globalmenu
** Branch linked: lp:~mozillateam/firefox/firefox-beta.bionic ** Branch linked: lp:firefox/beta -- 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/1834866 Title: Stop building and remove firefox-globalmenu Status in firefox package in Ubuntu: Fix Committed Bug description: firefox-globalmenu is an empty transitional package that was needed on Ubuntu 14.04. Now that trusty is EOL, it can be safely removed (see https://bazaar.launchpad.net/~mozillateam/firefox/firefox- trunk.head/view/head:/debian/control.in#L132). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1834866/+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 1834866] Re: Stop building and remove firefox-globalmenu
** Branch linked: lp:~mozillateam/firefox/firefox-beta.xenial -- 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/1834866 Title: Stop building and remove firefox-globalmenu Status in firefox package in Ubuntu: In Progress Bug description: firefox-globalmenu is an empty transitional package that was needed on Ubuntu 14.04. Now that trusty is EOL, it can be safely removed (see https://bazaar.launchpad.net/~mozillateam/firefox/firefox- trunk.head/view/head:/debian/control.in#L132). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1834866/+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 1824408] Re: With client side decoration, Firefox preempts any middle click on title bar
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/1824408 Title: With client side decoration, Firefox preempts any middle click on title bar Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: New Bug description: Since recent versions, Firefox uses client-side decoration to draw its title bar. I have a mouse shortcut defined in gnome-tweaks that allows me to minimize windows on middle mouse button click on title bar This works well, except on new Firefox, where it will open a new tab... I didn't find the way to disable this behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0.3+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 3795 F pulseaudio /dev/snd/pcmC1D0c: franck 3795 F...m pulseaudio /dev/snd/controlC0: franck 3795 F pulseaudio /dev/snd/pcmC0D7p: franck 3795 F...m pulseaudio BuildID: 20190410124846 Channel: Unavailable CurrentDesktop: GNOME Date: Thu Apr 11 20:28:43 2019 EcryptfsInUse: Yes 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) IpRoute: default via 10.0.0.1 dev enp0s25 proto dhcp metric 100 default via 10.0.0.1 dev wlp3s0 proto dhcp metric 600 10.0.0.0/24 dev enp0s25 proto kernel scope link src 10.0.0.14 metric 100 10.0.0.0/24 dev wlp3s0 proto kernel scope link src 10.0.0.246 metric 600 10.204.48.0/24 dev lxdbr0 proto kernel scope link src 10.204.48.1 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0.3/20190410124846 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) 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: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1824408/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
** Changed in: mesa (Ubuntu Bionic) Importance: Undecided => Critical -- 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/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 Status in mesa package in Ubuntu: Won't Fix Status in mesa source package in Bionic: In Progress Bug description: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04. ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ~# uname -a Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 i686 i686 GNU/Linux ~# lspci -nn -k -d ::0300 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90] Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Kernel driver in use: i915 Kernel modules: i915 mesa: 19.0.2-1ubuntu1.1~18.04.1 X crashes with message: i965: Failed to submit batchbuffer: Invalid argument The same issue was after updating mesa from 18.0 to 18.2: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172 I have tried the same fix and it works for me: https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
FWIW, I did not experience this issue until I changed the hardware platform. Old system: Intel Haswell i7-4790, nVidia 970 GTX, ASUS X97 Pro, 32GB RAM New system: AMD Ryzen 3700x, nVidia 2080 RTX, ASUS Crosshair Hero VIII, 64 GB RAM -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: I've had this happen a couple of times now since upgrading to 18.04: soon (perhaps within a minute) after logging in, Gnome session ends abruptly and I'm thrown back to the login screen. IIRC, in both instances this occurred on the first login after boot, so it does not reoccur on the subsequent re-login, and not on every login (very rarely in fact), and for now I have no better steps to reproduce this other than "boot, log in". Bug #1663839 (reported against 17.04) seems similar, as does bug #1731428 (reported against 17.10). journalctl output during the issue: Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 16 17:07:14 2018 InstallationDate: Installed on 2016-10-13 (550 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+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 1835622] Re: Cannot start desktop session with compositor enabled
** Changed in: xfwm4 (Ubuntu) Status: New => Invalid -- 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/1835622 Title: Cannot start desktop session with compositor enabled Status in Xfwm4: Invalid Status in mesa package in Ubuntu: New Status in xfwm4 package in Ubuntu: Invalid Bug description: I cannot login to the Xfce desktop session anymore. in ~/.xsession- errors there's the message: xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285: intel_miptree_match_image: Assertion `image->TexObject->Target == mt->target' failed. Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0. I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA with xfwm4 4.13.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+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 1766192] Re: [snap] cannot save file under $HOME
Hi Ulrich-Lorenz, no regression - the root issue has not yet been resolved. -- 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/1766192 Title: [snap] cannot save file under $HOME Status in snapd: Triaged Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: (this was initially reported on the forum: https://forum.snapcraft.io/t/libreoffice-6-0-3-not-so-stable/5032) When trying to save a file under $HOME (not a subdirectory), the user is presented with an error dialog: --- Error --- Error saving the document Untitled 1: Object not accessible. The object cannot be accessed due to insufficient user rights. [OK] This is because libreoffice tries to create a lock file of the form: "$HOME/.~lock.Untitled 1.odt", and the home interface doesn't allow writing hidden files (those with a filename that starts with a dot) under $HOME. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)" DESKTOP_SESSION=ubuntu GTK_MODULES=gail:atk-bridge HOME=/home/osomon/snap/libreoffice/59 LANG=fr_FR.UTF-8 LC_MONETARY=fr_FR.UTF-8 LC_NAME=fr_FR.UTF-8 LC_NUMERIC=fr_FR.UTF-8 LC_TIME=fr_FR.UTF-8 LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu::/snap/libreoffice/59/lib:/snap/libreoffice/59/usr/lib:/snap/libreoffice/59/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa PATH=/snap/libreoffice/59/usr/sbin:/snap/libreoffice/59/usr/bin:/snap/libreoffice/59/sbin:/snap/libreoffice/59/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games SNAP=/snap/libreoffice/59 SNAP_ARCH=amd64 SNAP_COMMON=/var/snap/libreoffice/common SNAP_DATA=/var/snap/libreoffice/59 SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void SNAP_NAME=libreoffice SNAP_REEXEC= SNAP_REVISION=59 SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common SNAP_USER_DATA=/home/osomon/snap/libreoffice/59 SNAP_VERSION=6.0.3.2 TEMPDIR=/tmp TMPDIR=/run/user/1000/snap.libreoffice XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg XDG_CURRENT_DESKTOP=ubuntu:GNOME XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice XDG_SESSION_DESKTOP=ubuntu XDG_SESSION_TYPE=x11 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1766192/+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 726439] Re: Search for document returns an Unknown error: 'URI xref:search=' could not be parsed
Still exists in Eoan. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/726439 Title: Search for document returns an Unknown error: 'URI xref:search=' could not be parsed Status in Yelp: Expired Status in yelp package in Ubuntu: Confirmed Bug description: Binary package hint: yelp TEST CASE: 1. Launch Yelp 2. Select the menu 'Go / All Documents" 2. Enter some text (e.g nautilus) in the address bar 3. Hit Enter Result: The following error is displayed: """ Unknown Error The URI ‘xref:search=nautilus’ could not be parsed. """ Expected Results: List of documents matching the search list is returned ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: yelp 2.91.90-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic i686 Architecture: i386 Date: Mon Feb 28 11:01:37 2011 EcryptfsInUse: Yes ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: yelp To manage notifications about this bug go to: https://bugs.launchpad.net/yelp/+bug/726439/+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 1824408] Re: With client side decoration, Firefox preempts any middle click on title bar
I opened a bug upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1567176 ** Bug watch added: Mozilla Bugzilla #1567176 https://bugzilla.mozilla.org/show_bug.cgi?id=1567176 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1567176 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/1824408 Title: With client side decoration, Firefox preempts any middle click on title bar Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: New Bug description: Since recent versions, Firefox uses client-side decoration to draw its title bar. I have a mouse shortcut defined in gnome-tweaks that allows me to minimize windows on middle mouse button click on title bar This works well, except on new Firefox, where it will open a new tab... I didn't find the way to disable this behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0.3+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 3795 F pulseaudio /dev/snd/pcmC1D0c: franck 3795 F...m pulseaudio /dev/snd/controlC0: franck 3795 F pulseaudio /dev/snd/pcmC0D7p: franck 3795 F...m pulseaudio BuildID: 20190410124846 Channel: Unavailable CurrentDesktop: GNOME Date: Thu Apr 11 20:28:43 2019 EcryptfsInUse: Yes 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) IpRoute: default via 10.0.0.1 dev enp0s25 proto dhcp metric 100 default via 10.0.0.1 dev wlp3s0 proto dhcp metric 600 10.0.0.0/24 dev enp0s25 proto kernel scope link src 10.0.0.14 metric 100 10.0.0.0/24 dev wlp3s0 proto kernel scope link src 10.0.0.246 metric 600 10.204.48.0/24 dev lxdbr0 proto kernel scope link src 10.204.48.1 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0.3/20190410124846 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) 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: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1824408/+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 1835622] Re: Cannot start desktop session with compositor enabled
please test ppa:ubuntu-x-swat/updates seems to be a duplicate of bug 1836721 -- 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/1835622 Title: Cannot start desktop session with compositor enabled Status in Xfwm4: Invalid Status in mesa package in Ubuntu: New Status in xfwm4 package in Ubuntu: New Bug description: I cannot login to the Xfce desktop session anymore. in ~/.xsession- errors there's the message: xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285: intel_miptree_match_image: Assertion `image->TexObject->Target == mt->target' failed. Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0. I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA with xfwm4 4.13.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+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 1835622] Re: Cannot start desktop session with compositor enabled
well, perhaps not a dupe but would be nice to know if the new upstream bugfix version helps -- 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/1835622 Title: Cannot start desktop session with compositor enabled Status in Xfwm4: Invalid Status in mesa package in Ubuntu: New Status in xfwm4 package in Ubuntu: New Bug description: I cannot login to the Xfce desktop session anymore. in ~/.xsession- errors there's the message: xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285: intel_miptree_match_image: Assertion `image->TexObject->Target == mt->target' failed. Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0. I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA with xfwm4 4.13.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+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 1836641] Re: 18.04 firefox - broken for xml display
This is an unfortunate side effect of improved security, see
https://www.mozilla.org/en-US/firefox/68.0/releasenotes/#fixed ("Local
files can no longer access other files in the same directory.").
As a workaround, try changing the value of the
'privacy.file_unique_origin' preference to 'false' in about:config.
Please note that this is unsafe, and should be used only for testing
purposes, and reverted to the default value afterwards.
** Changed in: firefox (Ubuntu)
Status: New => Invalid
--
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/1836641
Title:
18.04 firefox - broken for xml display
Status in firefox package in Ubuntu:
Invalid
Bug description:
I have some files on my system that I browse with firefox.
file:///some/folder/data.xml
And data.xml is formatted using an xsl stylesheet.
This worked fine until this weekend. Now, I just see a big blob of
unformatted text when I visit data.xml.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 68.0+build3-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BuildID: 20190706110151
Channel: Unavailable
CurrentDesktop: GNOME
Date: Mon Jul 15 15:44:31 2019
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IpRoute:
default via 192.168.50.1 dev eth2 proto dhcp metric 100
169.254.0.0/16 dev eth2 scope link metric 1000
192.168.50.0/24 dev eth2 proto kernel scope link src 192.168.50.100 metric
100
Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so
(adobe-flashplugin)
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:1141
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=68.0/20190706110151 (In use)
RelatedPackageVersions: adobe-flashplugin 1:20190709.1-0ubuntu0.18.04.1
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1707
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1836641/+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 1766192] Re: [snap] cannot save file under $HOME
@audiomobster, the root issue of write access to $HOME has not yet been resolved. The snapd team is aware of this, but it is a complex issue whose solution requires careful consideration. -- 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/1766192 Title: [snap] cannot save file under $HOME Status in snapd: Triaged Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: (this was initially reported on the forum: https://forum.snapcraft.io/t/libreoffice-6-0-3-not-so-stable/5032) When trying to save a file under $HOME (not a subdirectory), the user is presented with an error dialog: --- Error --- Error saving the document Untitled 1: Object not accessible. The object cannot be accessed due to insufficient user rights. [OK] This is because libreoffice tries to create a lock file of the form: "$HOME/.~lock.Untitled 1.odt", and the home interface doesn't allow writing hidden files (those with a filename that starts with a dot) under $HOME. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)" DESKTOP_SESSION=ubuntu GTK_MODULES=gail:atk-bridge HOME=/home/osomon/snap/libreoffice/59 LANG=fr_FR.UTF-8 LC_MONETARY=fr_FR.UTF-8 LC_NAME=fr_FR.UTF-8 LC_NUMERIC=fr_FR.UTF-8 LC_TIME=fr_FR.UTF-8 LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu::/snap/libreoffice/59/lib:/snap/libreoffice/59/usr/lib:/snap/libreoffice/59/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa PATH=/snap/libreoffice/59/usr/sbin:/snap/libreoffice/59/usr/bin:/snap/libreoffice/59/sbin:/snap/libreoffice/59/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games SNAP=/snap/libreoffice/59 SNAP_ARCH=amd64 SNAP_COMMON=/var/snap/libreoffice/common SNAP_DATA=/var/snap/libreoffice/59 SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void SNAP_NAME=libreoffice SNAP_REEXEC= SNAP_REVISION=59 SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common SNAP_USER_DATA=/home/osomon/snap/libreoffice/59 SNAP_VERSION=6.0.3.2 TEMPDIR=/tmp TMPDIR=/run/user/1000/snap.libreoffice XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg XDG_CURRENT_DESKTOP=ubuntu:GNOME XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice XDG_SESSION_DESKTOP=ubuntu XDG_SESSION_TYPE=x11 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1766192/+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 1760849] Re: Login screen appears on only one monitor and it's not the one I want
In addition, for me, install lightdm solve the problem. Now, I can see login screen on both monitors :) -- 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/1760849 Title: Login screen appears on only one monitor and it's not the one I want Status in gdm: New Status in gdm3 package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Bug description: Upstream bugs: https://gitlab.gnome.org/GNOME/gdm/issues/168 https://gitlab.gnome.org/GNOME/gdm/issues/183 https://gitlab.gnome.org/GNOME/gdm/issues/195 https://gitlab.gnome.org/GNOME/gdm/issues/319 https://gitlab.gnome.org/GNOME/gdm/issues/372 The Ubuntu login screen is tiled on all displays, not mirrored, making it nearly impossible to login when using an external monitor if the laptop screen is not visible. There appears to be no available control to alter the display settings of the login screen. Prior to bionic, the controls followed the mouse onto different displays so you could login by giving the mouse a swipe to the right to get the controls to appear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 22:13:53 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1760849/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Have the same issue in Ubuntu 18.04.2 LTS. In pavucontrol or in blueman-applet: If select A2DP sound works; If select HSP/HFP sound/mic do not work. bluetoothctl output: Name: Jabra Elite 65t Alias: Jabra Elite 65t Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (-deca-fade-deca-deafdecacaff) UUID: Serial Port (1101--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: bluetooth:v0067p247Ed020E -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 1760849] Re: Login screen appears on only one monitor and it's not the one I want
Are there some solution for it? -- 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/1760849 Title: Login screen appears on only one monitor and it's not the one I want Status in gdm: New Status in gdm3 package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Bug description: Upstream bugs: https://gitlab.gnome.org/GNOME/gdm/issues/168 https://gitlab.gnome.org/GNOME/gdm/issues/183 https://gitlab.gnome.org/GNOME/gdm/issues/195 https://gitlab.gnome.org/GNOME/gdm/issues/319 https://gitlab.gnome.org/GNOME/gdm/issues/372 The Ubuntu login screen is tiled on all displays, not mirrored, making it nearly impossible to login when using an external monitor if the laptop screen is not visible. There appears to be no available control to alter the display settings of the login screen. Prior to bionic, the controls followed the mouse onto different displays so you could login by giving the mouse a swipe to the right to get the controls to appear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 22:13:53 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1760849/+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 1836659] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox again
I am not seeing the problem you describe in an up-to-date 18.04.2 VM, with the same versions of firefox, gnome-shell and ibus. Is this happening for all password fields on all web pages? If not, can you share a link to a page that exhibits the problem? What's the default value for GTK_IM_MODULE in your environment? ** 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/1836659 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox again Status in firefox package in Ubuntu: Incomplete Bug description: On an uptodate Ubuntu 18.04.2 LTS system I am observing the same symptoms as in bug https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 When I focus a password field in Firefox, it starts focusing and unfocusing rapidly, making it difficult to type passwords. Also, CPU usage goes up with the 4 processes eating most: %Cpu(s): 25,3 us, 11,0 sy, 0,0 ni, 63,5 id Xorg 60% gnome-flashback 21% firefox 20% ibus-daemon 4% Launching Firefox with GTK_IM_MODULE=xim firefox makes it go away. This started several (~7) days ago. $ apt list gnome-shell ibus firefox Listing... Done firefox/bionic-updates,bionic-security,now 68.0+build3-0ubuntu0.18.04.1 amd64 [installed] gnome-shell/bionic-updates,now 3.28.4-0ubuntu18.04.1 amd64 [installed] ibus/bionic,now 1.5.17-3ubuntu4 amd64 [installed] $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1836659/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
cool, the fix is on the SRU queue now, waiting for review -- 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/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 Status in mesa package in Ubuntu: Won't Fix Status in mesa source package in Bionic: In Progress Bug description: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04. ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ~# uname -a Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 i686 i686 GNU/Linux ~# lspci -nn -k -d ::0300 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90] Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Kernel driver in use: i915 Kernel modules: i915 mesa: 19.0.2-1ubuntu1.1~18.04.1 X crashes with message: i965: Failed to submit batchbuffer: Invalid argument The same issue was after updating mesa from 18.0 to 18.2: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172 I have tried the same fix and it works for me: https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1836804] Re: Unable to locate mail spool file.
Does this help? https://support.mozilla.org/en-US/questions/1157285 ** Changed in: thunderbird (Ubuntu) Status: New => Incomplete -- 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/1836804 Title: Unable to locate mail spool file. Status in thunderbird package in Ubuntu: Incomplete Bug description: If i launch Thunderbird I will get this error ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:60.8.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: artem 1115 F pulseaudio BuildID: 20190705213317 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Jul 16 23:31:05 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-07-14 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190712) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.104 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Prefs: extensions.lastAppVersion: "60.8.0" (prefs.js) network.cookie.prefsMigrated: true (prefs.js) network.predictor.cleaned-up: true (prefs.js) places.history.expiration.transient_current_max_pages: 104858 (prefs.js) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705213317 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832E dmi.board.vendor: HP dmi.board.version: 26.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd05/17/2018:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G6 Notebook PC dmi.product.sku: 3DN65ES#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1836804/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
I have just updated from ppa:ubuntu-x-swat/updates, now everything is fine on i386 Ubuntu 18.04 ~# apt-cache policy libgl1-mesa-glx libgl1-mesa-glx: Installed: 19.0.8-0ubuntu0~18.04.1 Candidate: 19.0.8-0ubuntu0~18.04.1 Version table: *** 19.0.8-0ubuntu0~18.04.1 500 500 http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status -- 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/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 Status in mesa package in Ubuntu: Won't Fix Status in mesa source package in Bionic: In Progress Bug description: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04. ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ~# uname -a Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 i686 i686 GNU/Linux ~# lspci -nn -k -d ::0300 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90] Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Kernel driver in use: i915 Kernel modules: i915 mesa: 19.0.2-1ubuntu1.1~18.04.1 X crashes with message: i965: Failed to submit batchbuffer: Invalid argument The same issue was after updating mesa from 18.0 to 18.2: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172 I have tried the same fix and it works for me: https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1754671] Re: Full-tunnel VPN DNS leakage regression
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu Xenial) Status: New => Confirmed -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Won't Fix Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1716654] Re: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound
Exactly the same issue on 18.04. Why was this closed? -- 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/1716654 Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Have checked under windows (same computer in dual-boot & same headset), and the sound is crystal clear, so 99% sure this is not a hardware problem. Motherboard is ASUS Crosshair Hero 6. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: paul 2587 F pulseaudio /dev/snd/controlC0: paul 2587 F pulseaudio /dev/snd/controlC1: paul 2587 F pulseaudio /dev/snd/controlC2: paul 2587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 11:48:05 2017 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic successful Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx: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 mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+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 1766192] Re: [snap] cannot save file under $HOME
I can confirm this with 19.04 (Disco Dingo) and libreoffice 6.2.5.2 latest updates. "Document could not be locked". Is this regression? -- 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/1766192 Title: [snap] cannot save file under $HOME Status in snapd: Triaged Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: (this was initially reported on the forum: https://forum.snapcraft.io/t/libreoffice-6-0-3-not-so-stable/5032) When trying to save a file under $HOME (not a subdirectory), the user is presented with an error dialog: --- Error --- Error saving the document Untitled 1: Object not accessible. The object cannot be accessed due to insufficient user rights. [OK] This is because libreoffice tries to create a lock file of the form: "$HOME/.~lock.Untitled 1.odt", and the home interface doesn't allow writing hidden files (those with a filename that starts with a dot) under $HOME. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)" DESKTOP_SESSION=ubuntu GTK_MODULES=gail:atk-bridge HOME=/home/osomon/snap/libreoffice/59 LANG=fr_FR.UTF-8 LC_MONETARY=fr_FR.UTF-8 LC_NAME=fr_FR.UTF-8 LC_NUMERIC=fr_FR.UTF-8 LC_TIME=fr_FR.UTF-8 LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu::/snap/libreoffice/59/lib:/snap/libreoffice/59/usr/lib:/snap/libreoffice/59/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa PATH=/snap/libreoffice/59/usr/sbin:/snap/libreoffice/59/usr/bin:/snap/libreoffice/59/sbin:/snap/libreoffice/59/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games SNAP=/snap/libreoffice/59 SNAP_ARCH=amd64 SNAP_COMMON=/var/snap/libreoffice/common SNAP_DATA=/var/snap/libreoffice/59 SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void SNAP_NAME=libreoffice SNAP_REEXEC= SNAP_REVISION=59 SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common SNAP_USER_DATA=/home/osomon/snap/libreoffice/59 SNAP_VERSION=6.0.3.2 TEMPDIR=/tmp TMPDIR=/run/user/1000/snap.libreoffice XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg XDG_CURRENT_DESKTOP=ubuntu:GNOME XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice XDG_SESSION_DESKTOP=ubuntu XDG_SESSION_TYPE=x11 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1766192/+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 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)
excellent, that version is on the SRU queue already, waiting for review
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
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/1836772
Title:
Xorg crash on 3d-enabled virgl (Haswell host)
Status in mesa package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
Invalid
Bug description:
I am running a KVM virtual machine with 3D acceleration (virgl). The
host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
session started crashing just after the login. In xorg logs, I see
this:
[15.338] (WW) modeset(0): Page flip failed: Invalid argument
[15.338] (EE) modeset(0): present flip failed
[15.397] (WW) modeset(0): Page flip failed: Invalid argument
[15.397] (EE) modeset(0): present flip failed
[15.418] (WW) modeset(0): Page flip failed: Invalid argument
[15.419] (EE) modeset(0): present flip failed
[15.440] (WW) modeset(0): Page flip failed: Invalid argument
[15.440] (EE) modeset(0): present flip failed
[15.460] (WW) modeset(0): Page flip failed: Invalid argument
[15.460] (EE) modeset(0): present flip failed
[15.975] (WW) modeset(0): Page flip failed: Invalid argument
[15.976] (EE) modeset(0): present flip failed
[16.039] (WW) modeset(0): Page flip failed: Invalid argument
[16.040] (EE) modeset(0): present flip failed
[16.064] (WW) modeset(0): Page flip failed: Invalid argument
[16.064] (EE) modeset(0): present flip failed
[16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
0:11(2): error: value of type vec4 cannot be assigned to variable of type
error
0:12(2): error: `color1' undeclared
0:12(2): error: value of type vec4 cannot be assigned to variable of type
error
[16.096] Program source:
#ifdef GL_ES
precision mediump float;
#endif
#define ATLAS_DIM_INV 0.0009765625
varying vec2 glyph_pos;
uniform vec4 fg;
uniform sampler2D atlas;
void main() {
vec4 mask = texture2D(atlas, glyph_pos);
vec4 source = fg;
color0 = source * mask;
color1 = source.a * mask;
}
[16.096] (EE)
Fatal server error:
[16.096] (EE) GLSL compile failure
Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
18.0.0~rc5-1ubuntu1 helps.
Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.
On the host, the GPU is Intel Haswell:
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon
E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
[8086:0412] (rev 06)
The CPU is Intel(R) Core(TM) i7-4770S CPU.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 16 20:52:03 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.12.0-20181126_142135-anatol
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-4.0
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-4.0
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1836881] Re: gnome-shell freeze
Hello Daniel, thank you for the help. The freezing has just happened again, I enter tty, used the command ps -A | grep gnome , and I believe that the ID is the gnome-shell associated to the tty2 because ctrl+alt+f2 is my interface shortcut. I ran the apport command and with the ID and it give me some options, on of which is to send the report. There was no option to generate a link. I sent the report by pressing s but I am not sure where the report when to and how you could locate it. Is there another way to make the report available to you? -- 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/1836881 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: My gnome session freezes, mouse works fine but cannot start applications. I am able to enter one of the tty terminals and kill the session. This happens a few times a day and started a week ago probably. Douglas ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 12:29:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 4.15.0-52-generic, x86_64: installed nvidia, 418.56, 4.15.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1208] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1207] InstallationDate: Installed on 2018-01-13 (550 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 002: ID 0461:4e81 Primax Electronics, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator PH317-51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=455417ef-94fe-4ab8-97b7-0b992c951267 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienna_KLS dmi.board.vendor: KBL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnPredatorPH317-51:pvrV1.05:rvnKBL:rnSienna_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH317-51 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 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/ubuntu/+source/gnome-shell/+bug/1836881/+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 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)
It works.
--
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/1836772
Title:
Xorg crash on 3d-enabled virgl (Haswell host)
Status in mesa package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
New
Bug description:
I am running a KVM virtual machine with 3D acceleration (virgl). The
host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
session started crashing just after the login. In xorg logs, I see
this:
[15.338] (WW) modeset(0): Page flip failed: Invalid argument
[15.338] (EE) modeset(0): present flip failed
[15.397] (WW) modeset(0): Page flip failed: Invalid argument
[15.397] (EE) modeset(0): present flip failed
[15.418] (WW) modeset(0): Page flip failed: Invalid argument
[15.419] (EE) modeset(0): present flip failed
[15.440] (WW) modeset(0): Page flip failed: Invalid argument
[15.440] (EE) modeset(0): present flip failed
[15.460] (WW) modeset(0): Page flip failed: Invalid argument
[15.460] (EE) modeset(0): present flip failed
[15.975] (WW) modeset(0): Page flip failed: Invalid argument
[15.976] (EE) modeset(0): present flip failed
[16.039] (WW) modeset(0): Page flip failed: Invalid argument
[16.040] (EE) modeset(0): present flip failed
[16.064] (WW) modeset(0): Page flip failed: Invalid argument
[16.064] (EE) modeset(0): present flip failed
[16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
0:11(2): error: value of type vec4 cannot be assigned to variable of type
error
0:12(2): error: `color1' undeclared
0:12(2): error: value of type vec4 cannot be assigned to variable of type
error
[16.096] Program source:
#ifdef GL_ES
precision mediump float;
#endif
#define ATLAS_DIM_INV 0.0009765625
varying vec2 glyph_pos;
uniform vec4 fg;
uniform sampler2D atlas;
void main() {
vec4 mask = texture2D(atlas, glyph_pos);
vec4 source = fg;
color0 = source * mask;
color1 = source.a * mask;
}
[16.096] (EE)
Fatal server error:
[16.096] (EE) GLSL compile failure
Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
18.0.0~rc5-1ubuntu1 helps.
Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.
On the host, the GPU is Intel Haswell:
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon
E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
[8086:0412] (rev 06)
The CPU is Intel(R) Core(TM) i7-4770S CPU.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 16 20:52:03 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.12.0-20181126_142135-anatol
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-4.0
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-4.0
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
[Desktop-packages] [Bug 1835650] Re: firefox fails to open private sessions from bash
You might want to file an upstream bug at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox to request
the old behaviour back, or at least ask for a console warning when using
the "-private" flag together with a URL, or when there's already a
running instance.
If you do please link it here, for future reference. 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/1835650
Title:
firefox fails to open private sessions from bash
Status in firefox package in Ubuntu:
Invalid
Bug description:
running
% firefox -private URL
or
% firefox -private-toggle URL
from a cli used to start firefox in private mode. This does not work
(in my setup) anymore.
[ctrl]-[shift]-p and "new private window" from the file menu also does
not always open private windows, anymore.
I'm wondering if this is a security bug (it clearly is a privacy bug)..
1)
$ lsb_release -rd
Description: Ubuntu 19.04
Release: 19.04
2)
$ apt-cache policy firefox
firefox:
Installed: 67.0.4+build1-0ubuntu0.19.04.1
Candidate: 67.0.4+build1-0ubuntu0.19.04.1
Version table:
*** 67.0.4+build1-0ubuntu0.19.04.1 500
500 http://de.archive.ubuntu.com/ubuntu disco-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu disco-security/main amd64
Packages
100 /var/lib/dpkg/status
66.0.3+build1-0ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu disco/main amd64 Packages
3) What I expect to happen
Opening a private window from the command line typing
firefox -private URL
should open the URL in a private window
4) What happens instead
Upon the given command firefox opens the URL, but not in a private window and
leaves the URL in the history of the browser.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: firefox 67.0.4+build1-0ubuntu0.19.04.1
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: thorsten 2262 F pulseaudio
BuildID: 20190620151128
Channel: Unavailable
CurrentDesktop: MATE
Date: Sun Jul 7 13:22:56 2019
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-04-10 (87 days ago)
InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
IpRoute:
default via 192.168.178.1 dev wlp61s0 proto dhcp metric 600
169.254.0.0/16 dev wlp61s0 scope link metric 1000
192.168.178.0/24 dev wlp61s0 proto kernel scope link src 192.168.178.24
metric 600
MostRecentCrashID: bp-86cfd7c5-fc1a-482b-b67f-a018b1180516
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:1151
PrefSources:
/usr/lib/firefox/defaults/pref/all-ubuntumate.js
prefs.js
Profiles: Profile0 (Default) - LastVersion=67.0.4/20190620151128 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/13/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET49W (1.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S29W00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L8S29W00:pvrThinkPadT480s:rvnLENOVO:rn20L8S29W00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S29W00
dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1835650/+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 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
Thanks for the feedback. I'm closing this bug accordingly. Note that "Delete this seriously flawed extension!" (on https://extensions.gnome.org/extension/937/laine/ and https://gitlab.com/jhoran/Laine/issues/52) is not usually considered constructive feedback. I'm sure the developers of that extension will be more than happy to investigate and fix the problem, now that it has been reported to them. Wording the report in friendly terms wouldn't hurt. ** Bug watch added: gitlab.com/jhoran/Laine/issues #52 https://gitlab.com/jhoran/Laine/issues/52 ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- 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/1835623 Title: Google Chrome Linux version 75 freezes and then crashes when trying to play any video Status in chromium-browser package in Ubuntu: Invalid Bug description: (upstream bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=983203) Ubuntu 18.04 I expect Chrome to play videos. When I try to play any video on Google Chrome for Linux, any version of 75 or higher, Google Chrome freezes. Chrome 75 will allow sound but no video. All mouse clicks become unresponsive. Attempting to close Chrome after many mouse clicks causes Chrome to crash. Even worse it often also crashes Ubuntu 18.04. Google Chrome 74 or lower work without any problems playing videos. It is a Google Chrome Linux version 75 or higher problem. I cannot believe that neither Google or Ubuntu or any other Linux OS seem to completely ignore this extremely serious problem. I am forced to install Google Chrome 71 to fix video playback problem. I posted on Ubuntu ask, and show over 90 views but no comments. One answer confirms that he has the exact same problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: DistroRelease: Ubuntu 18.04 Env: 'None' 'None' InstallationDate: Installed on 2019-05-02 (66 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181019) Load-Avg-1min: 1.47 Load-Processes-Running-Percent: 0.1% MachineType: MSI MS-7641 NonfreeKernelModules: nvidia_modeset nvidia Package: chromium-browser 75.0.3770.90-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=7181ee96-0bd0-4b3c-9100-fa205ef6bd1d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-55-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm adm cdrom cdrom dip dip lpadmin lpadmin plugdev plugdev sambashare sambashare sudo sudo _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.1 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 760GMA-P34(FX) (MS-7641) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.1:bd04/20/2015:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7641 dmi.product.version: 5.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1835623/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
please test 19.0.8 from ppa:ubuntu-x-swat/updates once it has built -- 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/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 Status in mesa package in Ubuntu: Won't Fix Status in mesa source package in Bionic: In Progress Bug description: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04. ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ~# uname -a Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 i686 i686 GNU/Linux ~# lspci -nn -k -d ::0300 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90] Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Kernel driver in use: i915 Kernel modules: i915 mesa: 19.0.2-1ubuntu1.1~18.04.1 X crashes with message: i965: Failed to submit batchbuffer: Invalid argument The same issue was after updating mesa from 18.0 to 18.2: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172 I have tried the same fix and it works for me: https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1835922] Re: missing gl* symbols in version 19.0.2
please test 19.0.8 from ppa:ubuntu-x-swat/updates once it has built -- 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/1835922 Title: missing gl* symbols in version 19.0.2 Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: New Status in mesa source package in Disco: New Bug description: Linking with libosmesa6-dev version 19.0.2 will fail because all the gl* symbols are missing: ``` [100%] Linking CXX executable bin/minko-converter ../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o): In function `jas_stream_tmpfile': jas_stream.c:(.text+0x6fd): warning: the use of `tmpnam' is dangerous, better use `mkstemp' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::clear(unsigned int, float, float, float, float, float, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0xb3): undefined reference to `glDepthMask' OpenGLES2Context.cpp:(.text+0xd9): undefined reference to `glClearDepth' OpenGLES2Context.cpp:(.text+0xe7): undefined reference to `glClearColor' OpenGLES2Context.cpp:(.text+0xfc): undefined reference to `glClearStencil' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, unsigned int, int)': OpenGLES2Context.cpp:(.text+0x120): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, int)': OpenGLES2Context.cpp:(.text+0x153): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadVertexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x191): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadIndexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x1db): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x297): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x2aa): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x2b9): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteIndexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x332): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x345): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x354): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::setVertexBufferAt(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0x527): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x559): undefined reference to `glVertexAttribPointer' OpenGLES2Context.cpp:(.text+0x59a): undefined reference to `glDisableVertexAttribArray' OpenGLES2Context.cpp:(.text+0x61e): undefined reference to `glEnableVertexAttribArray' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::createVertexAttributeArray()': OpenGLES2Context.cpp:(.text+0x65f): undefined reference to `glGenVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexAttributeArray(unsigned int)': OpenGLES2Context.cpp:(.text+0x6b3): undefined reference to `glDeleteVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadCubeTextureData(unsigned int, minko::render::CubeTexture::Face, unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x6e4): undefined reference to `glBindTexture' OpenGLES2Context.cpp:(.text+0x736): undefined reference to `glTexImage2D' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadTexture2dData(unsigned int, unsigned int, unsigned int, unsigned int, void*)':
[Desktop-packages] [Bug 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)
please test 19.0.8 from ppa:ubuntu-x-swat/updates
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
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/1836772
Title:
Xorg crash on 3d-enabled virgl (Haswell host)
Status in mesa package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
New
Bug description:
I am running a KVM virtual machine with 3D acceleration (virgl). The
host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
session started crashing just after the login. In xorg logs, I see
this:
[15.338] (WW) modeset(0): Page flip failed: Invalid argument
[15.338] (EE) modeset(0): present flip failed
[15.397] (WW) modeset(0): Page flip failed: Invalid argument
[15.397] (EE) modeset(0): present flip failed
[15.418] (WW) modeset(0): Page flip failed: Invalid argument
[15.419] (EE) modeset(0): present flip failed
[15.440] (WW) modeset(0): Page flip failed: Invalid argument
[15.440] (EE) modeset(0): present flip failed
[15.460] (WW) modeset(0): Page flip failed: Invalid argument
[15.460] (EE) modeset(0): present flip failed
[15.975] (WW) modeset(0): Page flip failed: Invalid argument
[15.976] (EE) modeset(0): present flip failed
[16.039] (WW) modeset(0): Page flip failed: Invalid argument
[16.040] (EE) modeset(0): present flip failed
[16.064] (WW) modeset(0): Page flip failed: Invalid argument
[16.064] (EE) modeset(0): present flip failed
[16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
0:11(2): error: value of type vec4 cannot be assigned to variable of type
error
0:12(2): error: `color1' undeclared
0:12(2): error: value of type vec4 cannot be assigned to variable of type
error
[16.096] Program source:
#ifdef GL_ES
precision mediump float;
#endif
#define ATLAS_DIM_INV 0.0009765625
varying vec2 glyph_pos;
uniform vec4 fg;
uniform sampler2D atlas;
void main() {
vec4 mask = texture2D(atlas, glyph_pos);
vec4 source = fg;
color0 = source * mask;
color1 = source.a * mask;
}
[16.096] (EE)
Fatal server error:
[16.096] (EE) GLSL compile failure
Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
18.0.0~rc5-1ubuntu1 helps.
Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.
On the host, the GPU is Intel Haswell:
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon
E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
[8086:0412] (rev 06)
The CPU is Intel(R) Core(TM) i7-4770S CPU.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 16 20:52:03 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.12.0-20181126_142135-anatol
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-4.0
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-4.0
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Desktop-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
** Changed in: linux (Ubuntu Cosmic) Status: New => Won't Fix ** Summary changed: - Black screen on skylake after 18.0 => 18.2 update + [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa -- 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/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
okay, adding the revert again.. this should've been fixed in the kernel after 18.04.2 but that didn't happen since we don't support 32bit installs in newer releases, bionic is the only one that will get this ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu Bionic) Status: New => In Progress ** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix -- 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/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 Status in mesa package in Ubuntu: Won't Fix Status in mesa source package in Bionic: In Progress Bug description: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04. ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ~# uname -a Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 i686 i686 GNU/Linux ~# lspci -nn -k -d ::0300 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90] Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Kernel driver in use: i915 Kernel modules: i915 mesa: 19.0.2-1ubuntu1.1~18.04.1 X crashes with message: i965: Failed to submit batchbuffer: Invalid argument The same issue was after updating mesa from 18.0 to 18.2: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172 I have tried the same fix and it works for me: https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1835922] Re: missing gl* symbols in version 19.0.2
fixed upstream in 19.0.5 ** Bug watch added: freedesktop.org Bugzilla #109659 https://bugs.freedesktop.org/show_bug.cgi?id=109659 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=109659 Importance: Unknown Status: Unknown ** Also affects: mesa (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- 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/1835922 Title: missing gl* symbols in version 19.0.2 Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: New Status in mesa source package in Disco: New Bug description: Linking with libosmesa6-dev version 19.0.2 will fail because all the gl* symbols are missing: ``` [100%] Linking CXX executable bin/minko-converter ../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o): In function `jas_stream_tmpfile': jas_stream.c:(.text+0x6fd): warning: the use of `tmpnam' is dangerous, better use `mkstemp' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::clear(unsigned int, float, float, float, float, float, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0xb3): undefined reference to `glDepthMask' OpenGLES2Context.cpp:(.text+0xd9): undefined reference to `glClearDepth' OpenGLES2Context.cpp:(.text+0xe7): undefined reference to `glClearColor' OpenGLES2Context.cpp:(.text+0xfc): undefined reference to `glClearStencil' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, unsigned int, int)': OpenGLES2Context.cpp:(.text+0x120): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, int)': OpenGLES2Context.cpp:(.text+0x153): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadVertexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x191): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadIndexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x1db): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x297): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x2aa): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x2b9): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteIndexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x332): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x345): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x354): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::setVertexBufferAt(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0x527): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x559): undefined reference to `glVertexAttribPointer' OpenGLES2Context.cpp:(.text+0x59a): undefined reference to `glDisableVertexAttribArray' OpenGLES2Context.cpp:(.text+0x61e): undefined reference to `glEnableVertexAttribArray' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::createVertexAttributeArray()': OpenGLES2Context.cpp:(.text+0x65f): undefined reference to `glGenVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexAttributeArray(unsigned int)': OpenGLES2Context.cpp:(.text+0x6b3): undefined reference to `glDeleteVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadCubeTextureData(unsigned int, minko::render::CubeTexture::Face, unsigned int,
[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
> That's weird, do you understand why? The update was deleted so you should be > back to initial > situation, we had no change to the previous package build Other package changes? Certainly systemd-resolver although we don't use that (because of a previous VPN DNS leak problem) we use dnsmasq. My original thought was that it was the VPN config change that we'd made to cope with the new NM, but testing seems to show it isn't that. Now we have a failure mode which some people had *occasionally* reported before, where even VPN lookups which *must* go to the VPN, for the company domain, are not. This was just occasional before; now it seems to happen all the time. I haven't done a thorough investigation since just putting the updated NM back has been enough to fix it. -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Won't Fix Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+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
