[Desktop-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
** Bug watch added: Debian Bug tracker #931488 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931488 ** Changed in: jackd2 (Debian) Importance: Undecided => Unknown ** Changed in: jackd2 (Debian) Status: Confirmed => Unknown ** Changed in: jackd2 (Debian) Remote watch: None => Debian Bug tracker #931488 ** Bug watch removed: github.com/xbmc/xbmc/issues #16258 https://github.com/xbmc/xbmc/issues/16258 ** Changed in: jackd2 (Ubuntu) Importance: High => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: Confirmed Status in jackd2 package in Debian: Unknown Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+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 192065] Re: Images in mail marked as 'Junk' should not be displayed
[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/192065 Title: Images in mail marked as 'Junk' should not be displayed Status in thunderbird package in Ubuntu: Expired Bug description: Binary package hint: thunderbird This is actually a suggestion, not a bug. (But maybe its a bug :) ) When the thunderbird shows spam mail, it sometimes does not filter out all images. Would it be possible to configure the Thunderbird in such a way, that the images are not shown for mail that are considered tobe spam? This is important for me, since i have to recheck all the mail, to make shure that they are indeed spam. But some mail have inappropriate images, that i would not like to see. So, and option, that turns off imges would be great. Thanks Anton ProblemType: Bug Architecture: i386 Date: Fri Feb 15 11:02:22 2008 DistroRelease: Ubuntu 7.10 Package: mozilla-thunderbird 2.0.0.8~pre071022+nobinonly-0ubuntu0.7.10 PackageArchitecture: all SourcePackage: thunderbird Uname: Linux Notebook 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/192065/+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 806300] Re: Crash start Firefox
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/806300 Title: Crash start Firefox Status in firefox package in Ubuntu: Expired Bug description: $ FoxyProxy settingsDir: /home/caravena/.mozilla/firefox/5j0xtc7t.default/foxyproxy.xml (firefox-bin:7619): LIBDBUSMENU-GTK-CRITICAL **: dbusmenu_menuitem_property_set_shortcut: assertion `gtk_accelerator_valid(key, modifier)' failed (firefox-bin:7619): Gtk-CRITICAL **: IA__gtk_text_buffer_create_mark: assertion `GTK_IS_TEXT_BUFFER (buffer)' failed (firefox-bin:7619): Gtk-CRITICAL **: IA__gtk_text_buffer_create_mark: assertion `GTK_IS_TEXT_BUFFER (buffer)' failed (firefox-bin:7619): GLib-GObject-WARNING **: instance of invalid non- instantiatable type `' (firefox-bin:7619): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (firefox-bin:7619): GLib-GObject-WARNING **: instance of invalid non- instantiatable type `' (firefox-bin:7619): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (firefox-bin:7619): GLib-GObject-WARNING **: instance of invalid non- instantiatable type `' (firefox-bin:7619): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (firefox-bin:7619): Gtk-CRITICAL **: IA__gtk_text_buffer_get_paste_target_list: assertion `GTK_IS_TEXT_BUFFER (buffer)' failed (crashreporter:7714): Gtk-CRITICAL **: IA__gtk_text_buffer_create_mark: assertion `GTK_IS_TEXT_BUFFER (buffer)' failed (crashreporter:7714): Gtk-CRITICAL **: IA__gtk_text_buffer_create_mark: assertion `GTK_IS_TEXT_BUFFER (buffer)' failed (crashreporter:7714): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `' (crashreporter:7714): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (crashreporter:7714): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `' (crashreporter:7714): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (crashreporter:7714): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `' (crashreporter:7714): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (crashreporter:7714): Gtk-CRITICAL **: IA__gtk_text_buffer_get_paste_target_list: assertion `GTK_IS_TEXT_BUFFER (buffer)' failed ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: firefox 5.0+build1+nobinonly-0ubuntu3 Uname: Linux 3.0.0-0300rc6-generic x86_64 Architecture: amd64 Date: Tue Jul 5 23:54:15 2011 ExecutablePath: /usr/lib/firefox-5.0/crashreporter FirefoxPackages: firefox 5.0+build1+nobinonly-0ubuntu3 flashplugin-installer 10.3.181.34ubuntu1 adobe-flashplugin N/A icedtea-plugin 1.1-1ubuntu1 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1) ProcCmdline: /usr/lib/firefox-5.0/crashreporter /home/username/.mozilla/firefox/5j0xtc7t.default/minidumps/256394bf-75de-42ae-20136c9b-0a573792.dmp ProcEnviron: LANG=es_CL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f3f2e930043 : mov(%r12),%r12 PC (0x7f3f2e930043) ok source "(%r12)" (0x) not located in a known VMA region (needed readable region)! destination "%r12" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: firefox StacktraceTop: gtk_text_view_target_list_notify (buffer=, pspec=, data=0x7f3f2ffeb340) at /build/buildd/gtk+2.0-2.24.5/gtk/gtktextview.c:7634 IA__gtk_text_view_set_buffer (text_view=0x7f3f2ffeb340, buffer=0x7f3f2ff16140) at /build/buildd/gtk+2.0-2.24.5/gtk/gtktextview.c:1497 get_buffer (text_view=0x7f3f2ffeb340) at /build/buildd/gtk+2.0-2.24.5/gtk/gtktextview.c:1523 ?? () ?? () Title: crashreporter crashed with SIGSEGV in gtk_text_view_target_list_notify() 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/firefox/+bug/806300/+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 785585] Re: web page requires ActiveX.
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/785585 Title: web page requires ActiveX. Status in firefox package in Ubuntu: Expired Bug description: Binary package hint: firefox I realize that Active X is a security concern, however it would be helpfull if a more secure but compatible alternative was available, as one very usefull city mapping service requires active x for it's full potential to be utilized ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 4.0.1+build1+nobinonly-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Fri May 20 00:01:17 2011 EcryptfsInUse: Yes FirefoxPackages: firefox 4.0.1+build1+nobinonly-0ubuntu0.11.04.1 flashplugin-installer 10.2.159.1ubuntu1 adobe-flashplugin N/A icedtea-plugin 1.1~20110420-0ubuntu1 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: Upgraded to natty on 2011-04-29 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/785585/+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 1119700] Re: Crash in libglobalmenu.so while accessing GDocs
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1119700 Title: Crash in libglobalmenu.so while accessing GDocs Status in firefox package in Ubuntu: Expired Bug description: The firefox-globalmenu regularly (3 times in just over an hour) crashes Firefox while I'm trying to work in a Google Doc. This affects word processing docs and spreadsheets. The crashes are seemingly random - I get them while editing text, scrolling the page, or performing an operation like refreshing a table of contents within a document. Sample crash reports: https://crash-stats.mozilla.com/report/index/bp-4600c678-575d-4a12-af26-7ebe62130208 https://crash-stats.mozilla.com/report/index/bp-3c5752d1-af48-4abf-ab59-1e0052130208 https://crash-stats.mozilla.com/report/index/bp-24dfd44e-ef6e-42ae-a657-bec6e2130208 The signature in in Mozilla's crash DB is 'libglobalmenu.so@0xa772' This problem occurred in Firefox 18 on 12.10, and it remains in FF19 on 13.04 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: firefox 19.0~b5+build1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False ApportVersion: 2.8-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 2237 F pulseaudio BuildID: 20130206204007 Channel: Unavailable Date: Fri Feb 8 14:40:41 2013 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2010-09-17 (875 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) IpRoute: default via 192.168.3.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.3.0/24 dev wlan0 proto kernel scope link src 192.168.3.119 metric 9 MarkForUpload: True MostRecentCrashID: bp-4600c678-575d-4a12-af26-7ebe62130208 Plugins: iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Google Talk Plugin Video Accelerator - /opt/google/talkplugin/libnpgtpo3dautoplugin.so (google-talkplugin) Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so (google-talkplugin) Shockwave Flash - /usr/lib/mozilla/plugins/libflashplayer.so HP Virtual Rooms Plug-in - [HomeDir]/.mozilla/plugins/hpvirtualrooms-plugin.so PrefSources: prefs.js ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=19.0/20130206204007 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.98-0ubuntu3 google-talkplugin 3.10.2.0-1 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to raring on 2013-01-25 (14 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8: dmi.product.name: MacBookPro3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1119700/+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 1009194] Re: Tool tips do not comply with unity design
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1009194 Title: Tool tips do not comply with unity design Status in firefox package in Ubuntu: Expired Bug description: The tool tips look ugly in Ubuntu unity. It has a squared borders and opacity is 100% black. This is in contrast to overall unity settings which have smooth curved design for tool tips. I have attached the tool tip screen shots ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 12.0+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ram1766 F pulseaudio BuildID: 20120423122624 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 ALC888' Components : 'HDA:10ec0888,1565e601,0011' Controls : 47 Simple ctrls : 21 Channel: release Date: Wed Jun 6 01:30:02 2012 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) 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.2 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=12.0/20120423122624 (Running) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: TF7025-M2 dmi.board.vendor: BIOSTAR Group dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/16/2008:svnBIOSTARGroup:pnTF7025-M2:pvr5.0:rvnBIOSTARGroup:rnTF7025-M2:rvr1.0:cvnBIOSTARGroup:ct3:cvr: dmi.product.name: TF7025-M2 dmi.product.version: 5.0 dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1009194/+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 847365] Re: totem crashed with SIGSEGV
[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/847365 Title: totem crashed with SIGSEGV Status in totem package in Ubuntu: Expired Bug description: I tried to chance the attributes for the subtitles from the movie that was playing (mkv movie with srt subtitles). ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: totem 3.0.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 ApportVersion: 1.22.1-0ubuntu2 Architecture: amd64 Date: Sun Sep 11 22:28:24 2011 ExecutablePath: /usr/bin/totem InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcCmdline: totem /home/username/Videos/Wing\ commander.mkv SegvAnalysis: Segfault happened at: 0x7f309133c960:cmp0x8(%rdx),%rax PC (0x7f309133c960) ok source "0x8(%rdx)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem Stacktrace: #0 0x7f309133c960 in ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 No symbol table info available. Cannot access memory at address 0x7fff63b6a9a8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: totem crashed with SIGSEGV 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/847365/+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 1441940] Re: Chromium keyring save fail loops until memory exhausted and crashes
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1441940 Title: Chromium keyring save fail loops until memory exhausted and crashes Status in chromium-browser package in Ubuntu: Expired Bug description: This is collected on 15.04, but also occurred in 14.10 on the same laptop and another AMD custom built desktop. The browsers have three users signed in, but only one active window open and one blank tab. Removing the extensions seemed to have zero impact on the crash. This stall then crash behaviour makes Chromium and Chrome unusable as the program is killed within a few minutes of starting. The following is the terminal output of just launching chromium- browser and letting it sit. The same behaviour also occurs with Google-Chrome as well and does not disappear if the packages are installed and reinstalled. The observed behaviour is upon launch the system loads as expected while watching the system ram allocation the RAM grows then plateaus then while sitting there the window will gray and be non responsive. Then resume to a regular colour while the RAM will grow until the system memory is exhausted. $ chromium-browser ATTENTION: default value of option force_s3tc_enable overridden by environment. [12544:12544:0408/220540:ERROR:sandbox_linux.cc(325)] InitializeSandbox() called with multiple threads in process gpu-process [12509:12509:0408/220702:ERROR:extension_downloader.cc(696)] Invalid URL: '' for extension beebokabokkekbplnihckfiebkpfabom [12509:12509:0408/220702:ERROR:extension_downloader.cc(696)] Invalid URL: '' for extension ognampngfcbddbfemdapefohjiobgbdl [12509:12509:0408/220702:ERROR:extension_downloader.cc(696)] Invalid URL: '' for extension jfppgkomfopklagggkjiaddgndkgopgl [12509:12509:0408/220702:ERROR:extension_downloader.cc(696)] Invalid URL: '' for extension jnkffnoliaheoidfeejcmnidkkgilkja [12509:12509:0408/220702:ERROR:extension_downloader.cc(696)] Invalid URL: '' for extension hgakehlldcacnfhjampnkihibmkgclhk [12509:12509:0408/220702:ERROR:extension_downloader.cc(696)] Invalid URL: '' for extension eejaoobjdaomccncipbcpioedbamjpnn Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [12509:12533:0408/220738:ERROR:native_backend_gnome_x.cc(546)] Keyring save failed: Error communicating with gnome-keyring-daemon Killed ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: chromium-browser 41.0.2272.76-0ubuntu1.1134 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DRM.card0.DVI.D.1: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.HDMI.A.1: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.eDP.1: edid-base64: AP///wANrrsVAB0WAQOAIhN4CkY1nldXlCcUUFQBAQEBAQEBAQEBAQEBAQEBljuAMnE4PkBaPGkAWMIQAAAY/gBOMTU2SEdFLUxCMQog/gBDTU4KICAgICAgICAg/gBOMTU2SEdFLUxCMQogAC4= dpms: On modes: 1920x1080 1680x1050 1400x1050 1280x1024 1440x900 1280x960 1280x854 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 enabled: enabled status: connected Date: Wed Apr 8 22:09:11 2015 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2015-01-29 (69 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141015) Load-Avg-1min: 8.10 Load-Processes-Running-Percent: 0.9% MachineType: Hewlett-Packard HP ENVY TS 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic.efi.signed root=UUID=1cc26cb0-3476-4abf-a12e-acac53ba8537 ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to vivid on 2015-04-06 (2 days ago) dmi.bios.date: 11/06/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 198A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.14 dmi.chassis.asset.tag: 5CG32129MN dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias:
[Desktop-packages] [Bug 1469485] Re: Chromium triggers keychain unlock too late
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1469485 Title: Chromium triggers keychain unlock too late Status in chromium-browser package in Ubuntu: Expired Bug description: When you visit a login page for which you have saved the password, the browser does not auto fill the password. You have to enter it again. Once you have entered it, Chromium asks you to save it (even though it has been saved a thousand times before). When you choose to save it, Ubuntu asks you to unlock the keychain. After you unlock it, you don't have to manually enter saved passwords in the current session. This is extremely stupid and inconvenient - what's the point of saving passwords when you have to always enter it again plus enter the keychain password to log into accounts? Instead of not entering any password - you have to enter two passwords! Other browsers, like Firefox, don't work this way. Please remove the keychain unlock all together or trigger the unlock dialogue prior account password entry or on browser startup. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089 ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 28 09:24:30 2015 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2015-06-06 (21 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Load-Avg-1min: 0.53 Load-Processes-Running-Percent: 0.2% Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1469485/+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 1763036] Re: Firefox menu not showing in Unity's top menubar
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1763036 Title: Firefox menu not showing in Unity's top menubar Status in firefox package in Ubuntu: Expired Bug description: Firefox menu not showing in Unity's top menubar, neither when I move the mouse to the top of the screen, nor when I press Alt. When I press Alt, the menu is shown below the Unity menubar. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 60.0~b11+build2-0ubuntu0.17.10.1 [origin: LP-PPA-mozillateam-firefox-next] Uname: Linux 4.15.0-15.1-liquorix-amd64 x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dserodio 1907 F pulseaudio BuildID: 20180410075342 Channel: beta CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Apr 11 10:41:11 2018 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePlugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-11 (181 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MostRecentCrashID: bp-45cdae7e-18ce-4d0e-9de5-642950180405 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) Profile1PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) Profile2PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=60.0/20180410075342 (In use) Profile1 - LastVersion=58.0.2/20180208173149 (Out of date) Profile2 - LastVersion=60.0/20180329210734 (Out of date) RelatedPackageVersions: adobe-flashplugin 1:20180313.1-0ubuntu0.17.10.1 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to artful on 2017-10-19 (173 days ago) dmi.bios.date: 05/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G22RW dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd05/26/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0G22RW:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1763036/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
@Hui Wang My internal mic still doesn't work. Here is my alsa-info.txt. ** Attachment added: "alsa-info.txt.yFFhMAx6Sl" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+attachment/5281527/+files/alsa-info.txt.yFFhMAx6Sl -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1839010] Re: Touchpad does not work after installing Ubuntu
** Attachment added: "list_devices" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+attachment/5281528/+files/list_devices -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1839010 Title: Touchpad does not work after installing Ubuntu Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I previously had Windows 10 on my protab laptop. After wiping the hard drive and installing Ubuntu 19.04 on the device, the touchpad ceases to respond at all. I am using an external mouse currently. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:39:36 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+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 1839010] Re: Touchpad does not work after installing Ubuntu
Here are the logs: ** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+attachment/5281525/+files/journal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1839010 Title: Touchpad does not work after installing Ubuntu Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I previously had Windows 10 on my protab laptop. After wiping the hard drive and installing Ubuntu 19.04 on the device, the touchpad ceases to respond at all. I am using an external mouse currently. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:39:36 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+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 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
The fix for this bug is in mutter version 3.33.4, which will eventually reach Ubuntu version 19.10, and then maybe others after that. Nothing has been rejected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter source package in Bionic: Confirmed Status in mutter source package in Disco: Confirmed Status in mutter source package in Eoan: In Progress Bug description: https://trello.com/c/i5hENxSO Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 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: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string 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.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+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 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
Sorry for inconvenient Daniel, but the version 3.33.4 was rejected in review? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter source package in Bionic: Confirmed Status in mutter source package in Disco: Confirmed Status in mutter source package in Eoan: In Progress Bug description: https://trello.com/c/i5hENxSO Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 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: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string 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.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+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 1839402] [NEW] package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка перезаписать общий «/lib/ude
Public bug reported: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который отличается от других экземпляров пакета libsane:i386 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Wed Jul 31 06:27:15 2019 ErrorMessage: попытка перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который отличается от других экземпляров пакета libsane:i386 InstallationDate: Installed on 2017-03-04 (887 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: sane-backends Title: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который отличается от других экземпляров пакета libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1839402 Title: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который отличается от других экземпляров пакета libsane:i386 Status in sane-backends package in Ubuntu: New Bug description: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который отличается от других экземпляров пакета libsane:i386 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Wed Jul 31 06:27:15 2019 ErrorMessage: попытка перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который отличается от других экземпляров пакета libsane:i386 InstallationDate: Installed on 2017-03-04 (887 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: sane-backends Title: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который отличается от других экземпляров пакета libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1839402/+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 1833114] Re: print page dialog latency when trying to cancel or to save
Yes I think everything is affected. On Wed, Aug 7, 2019, 10:11 AM Olivier Tilloy, wrote: > I can observe this on my laptop, too. I can't reproduce in a clean disco > VM though. > > This is not specific to chromium though, other applications such as > gedit are affected (snap or deb seems to be irrelevant). > > @Christopher, can you confirm other applications on your system are > similarly affected (test e.g. gedit or evince)? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1833114 > > Title: > print page dialog latency when trying to cancel or to save > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1833114/+subscriptions > -- 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/1833114 Title: print page dialog latency when trying to cancel or to save Status in chromium-browser package in Ubuntu: New Bug description: Since less than a month ago, using the print page dialog (which for me defaults to saving as PDF) is outlandishly slow. Once opened, if I try to close it (click cancel / press Esc) or to use it (click Save or press Enter), there is no visible response, and my system hangs for 10 seconds. After that though, the operation concludes successfully and things return to normal. This did not used to happen. Closing or submitting the print-to-PDF used to result in the pop-up window closing immediately and the browser regaining responsiveness. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-5: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-6: enabled: disabled dpms: On status: connected edid-base64: AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM= modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-DP-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo= modes: 1920x1080 Date: Mon Jun 17 14:03:12 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2019-01-24 (144 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: Load-Avg-1min: 3.09 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Desktop-packages] [Bug 1839253] Re: Excessive screen tearing and flickering
Thanks. The videos seem to show this is a problem with aligning the entire display image. So it's not traditional "tearing", but I totally agree that "tearing" and "flickering" is the best description. Please try logging in to "Ubuntu on Wayland" and tell us if that avoids the problem. Please also try installing a newer kernel such as: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc3/ If the problem still continues then please open a Terminal window and run: dmesg -w Now do you see any new messages appearing in that window when the flickering happens? ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1839253 Title: Excessive screen tearing and flickering Status in linux package in Ubuntu: Incomplete Bug description: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 02:06:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] InstallationDate: Installed on 2019-08-06 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5201 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:56b9 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA 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-23-generic root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.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/linux/+bug/1839253/+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 1838249] Re: crash on startup
Same problem with or without --safe-mode: localc --norestore --safe-mode dbus[893]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2754. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f010b0ae568] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c5d6)[0x7f010b0d75d6] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f010ace8f20] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f010ace8e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f010acea801] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5d6e2)[0x7f010e0526e2] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7f010dfde092] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0e9b0)[0x7f010d0039b0] /usr/lib/libreoffice/program/libmergedlo.so(+0x2ceea3d)[0x7f010dfe3a3d] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x165b2)[0x7f010b0b15b2] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c49f)[0x7f010b0d749f] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f010ace8f20] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f010ace8e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f010acea801] /lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_abort+0x24)[0x7f0108451274] /lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_strdup+0x0)[0x7f0108447b00] /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_iter_append_basic+0x361)[0x7f0108439321] /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args_valist+0x2f3)[0x7f0108439e03] /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args+0x99)[0x7f0108439ed9] /usr/lib/x86_64-linux-gnu/libavahi-client.so.3(avahi_record_browser_new+0x17c)[0x7f00fc1a1bdc] /usr/lib/x86_64-linux-gnu/libcups.so.2(+0x29316)[0x7f010508e316] /usr/lib/x86_64-linux-gnu/libcups.so.2(cupsGetDests2+0x94)[0x7f010508e464] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d73127)[0x7f010e068127] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3f179)[0x7f010b0da179] /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7f01088966db] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f010adcb88f] == localc --norestore dbus[922]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2754. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f9d9f1b3568] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c5d6)[0x7f9d9f1dc5d6] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f9d9ededf20] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f9d9edede97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f9d9edef801] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5d6e2)[0x7f9da21576e2] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7f9da20e3092] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0e9b0)[0x7f9da11089b0] /usr/lib/libreoffice/program/libmergedlo.so(+0x2ceea3d)[0x7f9da20e8a3d] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x165b2)[0x7f9d9f1b65b2] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c49f)[0x7f9d9f1dc49f] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f9d9ededf20] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f9d9edede97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f9d9edef801] /lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_abort+0x24)[0x7f9d9c556274] /lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_strdup+0x0)[0x7f9d9c54cb00] /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_iter_append_basic+0x361)[0x7f9d9c53e321] /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args_valist+0x2f3)[0x7f9d9c53ee03] /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args+0x99)[0x7f9d9c53eed9] /usr/lib/x86_64-linux-gnu/libavahi-client.so.3(avahi_record_browser_new+0x17c)[0x7f9d902a6bdc] /usr/lib/x86_64-linux-gnu/libcups.so.2(+0x29316)[0x7f9d99193316] /usr/lib/x86_64-linux-gnu/libcups.so.2(cupsGetDests2+0x94)[0x7f9d99193464] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d73127)[0x7f9da216d127] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3f179)[0x7f9d9f1df179] /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7f9d9c99b6db] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f9d9eed088f] -- 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/1838249 Title: crash on startup Status in libreoffice package in Ubuntu: Confirmed Bug description: libreoffice --norestore --safe-mode
[Desktop-packages] [Bug 1838249] Re: crash on startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1838249 Title: crash on startup Status in libreoffice package in Ubuntu: Confirmed Bug description: libreoffice --norestore --safe-mode dbus[16783]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2754. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3ba93)[0x7f62a2538a93] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3bca3)[0x7f62a2538ca3] /lib/x86_64-linux-gnu/libc.so.6(+0x43f60)[0x7f62a2329f60] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f62a2329ed7] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f62a230b535] /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xb78d)[0x7f62a19e578d] /lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_strdup+0x0)[0x7f62a1a07380] /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_iter_append_basic+0x369)[0x7f62a19f8a79] /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args_valist+0x154)[0x7f62a19f93d4] /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args+0x99)[0x7f62a19f9669] /usr/lib/x86_64-linux-gnu/libavahi-client.so.3(avahi_record_browser_new+0x17c)[0x7f629d11ac9c] /usr/lib/x86_64-linux-gnu/libcups.so.2(+0x28f1e)[0x7f62a0537f1e] /usr/lib/x86_64-linux-gnu/libcups.so.2(cupsGetDests2+0x94)[0x7f62a05380b4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e97a17)[0x7f62a53f0a17] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3e6f8)[0x7f62a253b6f8] /lib/x86_64-linux-gnu/libpthread.so.0(+0x9182)[0x7f62a1a34182] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f62a2403b1f] --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-10-29 (273 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: libreoffice-core 1:6.2.5-0ubuntu0.19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Tags: disco Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-25 (95 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1838249/+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 1766495] Re: "your libfreerdp does not support h264"
I found it.. if you already have the connection setup right click, ->Color Depth (Choose Tru color(32 bpp) and it works like a charm.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1766495 Title: "your libfreerdp does not support h264" Status in remmina package in Ubuntu: Confirmed Bug description: When I try to connect via RDP, Remmina gives this error: "You requested an h264 GFX mode for server , but your libfreerdp does not support h264. Please check color depth settings." However, (1) I don't see any color depth settings in Remmina GUI, and (2) ubuntu-restricted-extras is installed. I have libx264-152 version 2:0.152.2854+gite9a5903-2. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: remmina 1.2.0-rcgit.29+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 24 09:29:44 2018 InstallationDate: Installed on 2018-03-23 (31 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1766495/+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 1766495] Re: "your libfreerdp does not support h264"
Can someone give a screen shot of how to specify "True Color" or another color depth in Remmina? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1766495 Title: "your libfreerdp does not support h264" Status in remmina package in Ubuntu: Confirmed Bug description: When I try to connect via RDP, Remmina gives this error: "You requested an h264 GFX mode for server , but your libfreerdp does not support h264. Please check color depth settings." However, (1) I don't see any color depth settings in Remmina GUI, and (2) ubuntu-restricted-extras is installed. I have libx264-152 version 2:0.152.2854+gite9a5903-2. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: remmina 1.2.0-rcgit.29+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 24 09:29:44 2018 InstallationDate: Installed on 2018-03-23 (31 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1766495/+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 1839253] Re: Excessive screen tearing and flickering
I'm assuming you want me to send the allpackages.txt to you, so here it is On Wed, Aug 7, 2019 at 2:51 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > These lines suggest some graphics-related packages are missing: > > (II) GLX: Initialized DRISWRAST GL provider for screen 0 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > > Please run: > > dpkg -l > allpackages.txt > > and then attach the file 'allpackages.txt'. > > > ** Package changed: xorg (Ubuntu) => ubuntu > > ** Changed in: ubuntu >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1839253 > > Title: > Excessive screen tearing and flickering > > Status in Ubuntu: > Incomplete > > Bug description: > I am experiencing a large amount of screen tearing flickering and > artifacting. I've tried the common fix that is suggested on > askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- > graphics.conf and this has not changed anything. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: xorg 1:7.7+19ubuntu12 > ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 > Uname: Linux 5.0.0-23-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27.1 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Aug 7 02:06:01 2019 > DistUpgraded: Fresh install > DistroCodename: disco > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 > [VGA controller]) > Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] > InstallationDate: Installed on 2019-08-06 (1 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 27c6:5201 >Bus 001 Device 003: ID 8087:0a2b Intel Corp. >Bus 001 Device 002: ID 13d3:56b9 IMC Networks >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA > 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-23-generic > root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/18/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX391UA.204 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX391UA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: ZenBook S > dmi.product.name: ZenBook S UX391UA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.97-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.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/+bug/1839253/+subscriptions > ** Attachment added: "allpackages.txt" https://bugs.launchpad.net/bugs/1839253/+attachment/5281502/+files/allpackages.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1839253 Title: Excessive screen tearing and flickering Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64
Re: [Desktop-packages] [Bug 1839253] Re: Excessive screen tearing and flickering
Here are two videos: https://photos.app.goo.gl/mtpHBRNHrY8XvZ3y6 https://photos.app.goo.gl/uV34bkz1ZZsd6msGA On Wed, Aug 7, 2019 at 2:51 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Also, if you can then please take a video of the issue and attach it > here. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1839253 > > Title: > Excessive screen tearing and flickering > > Status in Ubuntu: > Incomplete > > Bug description: > I am experiencing a large amount of screen tearing flickering and > artifacting. I've tried the common fix that is suggested on > askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- > graphics.conf and this has not changed anything. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: xorg 1:7.7+19ubuntu12 > ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 > Uname: Linux 5.0.0-23-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27.1 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Aug 7 02:06:01 2019 > DistUpgraded: Fresh install > DistroCodename: disco > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 > [VGA controller]) > Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] > InstallationDate: Installed on 2019-08-06 (1 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 27c6:5201 >Bus 001 Device 003: ID 8087:0a2b Intel Corp. >Bus 001 Device 002: ID 13d3:56b9 IMC Networks >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA > 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-23-generic > root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/18/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX391UA.204 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX391UA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: ZenBook S > dmi.product.name: ZenBook S UX391UA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.97-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.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/+bug/1839253/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1839253 Title: Excessive screen tearing and flickering Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 02:06:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc.
Re: [Desktop-packages] [Bug 1839253] Re: Excessive screen tearing and flickering
It's not clear to me how to change the driver to 'modesetting'. What I did was edit the file /etc/X11/xorg.conf.d/20-intel-graphics.conf and changed the line: Driver "intel" to Driver "modesetting" and I didn't see any change. On Wed, Aug 7, 2019 at 3:03 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Note also the 'intel' driver for Xorg is deprecated. You should be using > the default 'modesetting' driver for the best experience. If you can > then please go back to using that, not 'intel'. > > ** Package changed: ubuntu => xserver-xorg-video-intel (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1839253 > > Title: > Excessive screen tearing and flickering > > Status in xserver-xorg-video-intel package in Ubuntu: > Incomplete > > Bug description: > I am experiencing a large amount of screen tearing flickering and > artifacting. I've tried the common fix that is suggested on > askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- > graphics.conf and this has not changed anything. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: xorg 1:7.7+19ubuntu12 > ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 > Uname: Linux 5.0.0-23-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27.1 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Aug 7 02:06:01 2019 > DistUpgraded: Fresh install > DistroCodename: disco > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 > [VGA controller]) > Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] > InstallationDate: Installed on 2019-08-06 (1 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 27c6:5201 >Bus 001 Device 003: ID 8087:0a2b Intel Corp. >Bus 001 Device 002: ID 13d3:56b9 IMC Networks >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA > 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-23-generic > root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/18/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX391UA.204 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX391UA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: ZenBook S > dmi.product.name: ZenBook S UX391UA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.97-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.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/xserver-xorg-video-intel/+bug/1839253/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1839253 Title: Excessive screen tearing and flickering Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13]
[Desktop-packages] [Bug 1839380] Re: Nautilus freezes when restoring files and a copy already exists
Fixed the description so it reflects more to the bug, as well as the reproduction steps. ** Description changed: I have trashed the hidden file using nautilus to the trash bin, be it the hidden configuration file for XScreenSaver that is compiled from - source, and when it regenerated the hidden file, it is regenerated with - old config. + source, and it regenerated the hidden file in the same location that I + have deleted the old copy in. - I attempted to restore the file, but Nautilus freezes. It should give me + I attempted to restore the file, but because the file with the same name + is originated on the same location, Nautilus freezes. It should give me the "Replace file with newer version" dialog so I can decide if I want to replace the old file with the new one, or if I want to rename the trashed hidden file to another name. It shouldn't freeze. - However, the freeze only happens if the old file is in the trash, the - new file is located in the original directory, and both files have same - names. + Here's the clearer example. Suppose that... + + 1. I created a file named "test.txt" on "/home/eofla", + 2. I put it to the trash bin, + 3. I repeated Step 1, and + 4. I attempted to restore the same file that was on the trash. + 5. Nautilus freezes. Version of Ubuntu: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version of Nautilus: nautilus: Installed: 1:3.32.1-1ubuntu1 Candidate: 1:3.32.1-1ubuntu1 Version table: *** 1:3.32.1-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Debug output with "G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus": Nautilus-Share-Message: 23:01:44.608: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Debug output using "gdb nautilus" with exported environment variables of G_DEBUG="all" NAUTILUS_DEBUG="All" (More useful, with stack trace): https://paste.ubuntu.com/p/ChpBrDsTtd/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 13:43:40 2019 GsettingsChanges: InstallationDate: Installed on 2019-07-21 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1839380 Title: Nautilus freezes when restoring files and a copy already exists Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: I have trashed the hidden file using nautilus to the trash bin, be it the hidden configuration file for XScreenSaver that is compiled from source, and it regenerated the hidden file in the same location that I have deleted the old copy in. I attempted to restore the file, but because the file with the same name is originated on the same location, Nautilus freezes. It should give me the "Replace file with newer version" dialog so I can decide if I want to replace the old file with the new one, or if I want to rename the trashed hidden file to another name. It shouldn't freeze. Here's the clearer example. Suppose that... 1. I created a file named "test.txt" on "/home/eofla", 2. I put it to the trash bin, 3. I repeated Step 1, and 4. I attempted to restore the same file that was on the trash. 5. Nautilus freezes. Version of Ubuntu: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version of Nautilus: nautilus: Installed: 1:3.32.1-1ubuntu1 Candidate: 1:3.32.1-1ubuntu1 Version table: *** 1:3.32.1-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Debug output with "G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus": Nautilus-Share-Message: 23:01:44.608: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Debug output using "gdb nautilus" with exported environment variables of G_DEBUG="all" NAUTILUS_DEBUG="All" (More useful, with stack trace): https://paste.ubuntu.com/p/ChpBrDsTtd/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 13:43:40 2019 GsettingsChanges: InstallationDate: Installed on 2019-07-21 (16 days ago)
[Desktop-packages] [Bug 1837098] Re: Can't print in monochrome, only in colour
Can you attach the PPD file (from /etc/cups/ppd/) of your printer of the Disco machine and if possble also the one from your Bionic machine? ** Changed in: cups (Ubuntu) Status: New => Incomplete -- 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: Incomplete 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 1823361] Re: WeTransfer filelink provider is missing
** Changed in: thunderbird (Ubuntu) Status: In Progress => Fix Committed -- 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/1823361 Title: WeTransfer filelink provider is missing Status in thunderbird package in Ubuntu: Fix Committed Bug description: Upstream builds of thunderbird include the WeTransfer filelink provider. The Ubuntu package doesn't. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.6.1+build2-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-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: osomon 2794 F pulseaudio BuildID: 20190325095516 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 17:05:04 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) InstallationDate: Installed on 2016-07-02 (1006 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325095516 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-03-16 (19 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO 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:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.sku: LENOVO_MT_2306 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1823361/+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 1823361] Re: WeTransfer filelink provider is missing
** Branch linked: lp:~mozillateam/thunderbird/thunderbird.disco ** Branch linked: lp:~mozillateam/thunderbird/thunderbird.xenial ** Branch linked: lp:~mozillateam/thunderbird/thunderbird.bionic ** Branch linked: lp:thunderbird/stable -- 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/1823361 Title: WeTransfer filelink provider is missing Status in thunderbird package in Ubuntu: Fix Committed Bug description: Upstream builds of thunderbird include the WeTransfer filelink provider. The Ubuntu package doesn't. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.6.1+build2-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-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: osomon 2794 F pulseaudio BuildID: 20190325095516 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 17:05:04 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) InstallationDate: Installed on 2016-07-02 (1006 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325095516 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-03-16 (19 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO 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:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.sku: LENOVO_MT_2306 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1823361/+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 1839380] Re: Nautilus freezes when restoring hidden or normal file
The bug isn't to do with just restoring files as that works perfectly. The bug is restoring files back to where it was deleted from and a copy of the file already exists. I think the bug description needs to reflect that so I'm going to change it again. ** Summary changed: - Nautilus freezes when restoring hidden or normal file + Nautilus freezes when restoring files and a copy already exists -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1839380 Title: Nautilus freezes when restoring files and a copy already exists Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: I have trashed the hidden file using nautilus to the trash bin, be it the hidden configuration file for XScreenSaver that is compiled from source, and it regenerated the hidden file in the same location that I have deleted the old copy in. I attempted to restore the file, but because the file with the same name is originated on the same location, Nautilus freezes. It should give me the "Replace file with newer version" dialog so I can decide if I want to replace the old file with the new one, or if I want to rename the trashed hidden file to another name. It shouldn't freeze. Here's the clearer example. Suppose that... 1. I created a file named "test.txt" on "/home/eofla", 2. I put it to the trash bin, 3. I repeated Step 1, and 4. I attempted to restore the same file that was on the trash. 5. Nautilus freezes. Version of Ubuntu: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version of Nautilus: nautilus: Installed: 1:3.32.1-1ubuntu1 Candidate: 1:3.32.1-1ubuntu1 Version table: *** 1:3.32.1-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Debug output with "G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus": Nautilus-Share-Message: 23:01:44.608: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Debug output using "gdb nautilus" with exported environment variables of G_DEBUG="all" NAUTILUS_DEBUG="All" (More useful, with stack trace): https://paste.ubuntu.com/p/ChpBrDsTtd/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 13:43:40 2019 GsettingsChanges: InstallationDate: Installed on 2019-07-21 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1839380/+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 1839380] Re: Nautilus freezes when restoring hidden or normal file
** Summary changed: - Nautilus freezes when restoring file with same name and location + Nautilus freezes when restoring hidden or normal file -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1839380 Title: Nautilus freezes when restoring hidden or normal file Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: I have trashed the hidden file using nautilus to the trash bin, be it the hidden configuration file for XScreenSaver that is compiled from source, and when it regenerated the hidden file, it is regenerated with old config. I attempted to restore the file, but Nautilus freezes. It should give me the "Replace file with newer version" dialog so I can decide if I want to replace the old file with the new one, or if I want to rename the trashed hidden file to another name. It shouldn't freeze. However, the freeze only happens if the old file is in the trash, the new file is located in the original directory, and both files have same names. Version of Ubuntu: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version of Nautilus: nautilus: Installed: 1:3.32.1-1ubuntu1 Candidate: 1:3.32.1-1ubuntu1 Version table: *** 1:3.32.1-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Debug output with "G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus": Nautilus-Share-Message: 23:01:44.608: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Debug output using "gdb nautilus" with exported environment variables of G_DEBUG="all" NAUTILUS_DEBUG="All" (More useful, with stack trace): https://paste.ubuntu.com/p/ChpBrDsTtd/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 13:43:40 2019 GsettingsChanges: InstallationDate: Installed on 2019-07-21 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1839380/+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 1839380] Re: Nautilus freezes when restoring hidden file
It's a known problem: https://gitlab.gnome.org/GNOME/nautilus/issues/790 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #790 https://gitlab.gnome.org/GNOME/nautilus/issues/790 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/790 Importance: Unknown Status: Unknown ** Summary changed: - Nautilus freezes when restoring hidden file + Nautilus freezes when restoring file with same name and location -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1839380 Title: Nautilus freezes when restoring hidden or normal file Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: I have trashed the hidden file using nautilus to the trash bin, be it the hidden configuration file for XScreenSaver that is compiled from source, and when it regenerated the hidden file, it is regenerated with old config. I attempted to restore the file, but Nautilus freezes. It should give me the "Replace file with newer version" dialog so I can decide if I want to replace the old file with the new one, or if I want to rename the trashed hidden file to another name. It shouldn't freeze. However, the freeze only happens if the old file is in the trash, the new file is located in the original directory, and both files have same names. Version of Ubuntu: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version of Nautilus: nautilus: Installed: 1:3.32.1-1ubuntu1 Candidate: 1:3.32.1-1ubuntu1 Version table: *** 1:3.32.1-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Debug output with "G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus": Nautilus-Share-Message: 23:01:44.608: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Debug output using "gdb nautilus" with exported environment variables of G_DEBUG="all" NAUTILUS_DEBUG="All" (More useful, with stack trace): https://paste.ubuntu.com/p/ChpBrDsTtd/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 13:43:40 2019 GsettingsChanges: InstallationDate: Installed on 2019-07-21 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1839380/+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 1839380] Re: Nautilus freezes when restoring hidden file
Thanks for confirming! This suggests that not only does it freeze on hidden files, but also normal files. It should be fixed soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1839380 Title: Nautilus freezes when restoring hidden or normal file Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: I have trashed the hidden file using nautilus to the trash bin, be it the hidden configuration file for XScreenSaver that is compiled from source, and when it regenerated the hidden file, it is regenerated with old config. I attempted to restore the file, but Nautilus freezes. It should give me the "Replace file with newer version" dialog so I can decide if I want to replace the old file with the new one, or if I want to rename the trashed hidden file to another name. It shouldn't freeze. However, the freeze only happens if the old file is in the trash, the new file is located in the original directory, and both files have same names. Version of Ubuntu: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version of Nautilus: nautilus: Installed: 1:3.32.1-1ubuntu1 Candidate: 1:3.32.1-1ubuntu1 Version table: *** 1:3.32.1-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Debug output with "G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus": Nautilus-Share-Message: 23:01:44.608: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Debug output using "gdb nautilus" with exported environment variables of G_DEBUG="all" NAUTILUS_DEBUG="All" (More useful, with stack trace): https://paste.ubuntu.com/p/ChpBrDsTtd/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 13:43:40 2019 GsettingsChanges: InstallationDate: Installed on 2019-07-21 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1839380/+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 1837233] Re: [bionic] Manual IPv6 routes are not set
pitti, have you already tried network-manager 1.10.14 from bionic-
proposed (bug 1754671)? It did not make it to -updates as there appeared
two regression reports (bug 1829838 and bug 1829913), but if these
regressions do not affect your use case you could try it. I would like
to know whether it perhaps fixes your manual route problem.
--
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/1837233
Title:
[bionic] Manual IPv6 routes are not set
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
Won't Fix
Bug description:
I have a system connection like this:
-- /etc/NetworkManager/system-connections/eth2 ---
[connection]
id=eth2
uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd
type=ethernet
gateway-ping-timeout=12
interface-name=eth2
permissions=
timestamp=1563551266
[ethernet]
mac-address-blacklist=
[ipv4]
dns-search=
method=shared
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ignore-auto-routes=true
method=auto
route1=1:2::/60,1:2::3,42
-- 8< -
In particular, the last line (route1=) which sets a manual IPv6 route.
Of course this is rather bogus, I'm just using this to test cockpit's
web UI.
On Ubuntu 19.04, Debian 10, and Debian testing this works just fine:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42
}
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 101
IP6.ROUTE[2]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[3]: dst = 1:2::3/128, nh = ::, mt = 42
IP6.ROUTE[4]: dst = 1:2::/60, nh = 1:2::3, mt = 42
[...]
# ip -6 route show dev eth2
1:2::3 proto static metric 42 pref medium
1:2::/60 via 1:2::3 proto static metric 42 pref medium
fe80::/64 proto kernel metric 101 pref medium
(There, the file is called eth2.nmconnection, but same difference)
On Ubuntu 18.04 however, the route manual is ignored, and only the
automatic link-local one exists:
# nmcli c show eth2
ipv6.routes:{ ip = 1:2::/60, nh = 1:2::3, mt = 42
}
IP6.ROUTE[1]: dst = ff00::/8, nh = ::, mt = 256,
table=255
IP6.ROUTE[2]: dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[3]: dst = fe80::/64, nh = ::, mt = 101
# ip -6 route show dev eth2
fe80::/64 proto kernel metric 101 pref medium
fe80::/64 proto kernel metric 256 pref medium
Restarting NetworkManager does not help, nor does rebooting.
DistroRelease: Ubuntu 18.04
Package: 1.10.6-2ubuntu1.1
Architecture: amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1837233/+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 1766495] Re: "your libfreerdp does not support h264"
I believe AVC/H.264 is better compression than what is used by the other options. I would very much like it if I did not have to select True Color or any of the other options. Is there a workaround or plan to make AVC/H.264 usable in Ubuntu 18.04? I am using the remmina-ppa-team/remmina-next repo on Ubuntu 18.04, and these are the packages I have installed ii remmina1.2.0-rcgit.29+dfsg-1ubuntu1 amd64GTK+ Remote Desktop Client ii remmina-common 1.2.0-rcgit.29+dfsg-1ubuntu1 all Common files for Remmina ii remmina-plugin-rdp:amd64 1.2.0-rcgit.29+dfsg-1ubuntu1 amd64RDP plugin for Remmina ii remmina-plugin-secret:amd641.2.0-rcgit.29+dfsg-1ubuntu1 amd64Secret plugin for Remmina ii remmina-plugin-vnc:amd64 1.2.0-rcgit.29+dfsg-1ubuntu1 amd64VNC plugin for Remmina -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1766495 Title: "your libfreerdp does not support h264" Status in remmina package in Ubuntu: Confirmed Bug description: When I try to connect via RDP, Remmina gives this error: "You requested an h264 GFX mode for server , but your libfreerdp does not support h264. Please check color depth settings." However, (1) I don't see any color depth settings in Remmina GUI, and (2) ubuntu-restricted-extras is installed. I have libx264-152 version 2:0.152.2854+gite9a5903-2. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: remmina 1.2.0-rcgit.29+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 24 09:29:44 2018 InstallationDate: Installed on 2018-03-23 (31 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1766495/+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 1839380] Re: Nautilus freezes when restoring hidden file
I can reproduce this and the file doesn't have to be hidden. I copied a file to ~/Downloads and then moved it to the Rubbish Bin. I re-copied the file to ~/Downloads and then attempted to restore the first copy back to ~/Downloads. nautilus froze immediately and a couple of minutes later is still unusable. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1839380 Title: Nautilus freezes when restoring hidden file Status in nautilus package in Ubuntu: Confirmed Bug description: I have trashed the hidden file using nautilus to the trash bin, be it the hidden configuration file for XScreenSaver that is compiled from source, and when it regenerated the hidden file, it is regenerated with old config. I attempted to restore the file, but Nautilus freezes. It should give me the "Replace file with newer version" dialog so I can decide if I want to replace the old file with the new one, or if I want to rename the trashed hidden file to another name. It shouldn't freeze. However, the freeze only happens if the old file is in the trash, the new file is located in the original directory, and both files have same names. Version of Ubuntu: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version of Nautilus: nautilus: Installed: 1:3.32.1-1ubuntu1 Candidate: 1:3.32.1-1ubuntu1 Version table: *** 1:3.32.1-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Debug output with "G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus": Nautilus-Share-Message: 23:01:44.608: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Debug output using "gdb nautilus" with exported environment variables of G_DEBUG="all" NAUTILUS_DEBUG="All" (More useful, with stack trace): https://paste.ubuntu.com/p/ChpBrDsTtd/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 13:43:40 2019 GsettingsChanges: InstallationDate: Installed on 2019-07-21 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1839380/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1190 https://gitlab.gnome.org/GNOME/nautilus/issues/1190 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1190 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1190 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+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”
Comfirmed. ** Attachment added: "kodi core dump and crash logs" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+attachment/5281493/+files/kodi-crash.tar.xz -- 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: Confirmed 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 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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: Confirmed 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 1839380] [NEW] Nautilus freezes when restoring hidden file
Public bug reported: I have trashed the hidden file using nautilus to the trash bin, be it the hidden configuration file for XScreenSaver that is compiled from source, and when it regenerated the hidden file, it is regenerated with old config. I attempted to restore the file, but Nautilus freezes. It should give me the "Replace file with newer version" dialog so I can decide if I want to replace the old file with the new one, or if I want to rename the trashed hidden file to another name. It shouldn't freeze. However, the freeze only happens if the old file is in the trash, the new file is located in the original directory, and both files have same names. Version of Ubuntu: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Version of Nautilus: nautilus: Installed: 1:3.32.1-1ubuntu1 Candidate: 1:3.32.1-1ubuntu1 Version table: *** 1:3.32.1-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Debug output with "G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus": Nautilus-Share-Message: 23:01:44.608: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Debug output using "gdb nautilus" with exported environment variables of G_DEBUG="all" NAUTILUS_DEBUG="All" (More useful, with stack trace): https://paste.ubuntu.com/p/ChpBrDsTtd/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 13:43:40 2019 GsettingsChanges: InstallationDate: Installed on 2019-07-21 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 eoan nautilus ** Description changed: I have trashed the hidden file using nautilus to the trash bin, be it the hidden configuration file for XScreenSaver that is compiled from source, and when it regenerated the hidden file, it is regenerated with old config. I attempted to restore the file, but Nautilus freezes. It should give me the "Replace file with newer version" dialog so I can decide if I want to replace the old file with the new one, or if I want to rename the trashed hidden file to another name. It shouldn't freeze. + However, the freeze only happens if the old file is in the trash, the + new file is located in the original directory, and both files have same + names. + Version of Ubuntu: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version of Nautilus: nautilus: - Installed: 1:3.32.1-1ubuntu1 - Candidate: 1:3.32.1-1ubuntu1 - Version table: - *** 1:3.32.1-1ubuntu1 500 - 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:3.32.1-1ubuntu1 + Candidate: 1:3.32.1-1ubuntu1 + Version table: + *** 1:3.32.1-1ubuntu1 500 + 500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages + 100 /var/lib/dpkg/status Debug output with "G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus": Nautilus-Share-Message: 23:01:44.608: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Debug output using "gdb nautilus" with exported environment variables of G_DEBUG="all" NAUTILUS_DEBUG="All" (More useful, with stack trace): https://paste.ubuntu.com/p/ChpBrDsTtd/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 13:43:40 2019 GsettingsChanges: - + InstallationDate: Installed on 2019-07-21 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1839380 Title: Nautilus freezes when restoring hidden file Status in nautilus package in Ubuntu: New Bug description: I have trashed the hidden file using nautilus to the trash bin, be it the hidden configuration file for XScreenSaver that is compiled from source, and when it regenerated the hidden file, it is regenerated with old config. I attempted to restore the file, but Nautilus freezes. It should give me the "Replace file with newer version" dialog so I can decide if I want to
[Desktop-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/1190 + + --- + https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in nautilus package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1190 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726129/+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 1823361] Re: WeTransfer filelink provider is missing
** Changed in: thunderbird (Ubuntu) Status: Triaged => In Progress -- 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/1823361 Title: WeTransfer filelink provider is missing Status in thunderbird package in Ubuntu: In Progress Bug description: Upstream builds of thunderbird include the WeTransfer filelink provider. The Ubuntu package doesn't. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.6.1+build2-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-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: osomon 2794 F pulseaudio BuildID: 20190325095516 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 17:05:04 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) InstallationDate: Installed on 2016-07-02 (1006 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325095516 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-03-16 (19 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO 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:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.sku: LENOVO_MT_2306 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1823361/+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 1839111] Re: Please merge libvdpau 1.2-1 (main) from Debian unstable (main)
This bug was fixed in the package libvdpau - 1.2-1ubuntu1 --- libvdpau (1.2-1ubuntu1) eoan; urgency=low * Resynchronize with Debian (LP: #1839111), remaining changes: - control: Demote libvdpau-va-gl1 from vdpau-driver-all Depends to Suggests. -- Alberto Milone Tue, 06 Aug 2019 11:43:23 +0200 ** Changed in: libvdpau (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/1839111 Title: Please merge libvdpau 1.2-1 (main) from Debian unstable (main) Status in libvdpau package in Ubuntu: Fix Released Bug description: Please merge libvdpau 1.2-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1839111/+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 1839212] Re: UX issues in "Ubuntu Software" and related applications
Hi Chris, I've up'd your user level, you should be able to post now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1839212 Title: UX issues in "Ubuntu Software" and related applications Status in gnome-software package in Ubuntu: Invalid Bug description: I think it's important to have a look at the high level user experience around software updating in Ubuntu. This is all tested on the latest Ubuntu 19 (installed a few days ago). Apologies if this is the wrong place to post, and that I'm bundling a couple of things together. These issues go across "Ubuntu Software", "Software Updater" and "Software & Updates", and I didn't want to spam ya'll with multiple small disjointed issues. On the other hand I think this stuff is super-important for user experience and needs discussing in a bug context, not a support context. 1) Searching for "software" under "Show Applications", produces a screen with these options: "Ubuntu Softw..." "Software & Up..." "Software Upd..." This is a poor experience. There's no way for a new user to tell these 3 things apart, and for a real newbie it's not even obvious when opening them. For example, my initial thought with "Ubuntu Software" is perhaps it is just for installing snaps, that's the kind of unexpected confusion that can happen when there's multiple similar-sounding options on a menu. My suggestion would be to only have "Ubuntu Software". Remove the .desktop files for the other options, but make them available from within "Ubuntu Software". 2) "Software & Updates" has CD/DVD options, which is (a) antiquated and (b) unclear how it works. I understand it likely works by standardized mount paths, but most users nowadays will be installing with a USB stick which has no support. Imagine a new user who needs to install custom broadlink drivers from USB stick, but there's no way to easily configure the package manager to do it. That was my situation, I ended up finding the .deb file on the USB manually. I think you should just rework all this as an "Installation Media" option, and search all mounted paths for an Ubuntu signature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1839212/+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 1839212] Re: UX issues in "Ubuntu Software" and related applications
Thanks for bringing up the Discourse site. I actually have a lot more I want to talk about that is general and this seems to be the perfect place. I really want to contribute there but I don't seem to have posting permission on the Discourse. Username chrisgraham. There's no post topic button for me under Desktop. I can get one if I do the 'infinite scrolling' all the way to the bottom, but I think when it gives me one there it's a permissions bug because it will give me an access error when I actually follow through and post. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1839212 Title: UX issues in "Ubuntu Software" and related applications Status in gnome-software package in Ubuntu: Invalid Bug description: I think it's important to have a look at the high level user experience around software updating in Ubuntu. This is all tested on the latest Ubuntu 19 (installed a few days ago). Apologies if this is the wrong place to post, and that I'm bundling a couple of things together. These issues go across "Ubuntu Software", "Software Updater" and "Software & Updates", and I didn't want to spam ya'll with multiple small disjointed issues. On the other hand I think this stuff is super-important for user experience and needs discussing in a bug context, not a support context. 1) Searching for "software" under "Show Applications", produces a screen with these options: "Ubuntu Softw..." "Software & Up..." "Software Upd..." This is a poor experience. There's no way for a new user to tell these 3 things apart, and for a real newbie it's not even obvious when opening them. For example, my initial thought with "Ubuntu Software" is perhaps it is just for installing snaps, that's the kind of unexpected confusion that can happen when there's multiple similar-sounding options on a menu. My suggestion would be to only have "Ubuntu Software". Remove the .desktop files for the other options, but make them available from within "Ubuntu Software". 2) "Software & Updates" has CD/DVD options, which is (a) antiquated and (b) unclear how it works. I understand it likely works by standardized mount paths, but most users nowadays will be installing with a USB stick which has no support. Imagine a new user who needs to install custom broadlink drivers from USB stick, but there's no way to easily configure the package manager to do it. That was my situation, I ended up finding the .deb file on the USB manually. I think you should just rework all this as an "Installation Media" option, and search all mounted paths for an Ubuntu signature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1839212/+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 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
@Norbert I have Laptop with 16.04. And Alt+Shift, Alt+Shift+Tab are working ok. I have also tested it with new default installation in Virtualbox. And it also works fine. And it doesn't matter if i use Mate or Unity. -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in gnome-control-center: Unknown Status in X.Org X server: New Status in gnome-control-center package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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 1838965] Re: Screen tearing in Firefox on Wayland
I use Intel HD 500 video card and default free driver, that is included in Ubuntu GNU/Linux ср, 7 авг. 2019 г., 13:10 Olivier Tilloy : > The tearing isn't obvious to my untrained eye, nor can I observe it > locally when testing in VMs. > I tested both X11 and Wayland, by scrolling up and down a long wikipedia > page. > > Can you provide details about your graphics card and driver? > > Can you test an upstream build (download and unpack > https://www.mozilla.org/firefox/download/thanks/) and confirm whether > it's similarly affected? If so, can you file an upstream bug at > https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox and share > the link to it here? > > 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/1838965 > > Title: > Screen tearing in Firefox on Wayland > > Status in firefox package in Ubuntu: > Incomplete > > Bug description: > Details here: https://photos.app.goo.gl/9kA7R6KqNaSsn9CB8 > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: firefox 68.0.1+build1-0ubuntu2 > ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 > Uname: Linux 5.2.0-8-generic x86_64 > ApportVersion: 2.20.11-0ubuntu7 > Architecture: amd64 > BuildID: 20190719083815 > CurrentDesktop: ubuntu:GNOME > Date: Mon Aug 5 13:36:32 2019 > DefaultProfileExtensions: extensions.sqlite corrupt or missing > DefaultProfileIncompatibleExtensions: Unavailable (corrupt or > non-existant compatibility.ini or extensions.sqlite) > DefaultProfileLocales: extensions.sqlite corrupt or missing > DefaultProfilePrefErrors: Unexpected character ',' before close > parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 > DefaultProfileThemes: extensions.sqlite corrupt or missing > InstallationDate: Installed on 2019-08-04 (0 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) > Profiles: >Profile1 (Default) - LastVersion=None/None (Out of date) >Profile0 - LastVersion=68.0.1/20190719083815 (In use) > SourcePackage: firefox > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838965/+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/1838965 Title: Screen tearing in Firefox on Wayland Status in firefox package in Ubuntu: Incomplete Bug description: Details here: https://photos.app.goo.gl/9kA7R6KqNaSsn9CB8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 68.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BuildID: 20190719083815 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 13:36:32 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.0.1/20190719083815 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838965/+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 1827199] Re: firefox menu font can not set by gnome tweak 3.32.0
I can reproduce the problem in a VM when changing the default language of the desktop to Traditional Chinese. The upstream build of firefox is similarly affected. ** Summary changed: - firefox menu font can not set by gnome tweak 3.32.0 + firefox doesn't honour custom interface font when default language is Chinese ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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/1827199 Title: firefox doesn't honour custom interface font when default language is Chinese Status in firefox package in Ubuntu: Confirmed Bug description: I use ubuntu19.04, gnome 3.32.1, gnome tweak version 3.32.0, firefox version 66.0.3 In ubuntu18.04, firefox menu font can be set by gnome-tweak, but in ubuntu19.04 firefox menu font can not set by gnome tweak now.(The default menu font for firefox is too big and ugly I think) I don't know how to set firefox menu font now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1827199/+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 1833114] Re: print page dialog latency when trying to cancel or to save
I can observe this on my laptop, too. I can't reproduce in a clean disco VM though. This is not specific to chromium though, other applications such as gedit are affected (snap or deb seems to be irrelevant). @Christopher, can you confirm other applications on your system are similarly affected (test e.g. gedit or evince)? -- 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/1833114 Title: print page dialog latency when trying to cancel or to save Status in chromium-browser package in Ubuntu: New Bug description: Since less than a month ago, using the print page dialog (which for me defaults to saving as PDF) is outlandishly slow. Once opened, if I try to close it (click cancel / press Esc) or to use it (click Save or press Enter), there is no visible response, and my system hangs for 10 seconds. After that though, the operation concludes successfully and things return to normal. This did not used to happen. Closing or submitting the print-to-PDF used to result in the pop-up window closing immediately and the browser regaining responsiveness. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-5: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-6: enabled: disabled dpms: On status: connected edid-base64: AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM= modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-DP-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo= modes: 1920x1080 Date: Mon Jun 17 14:03:12 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2019-01-24 (144 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: Load-Avg-1min: 3.09 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications
[Desktop-packages] [Bug 1809150] Re: [snap] Permission denied in Chromium 71.0.3578.80 (Official Build)
Sorry for the lack of timely feedback Kulfy. Is the latest version of the chromium snap still affected by that issue? If so, can you please elaborate on what exactly you mean by "I get read error"? Is this an error dialog, a log in the terminal, or an apparmor denial? What's the full path to your desktop folder? Is it a symbolic link to somewhere else? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1809150 Title: [snap] Permission denied in Chromium 71.0.3578.80 (Official Build) Status in chromium-browser package in Ubuntu: Incomplete Bug description: I have installed Chromium 71.0.3578.80 (Official Build) through snap. But whenever I change path of Download to ~/Desktop I get read error. And that's indeed a read error since I can still download and save file to that folder (no write error). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1809150/+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 1806080] Re: [snap] Chromium snap crashes when trying to access fs
@Tejeev, can you confirm whether the latest version of the chromium snap has fixed the crashes? -- 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/1806080 Title: [snap] Chromium snap crashes when trying to access fs Status in chromium-browser package in Ubuntu: Confirmed Bug description: When I attempt to upload or save on certain pages it crashes the browser. Some examples below. Does not happen on Google Drive. Looks like it's trying to query the fs and dies when it can't. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial Kernel: 4.15.0-39-generic Chromium: Version 70.0.3538.110 (Official Build) snap (64-bit) # Right click on blank page "save as" Nov 30 16:31:00 $HOSTNAME kernel: [35208.515968] audit: type=1400 audit(1543595460.939:151): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=30734 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Restart browser Nov 30 16:31:04 $HOSTNAME dbus[1899]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name="org.freedesktop.secrets" pid=32093 label="snap.chromium.chromium" peer_pid=1823 peer_label="unconfined" Nov 30 16:31:04 $HOSTNAME kernel: [35212.081247] audit: type=1107 audit(1543595464.507:152): pid=1384 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=31991 label="snap.chromium.chromium" peer_pid=24826 peer_label="unconfined" Nov 30 16:31:05 $HOSTNAME kernel: [35213.238692] audit: type=1400 audit(1543595465.663:153): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=31991 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 30 16:31:05 $HOSTNAME kernel: [35213.274048] audit: type=1400 audit(1543595465.699:154): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c6:0" pid=31991 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Right click on blank page "save as" #2 Nov 30 16:31:08 $HOSTNAME kernel: [35216.557849] audit: type=1400 audit(1543595468.983:155): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=31991 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Restart browser Nov 30 16:31:13 $HOSTNAME dbus[1899]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name="org.freedesktop.secrets" pid=32646 label="snap.chromium.chromium" peer_pid=1823 peer_label="unconfined" Nov 30 16:31:14 $HOSTNAME kernel: [35221.656759] audit: type=1107 audit(1543595474.083:156): pid=1384 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=32544 label="snap.chromium.chromium" peer_pid=24826 peer_label="unconfined" Nov 30 16:31:23 $HOSTNAME kernel: [35230.641856] audit: type=1400 audit(1543595483.067:157): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=32544 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 30 16:31:23 $HOSTNAME kernel: [35230.660955] audit: type=1400 audit(1543595483.087:158): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c6:0" pid=32544 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Upload to Salesforce case #2 Nov 30 16:31:46 $HOSTNAME kernel: [35253.816946] audit: type=1400 audit(1543595506.243:159): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=32544 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Restart browser Nov 30 16:31:56 $HOSTNAME dbus[1899]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name="org.freedesktop.secrets" pid=938 label="snap.chromium.chromium" peer_pid=1823 peer_label="unconfined" Nov 30 16:31:56 $HOSTNAME kernel: [35264.509009] audit: type=1107 audit(1543595516.935:160): pid=1384 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager"
[Desktop-packages] [Bug 1794354] Re: [snap] emoji show as black and white if fonts-symbola is installed
The snap is now being built on bionic. However the issue can still be observed. What's more, it's not snap-specific. The deb is similarly affected. -- 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/1794354 Title: [snap] emoji show as black and white if fonts-symbola is installed Status in chromium-browser package in Ubuntu: Confirmed Bug description: I'm using the Chromium Snap from the Beta channel. Test Case = 0. Be sure you don't have the Chromium deb running. 1. Visit https://launchpad.net/bugs/1779569 The rainbow emoji should show in color 2. sudo apt install fonts-symbola 3. Close Chromium. Wait a few moments to make sure it closes then open it and repeat step 1 4. The rainbow emoji shows in black and white Other Info == Firefox and GTK apps like gedit correctly show in color as long as fonts-noto-color-emoji is installed, regardless of whether fonts-symbola is also installed. I also was unable to duplicate this bug with the Firefox Snap [edge channel 63.0b9-1 (134)]. System Info === Ubuntu 18.10 fonts-noto-color-emoji 0~20180810-1 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ contact: https://forum.snapcraft.io/ license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: beta refresh-date: 8 days ago, at 13:41 EDT channels: stable:69.0.3497.100 (494) 141MB - candidate: 69.0.3497.100 (494) 141MB - beta: 70.0.3538.16 (487) 142MB - edge: 70.0.3538.9 (472) 142MB - installed: 70.0.3538.16 (487) 142MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1794354/+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 1791307] Re: [snap] GTK theme doesn't match the host system
I confirm bwat47's observation (comment #9). The chrome part of the bug is fixed (except for bug #1800260), but open/save dialogs still don't look good. -- 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/1791307 Title: [snap] GTK theme doesn't match the host system Status in chromium-browser package in Ubuntu: Triaged Bug description: The GTK theme of the chrome and file open/save dialogs doesn't match the theme on the host system. See attached screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1791307/+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 1755119] Re: [snap] GTK dialogs have black corners
The chromium snap has been exclusively built from source for a good while. I just tested again in a bionic VM (X11 and Wayland sessions), and the problem appears to be gone, so I'm closing the bug. Please re-open if you're still seeing this in any configuration. ** Changed in: chromium-browser (Ubuntu) Status: Triaged => Fix Released -- 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/1755119 Title: [snap] GTK dialogs have black corners Status in chromium-browser package in Ubuntu: Fix Released Bug description: (initially reported on the forum: https://forum.snapcraft.io/t/call- for-testing-chromium-65-0-3325-146/4390/10) Observed on version 65.0.3325.146 from the candidate channel. This appears to be specific to the chromium snap, other snaps like libreoffice or gedit don't exhibit this. The corners of GTK dialogs (such as the one to save a page to HTML) are black instead of being transparent, and dialogs don't have shadows. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1755119/+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 1771380] Re: [snap] At first run on bionic, keyboard input is delayed by more than 10 seconds (by fontconfig cache generation)
This was fixed in snapd 2.36.2 (see https://forum.snapcraft.io/t/2-36 -point-releases/9008 and https://github.com/snapcore/snapd/releases/tag/2.36.2). ** Changed in: chromium-browser (Ubuntu) Status: Triaged => Fix Released -- 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/1771380 Title: [snap] At first run on bionic, keyboard input is delayed by more than 10 seconds (by fontconfig cache generation) Status in chromium-browser package in Ubuntu: Fix Released Bug description: This seems to happen only the first time the chromium snap is run after installing it afresh (not after upgrading). Steps to reproduce: 1) $ snap remove chromium # in case it was already installed 2) $ snap install chromium 3) $ snap run chromium 4) wait for the welcome page to be fully loaded, then press Ctrl+L to focus the omnibox (aka address bar) Expected result: the omnibox is instantly focused and its text is selected, key strokes are registered and input into it Current result: there's a long delay before the omnibox is actually focused and its text selected, more than 10 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1771380/+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 1453514] Re: Highlighted text in pdf files is not shown on prints
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1453514 Title: Highlighted text in pdf files is not shown on prints Status in Evince: Unknown Status in evince package in Ubuntu: Confirmed Bug description: Highghted text in pdf files is shown correctly in the viewer, but not in the print preview & the printouts, there only a yellow bar (the highlighting) is visible, and the actual text is behind it (since it is selectable in the print preview). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: evince 3.14.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 10 12:11:42 2015 ExecutablePath: /usr/bin/evince-previewer InstallationDate: Installed on 2015-05-06 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1453514/+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 1599527] Re: Pdf highlightings not printed
*** This bug is a duplicate of bug 1453514 *** https://bugs.launchpad.net/bugs/1453514 ** This bug has been marked a duplicate of bug 1453514 Highlighted text in pdf files is not shown on prints -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1599527 Title: Pdf highlightings not printed Status in evince package in Ubuntu: Confirmed Bug description: If I annotate a pdf with simple text highlightings, those are neither printed on paper, nor shown on the print preview window. I've tried: 1. changing the alpha parameter inside the highlighting settings. Nothing changed on the printed version (no highlighting). 2. Saving the file before printing it, with a different name on a different location. This to be sure that highltightings are saved properly. In fact, they are saved and reloaded when the file is opened, but still nothing shown in the printed paper. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 6 15:46:21 2016 InstallationDate: Installed on 2016-07-05 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1599527/+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 1453514] Re: Highlighted text in pdf files is not shown on prints
** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #624 https://gitlab.gnome.org/GNOME/evince/issues/624 ** Also affects: evince via https://gitlab.gnome.org/GNOME/evince/issues/624 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1453514 Title: Highlighted text in pdf files is not shown on prints Status in Evince: Unknown Status in evince package in Ubuntu: Confirmed Bug description: Highghted text in pdf files is shown correctly in the viewer, but not in the print preview & the printouts, there only a yellow bar (the highlighting) is visible, and the actual text is behind it (since it is selectable in the print preview). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: evince 3.14.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 10 12:11:42 2015 ExecutablePath: /usr/bin/evince-previewer InstallationDate: Installed on 2015-05-06 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1453514/+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 1823361] Re: WeTransfer filelink provider is missing
Quick and dirty test: I copied features/wetrans...@extensions.thunderbird.net.xpi from the upstream official build (thunderbird-60.8.0.tar.bz2) to /usr/lib/thunderbird/distribution/extensions/, and this was enough for thunderbird to pick it up and successfully use it. And unlike other extensions (calendar, see bug #545778), this xpi contains localizations for all available languages. -- 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/1823361 Title: WeTransfer filelink provider is missing Status in thunderbird package in Ubuntu: Triaged Bug description: Upstream builds of thunderbird include the WeTransfer filelink provider. The Ubuntu package doesn't. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.6.1+build2-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-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: osomon 2794 F pulseaudio BuildID: 20190325095516 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 17:05:04 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) InstallationDate: Installed on 2016-07-02 (1006 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325095516 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-03-16 (19 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO 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:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.sku: LENOVO_MT_2306 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1823361/+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 801991] Re: rhythmbox crashes when adding a podcast
Issue now being tracked at: https://gitlab.gnome.org/GNOME/rhythmbox/issues/1073 Does anyone still see a problem when adding a podcast to rhythmbox or can this bug report be closed low? ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #1073 https://gitlab.gnome.org/GNOME/rhythmbox/issues/1073 ** Changed in: rhythmbox Importance: Critical => Unknown ** Changed in: rhythmbox Status: Expired => Unknown ** Changed in: rhythmbox Remote watch: GNOME Bug Tracker #647615 => gitlab.gnome.org/GNOME/rhythmbox/issues #1073 ** Changed in: rhythmbox (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/801991 Title: rhythmbox crashes when adding a podcast Status in Rhythmbox: Unknown Status in rhythmbox package in Ubuntu: Incomplete Bug description: trying to add http://feeds.feedburner.com/linuxoutlaws-ogg Go to Music -> New Podcast Feed... Crash when I click add. gdb backtrace attached ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: rhythmbox 0.13.3-0ubuntu6 ProcVersionSignature: Ubuntu 2.6.38-10.44-generic-pae 2.6.38.7 Uname: Linux 2.6.38-10-generic-pae i686 Architecture: i386 Date: Sat Jun 25 18:42:44 2011 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: Upgraded to natty on 2011-03-15 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/801991/+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 263433] Re: rhythmbox crashes on closing prior to copying a disk in Gnome
Upstream bug was closed "RESOLVED FIXED" on 2012-02-09 after duplicate reports had stopped. Issue refers to a very old version of rhythmbox so closing as fixed. ** Changed in: rhythmbox (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/263433 Title: rhythmbox crashes on closing prior to copying a disk in Gnome Status in Rhythmbox: Fix Released Status in rhythmbox package in Ubuntu: Fix Released Bug description: Binary package hint: rhythmbox Description: Ubuntu 8.04.1 Release: 8.04 rhythmbox: Installed: 0.11.5-0ubuntu8 Candidate: 0.11.5-0ubuntu8 Version table: *** 0.11.5-0ubuntu8 0 500 http://gb.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 0.11.5-0ubuntu6 0 500 http://gb.archive.ubuntu.com hardy/main Packages I wanted to make a copy of an audio disc so I put the disc into my drive. Rhythmbox auto-launched, but I immediately closed it so as to choose "Copy disc" from the disc icon my desktop. A few seconds after the disc copy operation started, I get the Rhythmbox crash. ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/rhythmbox NonfreeKernelModules: nvidia Package: rhythmbox 0.11.5-0ubuntu8 ProcAttrCurrent: unconfined ProcCmdline: rhythmbox cdda://scd0/ ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /usr/lib/libglib-2.0.so.0 ?? () from /usr/lib/librhythmbox-core.so.0 ?? () from /usr/lib/librhythmbox-core.so.0 ?? () from /usr/lib/librhythmbox-core.so.0 rhythmdb_entry_set_internal () Title: rhythmbox crashed with SIGSEGV in rhythmdb_entry_set_internal() Uname: Linux 2.6.24-19-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/263433/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
@Kreaninw, please test this dkms, to install this dkms: sudo dpkg -i oem-audio-hda-daily-dkms_0.1_all.deb reboot #test if the internal mic works or not, if not, please also upload an alsa-info.txt to remove the dkms: sudo dpkg -r oem-audio-hda-daily-dkms reboot ** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+attachment/5281430/+files/oem-audio-hda-daily-dkms_0.1_all.deb -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
Hi, @Hui Wang ** Attachment added: "alsa-info.txt.jkhDO3jo0p" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+attachment/5281410/+files/alsa-info.txt.jkhDO3jo0p -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1838912] Re: Bluetooth doesn't remember my Logitech MX Master mouse.
gnome-control-center is only a configuration UI and doesn't include any service, it's not involved in reconnecting devices. Reassigning to bluez Could you include a 'journalctl -b 0' log after getting the issue? Could you also provide the bluetoothctl info for the device as explained on https://wiki.ubuntu.com/DebuggingBluetooth ? ** Package changed: gnome-control-center (Ubuntu) => bluez (Ubuntu) ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1838912 Title: Bluetooth doesn't remember my Logitech MX Master mouse. Status in bluez package in Ubuntu: Incomplete Bug description: I can pair my mouse, and sometimes Ubuntu will remember it, but more often it doesn't automatically connect when I turn the computer on or wake it up. I've noticed that it'll have the same BT address, so it should connect (?). When it DOES connect, it's when I've had the mouse turned off and don't turn it on until Ubuntu is completely awake and running. That doesn't always work, but if I have the mouse turned on before turning Ubuntu on, then it never connects. I have to re-pair them. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 18:40:38 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-01 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838912/+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 1750243] Re: [snap] StartupWMClass missing in .desktop file
Fixed with https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from- source/commit/?id=02e1a3b458a1edef2307278880337e8e494d5569. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Committed -- 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/1750243 Title: [snap] StartupWMClass missing in .desktop file Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Chromium Snap Version 64.0.3282.167 How to reproduce: In Gnome: Add the Chromium Snap to the left launcher panel. Start the Chromium Snap. Actual behavior: The Chromium snap starts and creates a new symbol in the launcher panel. Desired behavior: The Chromium snap should start using the symbol which is already pinned to the launcher panel. In Budgie: The Chromium Snap cannot be pinned to the panel at all. Possible solution: Add StartupWMClass= ... to the .desktop launcher of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1750243/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
Please upload the alsa-info.txt generated on your machine. $alsa-info --no-upload then upload the generated alsa-info.txt from /tmp/alsa-info.txt. -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1750243] Re: [snap] StartupWMClass missing in .desktop file
I tested again, and while I can confirm that the chromium snap cannot be pinned to the favorite apps in a Fedora 29 VM without the "StartupWMClass=chromium" line in its desktop file, Ubuntu doesn't seem to be affected. I tested bionic and eoan, in the alternative gnome- session, which has defaults similar to Fedora. I dug a bit in gnome-shell's code to try and understand why it's needed in Fedora and not in Ubuntu in the first place. In get_app_from_window_wmclass(): /* first try a match from WM_CLASS (instance part) to StartupWMClass */ /* then try a match from WM_CLASS to StartupWMClass */ /* then try a match from WM_CLASS (instance part) to .desktop */ /* finally, try a match from WM_CLASS to .desktop */ The first two attempts will fail when there's no StartupWMClass. The last two attempts would try to match, respectively, "chromium" (instance) and "Chromium" (class name) to a desktop file name. I'm not sure by which magic that would match against "chromium_chromium.desktop" (which is the name of the desktop file installed by the snap). In this light, adding StartupWMClass to the desktop file looks correct, and won't hurt the existing matching logic on desktops where it already works. ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium -- 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/1750243 Title: [snap] StartupWMClass missing in .desktop file Status in chromium-browser package in Ubuntu: Confirmed Bug description: Chromium Snap Version 64.0.3282.167 How to reproduce: In Gnome: Add the Chromium Snap to the left launcher panel. Start the Chromium Snap. Actual behavior: The Chromium snap starts and creates a new symbol in the launcher panel. Desired behavior: The Chromium snap should start using the symbol which is already pinned to the launcher panel. In Budgie: The Chromium Snap cannot be pinned to the panel at all. Possible solution: Add StartupWMClass= ... to the .desktop launcher of the chromium snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1750243/+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 1817537] Re: libsoup should support ntlmv2
Thanks Shawn, I'm going to mark it as verified since it's an improvement and resolve some cases. It looks like more work is needed but there is no reason to block the current round on that, we can reopen and look to cases still not working then. Lars, maybe it would be a good idea to report the issue also upstream on https://gitlab.gnome.org/GNOME/evolution-exchange if you could do that ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 Status in libsoup2.4 package in Ubuntu: Fix Released Status in libsoup2.4 source package in Bionic: Fix Committed Bug description: * Impact Without NTLMv2 support evolution-ews can't connect to some exchange servers * Test case Try connecting from evolution-ews to an exchange server which enforces NTLMV2 * Regression potential The change adds extra cases in the ntlm handling support, it should impact existing feature but check out for any potential regression in libsoup user (check at least evolution and epiphany-browser). Note that the patch include additional code tests --- Our Exchange admins recently made NTLMv2 obligatory. Since then interaction with Exchange through Evolution isn't possible anymore. In newer versions of libsoup that has been implemented, see https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 Could that be backported to Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsoup2.4-1 2.62.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 25 12:10:26 2019 SourcePackage: libsoup2.4 UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+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 1839322] Re: Logitech G920 is unusable with Ubuntu 16.04
Bug confirmed on Dell Latitude Inspiron 15 7000 Gaming Laptop with Ubuntu 16.04 factory installed. Upgrading to Ubuntu 18.04 resolve the issue, but introduces new bugs related to Nvidia driver and xorg/wayland. Not a good solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1839322 Title: Logitech G920 is unusable with Ubuntu 16.04 Status in usb-modeswitch package in Ubuntu: New Bug description: Version 2.2.5 supplied with Ubuntu 16.04 does not have support to Logitech G920 racing wheel, rendering it unusable. This device is in Xbox mode by default, needing a switch to HID mode to work. The symtoms are: - The device is in 0xFF (vendor) mode after usb cable is plugged in; - The device has an id product of 0xc261 (for Xbox); - The racing wheel keeps calibrating forever, turning left and right by itself with no calibration completion (the device is resetted every time, wich impares the ending of calibration process). The solution for this bug is to update the usb-modeswitch package to the version supplied with Ubuntu 18.04, wich solves the problem. More info on this issue can be found below: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=2=2510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1839322/+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 1839322] [NEW] Logitech G920 is unusable with Ubuntu 16.04
Public bug reported: Version 2.2.5 supplied with Ubuntu 16.04 does not have support to Logitech G920 racing wheel, rendering it unusable. This device is in Xbox mode by default, needing a switch to HID mode to work. The symtoms are: - The device is in 0xFF (vendor) mode after usb cable is plugged in; - The device has an id product of 0xc261 (for Xbox); - The racing wheel keeps calibrating forever, turning left and right by itself with no calibration completion (the device is resetted every time, wich impares the ending of calibration process). The solution for this bug is to update the usb-modeswitch package to the version supplied with Ubuntu 18.04, wich solves the problem. More info on this issue can be found below: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=2=2510 ** Affects: usb-modeswitch (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Logitech G920 is unusable + Logitech G920 is unusable with Ubuntu 16.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1839322 Title: Logitech G920 is unusable with Ubuntu 16.04 Status in usb-modeswitch package in Ubuntu: New Bug description: Version 2.2.5 supplied with Ubuntu 16.04 does not have support to Logitech G920 racing wheel, rendering it unusable. This device is in Xbox mode by default, needing a switch to HID mode to work. The symtoms are: - The device is in 0xFF (vendor) mode after usb cable is plugged in; - The device has an id product of 0xc261 (for Xbox); - The racing wheel keeps calibrating forever, turning left and right by itself with no calibration completion (the device is resetted every time, wich impares the ending of calibration process). The solution for this bug is to update the usb-modeswitch package to the version supplied with Ubuntu 18.04, wich solves the problem. More info on this issue can be found below: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=2=2510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1839322/+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 144334] Re: Rythmbox should scan for new music on start by default
Upstream issue now being tracked at: https://gitlab.gnome.org/GNOME/rhythmbox/issues/219 ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #219 https://gitlab.gnome.org/GNOME/rhythmbox/issues/219 ** Changed in: rhythmbox Importance: Medium => Unknown ** Changed in: rhythmbox Status: Expired => Unknown ** Changed in: rhythmbox Remote watch: GNOME Bug Tracker #349924 => gitlab.gnome.org/GNOME/rhythmbox/issues #219 ** Changed in: hundredpapercuts Status: Confirmed => Triaged ** Changed in: hundredpapercuts Importance: Low => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/144334 Title: Rythmbox should scan for new music on start by default Status in One Hundred Papercuts: Triaged Status in Rhythmbox: Unknown Status in rhythmbox package in Ubuntu: Triaged Bug description: For the sake of usability, Rhythmbox should have the preference option of "Watch my library for new files" enabled by default so people do not have to remember to re-import their collection. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/144334/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
Same problem on Thinkpad T470s with 19.04. Is this a problem on other distros too? I need my microphone to work... -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 246981] Re: drag and drop to nautilus desktop places icons in random spot
Upstream bug #513508 was closed "RESOLVED OBSOLETE" on 2018-01-02 as from version 3.28 nautilus no longer handles files on desktop. Papercuts task did not expire due to bug watch so closing now. ** Changed in: hundredpapercuts Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/246981 Title: drag and drop to nautilus desktop places icons in random spot Status in One Hundred Papercuts: Invalid Status in Nautilus: Expired Status in nautilus package in Ubuntu: Invalid Bug description: Binary package hint: file-roller When extracting something to the desktop from file-roller using drag'n'drop, the item is not placed where the mouse cursor was when the mouse button is raised but at a random spot. This is happening for me on hardy. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/246981/+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 1839253] Re: Excessive screen tearing and flickering
libgl1-mesa-glx is a transitional pkg these days -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1839253 Title: Excessive screen tearing and flickering Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 02:06:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] InstallationDate: Installed on 2019-08-06 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5201 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:56b9 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA 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-23-generic root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.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/xserver-xorg-video-intel/+bug/1839253/+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 1236983] Re: Possible security expoit using special characters to manipulate displayed filename.
It still works on Ubuntu Eoan, so not fixed yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1236983 Title: Possible security expoit using special characters to manipulate displayed filename. Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: Use of special characters can be used to manipulate a filename extension in Nautilus. We received a piece of malware with a filename that appears differently with Nautilus than on the command line using ls. With Nautilus we see: NO.00123Order# POrcs.pdf With ls in bash we see: NO.00123Order# POfdp.scr Using od the special characters are revealed as: ronp@ron:~/Desktop/virus$ ls *scr | od -c 000 N O . 0 0 1 2 3 O r d e r # P 020 O 342 200 256 f d p . s c r \n 034 Before extraction from the archive, the file appears with question marks as follows: NO.00123Order# PO???fdp.scr Perhaps this would be a more secure way to display the file in Nautaulis revealing the true nature of the file; scr instead of pdf. This occurred with Nautilus 3.4.2 on Ubuntu 12.10 and Nautilus 3.6.3 on Ubuntu 13.04 We note this type of exploit has been used before: https://kc.mcafee.com/resources/sites/MCAFEE/content/live/PRODUCT_DOCUMENTATION/23000/PD23930/en_US/McAfee_Labs_Threat_Advisory_XDocCrypt.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1236983/+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 1833798] Re: no restore after update when multiple profiles in use
This sounds very similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1274846. ** Bug watch added: Mozilla Bugzilla #1274846 https://bugzilla.mozilla.org/show_bug.cgi?id=1274846 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1274846 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/1833798 Title: no restore after update when multiple profiles in use Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: New Bug description: When Firefox is ready to force use of a new update, it displays in a tab a message: "Sorry. We just need to do one small thing to keep going. Firefox has just been updated in the background. Click Restart Firefox to complete the update. We will restore all your pages, windows and tabs afterwards, so you can be on your way quickly." However when I am using multiple profiles concurrently, after I click on the "Restart Firefox" button, a window for the profile that received the message does not get restarted after it has been closed and the update for that profile activated. Instead the profile has to be restarted manually as do all of the tabs that were open at the time in that profile. (Note: I typically get this message one profile at a time. The other open profiles are not immediately affected.) I expected that Firefox would restore the one window for the profile that was closed and restore all of the tabs to their previous URL, if not their previous state. Most recently this happened to me as Firefox started updating from 67.0.2 to 67.0.3, but it has been a problem with earlier versions as well. Unfortunately, because this is initiated by the availability of a new Firefox update, I do not have instructions on how to reproduce this problem on demand. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 67.0.3+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: circ 2588 F pulseaudio /dev/snd/controlC0: circ 2588 F pulseaudio /dev/snd/pcmC2D0p: circ 2588 F...m pulseaudio /dev/snd/controlC2: circ 2588 F pulseaudio BuildID: 20190618131358 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jun 21 17:36:55 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1151 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-11 (222 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.3.1 dev enp3s0 proto dhcp metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.3.0/24 dev enp3s0 proto kernel scope link src 192.168.3.181 metric 100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1151 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1151 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1151 Profile3PrefSources: prefs.js Profile3Themes:
[Desktop-packages] [Bug 1839304] Re: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1839304 Title: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Don't know much about it. It just came up. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: tnef: Install tex-common: Configure lmodern: Configure tnef: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 6 20:36:49 2019 DpkgHistoryLog: Start-Date: 2019-08-06 20:36:35 Commandline: apt-get install tnef Requested-By: drshred (1000) Install: tnef:amd64 (1.4.12-1.2) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-05-04 (2651 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-11-22 (258 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1839304/+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 1839304] [NEW] package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Don't know much about it. It just came up. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: tnef: Install tex-common: Configure lmodern: Configure tnef: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 6 20:36:49 2019 DpkgHistoryLog: Start-Date: 2019-08-06 20:36:35 Commandline: apt-get install tnef Requested-By: drshred (1000) Install: tnef:amd64 (1.4.12-1.2) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-05-04 (2651 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-11-22 (258 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1839304 Title: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Don't know much about it. It just came up. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: tnef: Install tex-common: Configure lmodern: Configure tnef: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 6 20:36:49 2019 DpkgHistoryLog: Start-Date: 2019-08-06 20:36:35 Commandline: apt-get install tnef Requested-By: drshred (1000) Install: tnef:amd64 (1.4.12-1.2) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-05-04 (2651 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: tex-common Title: package tex-common 6.09 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-11-22 (258 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1839304/+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 1838965] Re: Screen tearing in Firefox on Wayland
The tearing isn't obvious to my untrained eye, nor can I observe it locally when testing in VMs. I tested both X11 and Wayland, by scrolling up and down a long wikipedia page. Can you provide details about your graphics card and driver? Can you test an upstream build (download and unpack https://www.mozilla.org/firefox/download/thanks/) and confirm whether it's similarly affected? If so, can you file an upstream bug at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox and share the link to it here? Thanks! ** 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/1838965 Title: Screen tearing in Firefox on Wayland Status in firefox package in Ubuntu: Incomplete Bug description: Details here: https://photos.app.goo.gl/9kA7R6KqNaSsn9CB8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 68.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BuildID: 20190719083815 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 13:36:32 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.0.1/20190719083815 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838965/+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 1839030] Re: Artifacts appears when Chromium app is minimizing
I'm seeing something similar to the screencast, on 19.04, using the chromium snap, in the default X11 session. This is not minimizing, but un-maximizing the window. Can you confirm that the problem is that the address bar is sometimes not redrawn instantly when un-maximizing the window? -- 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/1839030 Title: Artifacts appears when Chromium app is minimizing Status in chromium-browser package in Ubuntu: New Bug description: Details here: https://photos.app.goo.gl/ummEcpamq3yYA7p38 Device: Ubuntu 19.10 on Wayland (last build for 5 August 2019), HP 250 G6 Notebook, Celeron N3350 (Apollo Lake), Intel HD 500. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839030/+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 1839030] Re: Artifacts appears when Chromium app is minimizing
Interestingly, I can't reproduce the problem in an up-to-date 19.10 VM, in the default X11 session. Can you test whether Google Chrome (not chromium) is similarly affected? If so, would you mind filing an upstream bug report at https://chromiumbugs.appspot.com and linking to it here? Thanks! -- 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/1839030 Title: Artifacts appears when Chromium app is minimizing Status in chromium-browser package in Ubuntu: New Bug description: Details here: https://photos.app.goo.gl/ummEcpamq3yYA7p38 Device: Ubuntu 19.10 on Wayland (last build for 5 August 2019), HP 250 G6 Notebook, Celeron N3350 (Apollo Lake), Intel HD 500. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839030/+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 1839217] Re: Bad user experience choosing partition labels
In which Ubuntu and gnome-disks-utility version are you running? Gnome disks does not give me an error message when formatting a FAT32 partition with the labels being lower case. Tried mixed case, and all lower case. None of them gave me an error message. Tested in Ubuntu Eoan Ermine with gnome-disks-utility 3.32.1-1ubuntu1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1839217 Title: Bad user experience choosing partition labels Status in gnome-disk-utility package in Ubuntu: New Bug description: For FAT partitions, labels have to be upper case. FAT is the default for a new partition, but the default example label is mixed case. This means just going on recommendation, it's not going to work out, and the user will get an error message. A better user experience would be to simply tell the user that their label will be made upper case, and ask them to confirm with yes/no. Or just do it without asking TBH because I think upper-casing it by default is a pretty harmless thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839217/+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 1838963] Re: Firefox window initially appears black when launching on Wayland
And I am seeing the same issue in a fully up-to-date Fedora 29 VM (defaults to Wayland session). So this isn't an Ubuntu-specific problem. -- 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/1838963 Title: Firefox window initially appears black when launching on Wayland Status in firefox package in Ubuntu: Confirmed Bug description: Details here: https://photos.app.goo.gl/2CjpJGB1wEWU8qJw6 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 68.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BuildID: 20190719083815 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 13:24:46 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.0.1/20190719083815 SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838963/+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 1839136] Re: Temporary freeze / delay with some dialog windows
** Description changed: Some dialog popups take a while to open, as if the system froze for a bit (even though journalctl -f doesn't show anything related) which is extremely annoying. Example: - the dialog shown if a file should be saved when trying to close a tab in Gedit - the popup confirmation dialog when using Shift + Delete in Nautilus - the dialog shown when trying to close a terminal that has a running process This does not happen every time, but I'm not sure what triggers it. I made a video showcasing the issue: https://streamable.com/xqjlf The first time I try to close a Gedit unsaved tab this issue happens, but the second time it does not happen. What I tried and did not solve this issue: - using modal or detached dialogs - disabling all Gnome Shell extensions (including those that ship with Ubuntu by default, by removing the packages) This seems related to using multiple monitors. I have two monitors, one - using 2560x1080 resolution, and the other 19220x1080 (both with the + using 2560x1080 resolution, and the other 1920x1080 (both with the default 100% scalx). When I mirrored the displays, this issue no longer happened. It only happens with extended (using the "Join Displays" option) display. To replicate, just click (focus) on other windows multiple times (on both monitors), then go to the window that causes these issues and it should happen, like I explained. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 14:10:26 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-10-17 (292 days ago) ** Description changed: Some dialog popups take a while to open, as if the system froze for a bit (even though journalctl -f doesn't show anything related) which is extremely annoying. Example: - the dialog shown if a file should be saved when trying to close a tab in Gedit - the popup confirmation dialog when using Shift + Delete in Nautilus - the dialog shown when trying to close a terminal that has a running process This does not happen every time, but I'm not sure what triggers it. I made a video showcasing the issue: https://streamable.com/xqjlf The first time I try to close a Gedit unsaved tab this issue happens, but the second time it does not happen. What I tried and did not solve this issue: - using modal or detached dialogs - disabling all Gnome Shell extensions (including those that ship with Ubuntu by default, by removing the packages) This seems related to using multiple monitors. I have two monitors, one using 2560x1080 resolution, and the other 1920x1080 (both with the - default 100% scalx). When I mirrored the displays, this issue no longer + default 100% scale). When I mirrored the displays, this issue no longer happened. It only happens with extended (using the "Join Displays" option) display. To replicate, just click (focus) on other windows multiple times (on both monitors), then go to the window that causes these issues and it should happen, like I explained. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 14:10:26 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-10-17 (292 days ago) -- 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/1839136 Title: Temporary freeze / delay with some dialog windows Status in gnome-shell package in Ubuntu: New Bug description: Some dialog popups take a while to open, as if the system froze for a bit (even though journalctl -f doesn't show anything related) which is extremely annoying. Example: - the dialog shown if a file should be saved when trying to close a tab in Gedit - the popup confirmation dialog when using Shift + Delete in Nautilus - the dialog shown when trying to close a terminal that has a running process This does not happen every time, but I'm not sure what triggers it. I made a video showcasing the issue: https://streamable.com/xqjlf The first time I try to close a Gedit unsaved tab this issue happens, but the second time it
[Desktop-packages] [Bug 1838963] Re: Firefox on Wayland opens with black screen
I can reliably observe the problem, on disco and eoan. Tested both the Ubuntu packages from the archive, and the upstream build. Would you mind filing an upstream bug report at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox and sharing the link to it here? Thanks! ** Summary changed: - Firefox on Wayland opens with black screen + Firefox window initially appears black when launching on Wayland ** Changed in: firefox (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1838963 Title: Firefox window initially appears black when launching on Wayland Status in firefox package in Ubuntu: Confirmed Bug description: Details here: https://photos.app.goo.gl/2CjpJGB1wEWU8qJw6 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 68.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BuildID: 20190719083815 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 13:24:46 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.0.1/20190719083815 SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838963/+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 1830748] Re: Pressing scrollbar makes it sticky
Please execute the following command in a terminal to attach additional debug information to the bug report: apport-collect 1830748 Also, please elaborate on what you mean by "Pressing scrollbar" and "sticky". I can use scrollbars in chromium just fine here. Thanks! ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1830748 Title: Pressing scrollbar makes it sticky Status in chromium-browser package in Ubuntu: Incomplete Status in Fedora: Unknown Bug description: Pressing scrollbar in any situation makes it sticky. Restart does not help. >:] The only workaround is to delete image cache and then restart the browser. This is a nice bug in sense that then you fix it browser becomes really smooth. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1830748/+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 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
Aside from the chromium upstream bug (https://bugs.chromium.org/p/chromium/issues/detail?id=627143), I'm not seeing any issue with the rendering of Ubuntu Light: - libreoffice renders text correctly when using the Ubuntu font and setting the character style to light - firefox and epiphany (web) render Iain's test page (comment #14) as expected I have tested on disco (19.04) and eoan (19.10). I have a limited understanding of how fonts work, but the chromium issue doesn't appear to be caused by font metadata, rather by an incorrect implementation of the W3C spec. @Harry, are there other problems with the rendering of Ubuntu Light? ** Changed in: chromium-browser (Ubuntu) Assignee: Olivier Tilloy (osomon) => (unassigned) ** Changed in: fonts-ubuntu (Ubuntu) Status: In Progress => Incomplete ** Changed in: hundredpapercuts Status: In Progress => Incomplete ** Changed in: ubuntu-font-family Status: In Progress => Incomplete -- 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/1512111 Title: "Ubuntu Light" font has heavier weight than "Ubuntu" Status in One Hundred Papercuts: Incomplete Status in Ubuntu Font Family: Incomplete Status in chromium-browser package in Ubuntu: Confirmed Status in fonts-ubuntu package in Ubuntu: Incomplete Bug description: After upgrading from Vivid to Wily, pages using the "Ubuntu light" font actually renders with a weight heavier than the regular one in web pages. This happens with Chrome/Chromium and also the Ubuntu browser. After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in place of 0.83-0ubuntu1), the issue is fixed. See the attached screenshot showing the result seen browing https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 1 17:55:19 2015 Dependencies: InstallationDate: Installed on 2014-10-14 (382 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago) IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users which impacts the usability and visual design. The new version of font package (0.831) corrects the relationship between Light and Medium weight to follow the commonly used naming standards: Ubuntu Light Light Light Italic UbuntuRegular Italic BoldBold Italic Ubuntu Medium Medium Medium Italic Ubuntu Condensed Regular Ubuntu Mono Regular Italic BoldBold Italic TEST CASE: in 15.10, go to https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu If the Light weight renders heavier than Normal weight, the bug is in place REGRESSION POTENTIAL 0.831 was tested by manually running in 15.10 and no regression was noticed, while the bug was fixed. The potential for regression is small. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+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 1831384] Re: .desktop files not working in Ubuntu 19.04 Gnome
Could you report it upstream on https://gitlab.gnome.org/GNOME/gnome- shell/issues ? -- 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/1831384 Title: .desktop files not working in Ubuntu 19.04 Gnome Status in gnome-shell package in Ubuntu: New Bug description: I use several instances of Firefox, that I usually launch from various launchers. For example, I have a `firefox-test.desktop` file in `~/.local/share/applications`, that contains: ``` [Desktop Entry] Version=1.0 Name=Firefox-Test StartupWMClass=firetest Exec=firefox --new-instance --no-remote -P Test --class firetest %u Icon=firefox-developer-icon Terminal=false Type=Application MimeType=text/html;text/xml;application/xhtml+xml;application/vnd.mozilla.xul+xml;text/mml;x-scheme-handler/http;x-scheme-handler/https; StartupNotify=true Categories=Network;WebBrowser; Keywords=web;browser;internet;pentest; Actions=new-window;new-private-window; ``` It worked for ages, in many DE, including GNOME in 18.04. But, in 19.04, clicking on my launchers does nothing. On the other hand, the commands works from the terminal: ``` firefox --new-instance --no-remote -P Test --class firetest ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831384/+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 1838868] Re: Desktop Bookmark from sidebar is removed and user-dirs.dirs config not working.
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1838868 Title: Desktop Bookmark from sidebar is removed and user-dirs.dirs config not working. Status in nautilus package in Ubuntu: New Bug description: All of a sudden I found that the Desktop bookmark from Nautilus's sidebar is removed. Please check the image bellow. https://raw.githubusercontent.com/devKamrul007/Nautilus-Bug- images/eaf3ef9517d4aa63e49dff4fc58ee49279e67a36/Screenshot%20from%202019-08-04%2013-42-44.png There is no desktop under Home. Moreover, I tried to fix the problem by editing ~/.config/user-dirs.dirs like bellow image. But, this seems to has no effect at all. https://raw.githubusercontent.com/devKamrul007/Nautilus-Bug- images/eaf3ef9517d4aa63e49dff4fc58ee49279e67a36/Screenshot%20from%202019-08-04%2013-29-43.png I am using Ubuntu 19.04 Disco Dingo latest 5.0.0-23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1838868/+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 1839010] Re: Touchpad does not work after installing Ubuntu
Thank you for your bug report. Could you add a 'journalctl -b 0' and 'sudo libinput-list-devices' logs to the bug? ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1839010 Title: Touchpad does not work after installing Ubuntu Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I previously had Windows 10 on my protab laptop. After wiping the hard drive and installing Ubuntu 19.04 on the device, the touchpad ceases to respond at all. I am using an external mouse currently. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:39:36 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+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 1838604] Re: cannot close nautilus windows
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1838604 Title: cannot close nautilus windows Status in nautilus package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 apt-cache policy nautilus nautilus: Installed: 1:3.32.1-0ubuntu0.19.04.0 Candidate: 1:3.32.1-0ubuntu0.19.04.0 Version table: *** 1:3.32.1-0ubuntu0.19.04.0 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.32.0-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages Right click quit 2 windows = windows remain open click on close individual window = window remains open WORSE, none of the contents in the folders are available. Mouse clicks do NOT respond in any of the open Nautilus windows. I can open other windows but if directory Z is not responding then I cannot open another instance of directory Z! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 08:30:38 2019 InstallationDate: Installed on 2015-08-23 (1438 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-24 (98 days ago) usr_lib_nautilus: dropbox 2019.02.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1838604/+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 1839253] Re: Excessive screen tearing and flickering
Note also the 'intel' driver for Xorg is deprecated. You should be using the default 'modesetting' driver for the best experience. If you can then please go back to using that, not 'intel'. ** Package changed: ubuntu => xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1839253 Title: Excessive screen tearing and flickering Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 02:06:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] InstallationDate: Installed on 2019-08-06 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5201 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:56b9 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA 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-23-generic root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.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/xserver-xorg-video-intel/+bug/1839253/+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 1839174] Re: Xorg crashes in stdio functions under pci_device_vgaarb_set_target() from VGAGet() from VGAarbiterSpriteMoveCursor()
If you want the fix and still want to stick with version 18.04 then you should get it by installing 18.04.2 instead: http://releases.ubuntu.com/18.04/ Alternatively you can install the HWE packages, but I don't have instructions prepared for how to do that reliably. -- 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/1839174 Title: Xorg crashes in stdio functions under pci_device_vgaarb_set_target() from VGAGet() from VGAarbiterSpriteMoveCursor() Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server source package in Disco: Fix Released Status in xorg-server source package in Eoan: Fix Released Bug description: Issue xorg crashes, there doesn't seem to be any repeatable cause, it'll happen just watching hulu or youtube, it'll happen when using citrix, or when playing steam games. Steps to reproduce use xorg for a while Expected behaviour not crashing Other information issue only happens when using pci-e passthrough to qemu virtual machines Has been an issue since setting up pci-e passthrough, have reinstalled Linux Mint (from XFCE version) but error persists, have changed numerous bios settings without having an impact Upgraded bios to most recent version, also reset bios to factory defaults, didn't make a difference Tried latest Linux 5.x kernels from uuku, same issue The virtual machine doesn't have any problems, it never crashes and stays running when the host os xorg crashes. System:Host: drac Kernel: 4.15.0-55-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.2.3 Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic Machine: Type: Server System: Supermicro product: Super Server v: 0123456789 serial: Mobo: Supermicro model: X10SRL-F v: 1.01B serial: UEFI: American Megatrends v: 3.1c date: 05/02/2019 Graphics: Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Micro-Star MSI driver: nvidia v: 430.34 bus ID: 03:00.0 Device-2: NVIDIA GK104 [GeForce GTX 770] vendor: eVga.com. driver: vfio-pci v: 0.2 bus ID: 04:00.0 Device-3: ASPEED Graphics Family vendor: Super Micro driver: ast v: kernel bus ID: 0b:00.0 Display: x11 server: X.Org 1.19.6 driver: nvidia resolution: 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 430.34 direct render: Yes CPU: Topology: 6-Core model: Intel Xeon E5-1650 v4 bits: 64 type: MT MCP arch: Broadwell rev: 1 L2 cache: 15.0 MiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 86397 Speed: 1203 MHz min/max: N/A Core speeds (MHz): 1: 1203 2: 1206 3: 1330 4: 1200 5: 1201 6: 1201 7: 1200 8: 1200 9: 2046 10: 1202 11: 1202 12: 1201 Not using PPA builds Linux Mint 19.2 (Upgraded from 19.1) 64bit root@drac:/vms# apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 1070GTX - NVIDIA-Linux-x86_64-430.34.run Left screen is a 60hz monitor, right screen is a 120hz monitor Also have a 770GTX bound to vfio for virtual machine passthrough Previously used the PPA from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa, but changed to Nvidia's .run to see if it made a different - it did not. [xsession-errors.old.upload.txt](https://github.com/linuxmint/cinnamon/files/3471789/xsession-errors.old.upload.txt) [xsession-errors.upload.txt](https://github.com/linuxmint/cinnamon/files/3471791/xsession-errors.upload.txt) [lspci.txt](https://github.com/linuxmint/cinnamon/files/3471859/lspci.txt) Syslog: [kernel.log.txt](https://github.com/linuxmint/cinnamon/files/3471804/kernel.log.txt) Grub: having mitigations on or off makes no difference GRUB_CMDLINE_LINUX_DEFAULT="intel_idle.max_cstate=1 drm.debug=14 log_buf_len=16M mitigations=on intel_iommu=on vfio-pci.ids=8086:8d26,10de:1184,10de:0e0a modprobe.blacklist=snd_hda_intel,snd_hda_core,snd_hda_codec,snd_hda_codec_hdmi,nouveau" Xorg crashdump traces: /var/crash/usr_lib_xorg_Xorg.0.crash Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -noliste'. Program terminated with signal SIGSEGV, Segmentation fault. #0
[Desktop-packages] [Bug 1839253] [NEW] Excessive screen tearing and flickering
You have been subscribed to a public bug: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 02:06:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] InstallationDate: Installed on 2019-08-06 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5201 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:56b9 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA 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-23-generic root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.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: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug disco ubuntu -- Excessive screen tearing and flickering https://bugs.launchpad.net/bugs/1839253 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839068] Re: Wrong password every time after changing login password
Thank you for your bug report, when using passwd to change your password the pam stack should update the keyring one as well, unsure why that's not working for you. Could you add your 'journalctl -b 0' log after a password change? ** Changed in: seahorse (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1839068 Title: Wrong password every time after changing login password Status in seahorse package in Ubuntu: New Bug description: After changing password with "passwd" command it's not possible to open the keyring anymore. Each time I have the dialog that open asking me for the password. I've tried to enter the old password and the new password but nothing changes. I've changed back the login password to the old one but even in that case the seahorse password dialog opens saying that the login password doesn't matches the keyring password and asking me to enter it again. I need a procedure to change the keyring password without login into the seahorse, so that it can match the login password of Ubuntu. Ubuntu 18.04.2 LTS Seahorse 3.20.0-5 from http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1839068/+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 1839253] Re: Excessive screen tearing and flickering
These lines suggest some graphics-related packages are missing: (II) GLX: Initialized DRISWRAST GL provider for screen 0 version.libgl1-mesa-glx: libgl1-mesa-glx N/A Please run: dpkg -l > allpackages.txt and then attach the file 'allpackages.txt'. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1839253 Title: Excessive screen tearing and flickering Status in Ubuntu: Incomplete Bug description: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 02:06:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] InstallationDate: Installed on 2019-08-06 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5201 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:56b9 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA 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-23-generic root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.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/+bug/1839253/+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 1839174] Re: Xorg crashes in stdio functions under pci_device_vgaarb_set_target() from VGAGet() from VGAarbiterSpriteMoveCursor()
the issue doesn't seem common enough to justify a SRU in the non hwe version at this point so setting that one as wontfix ** Changed in: xorg-server (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: xorg-server (Ubuntu Bionic) Status: Confirmed => Won't Fix -- 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/1839174 Title: Xorg crashes in stdio functions under pci_device_vgaarb_set_target() from VGAGet() from VGAarbiterSpriteMoveCursor() Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server source package in Disco: Fix Released Status in xorg-server source package in Eoan: Fix Released Bug description: Issue xorg crashes, there doesn't seem to be any repeatable cause, it'll happen just watching hulu or youtube, it'll happen when using citrix, or when playing steam games. Steps to reproduce use xorg for a while Expected behaviour not crashing Other information issue only happens when using pci-e passthrough to qemu virtual machines Has been an issue since setting up pci-e passthrough, have reinstalled Linux Mint (from XFCE version) but error persists, have changed numerous bios settings without having an impact Upgraded bios to most recent version, also reset bios to factory defaults, didn't make a difference Tried latest Linux 5.x kernels from uuku, same issue The virtual machine doesn't have any problems, it never crashes and stays running when the host os xorg crashes. System:Host: drac Kernel: 4.15.0-55-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.2.3 Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic Machine: Type: Server System: Supermicro product: Super Server v: 0123456789 serial: Mobo: Supermicro model: X10SRL-F v: 1.01B serial: UEFI: American Megatrends v: 3.1c date: 05/02/2019 Graphics: Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Micro-Star MSI driver: nvidia v: 430.34 bus ID: 03:00.0 Device-2: NVIDIA GK104 [GeForce GTX 770] vendor: eVga.com. driver: vfio-pci v: 0.2 bus ID: 04:00.0 Device-3: ASPEED Graphics Family vendor: Super Micro driver: ast v: kernel bus ID: 0b:00.0 Display: x11 server: X.Org 1.19.6 driver: nvidia resolution: 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 430.34 direct render: Yes CPU: Topology: 6-Core model: Intel Xeon E5-1650 v4 bits: 64 type: MT MCP arch: Broadwell rev: 1 L2 cache: 15.0 MiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 86397 Speed: 1203 MHz min/max: N/A Core speeds (MHz): 1: 1203 2: 1206 3: 1330 4: 1200 5: 1201 6: 1201 7: 1200 8: 1200 9: 2046 10: 1202 11: 1202 12: 1201 Not using PPA builds Linux Mint 19.2 (Upgraded from 19.1) 64bit root@drac:/vms# apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 1070GTX - NVIDIA-Linux-x86_64-430.34.run Left screen is a 60hz monitor, right screen is a 120hz monitor Also have a 770GTX bound to vfio for virtual machine passthrough Previously used the PPA from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa, but changed to Nvidia's .run to see if it made a different - it did not. [xsession-errors.old.upload.txt](https://github.com/linuxmint/cinnamon/files/3471789/xsession-errors.old.upload.txt) [xsession-errors.upload.txt](https://github.com/linuxmint/cinnamon/files/3471791/xsession-errors.upload.txt) [lspci.txt](https://github.com/linuxmint/cinnamon/files/3471859/lspci.txt) Syslog: [kernel.log.txt](https://github.com/linuxmint/cinnamon/files/3471804/kernel.log.txt) Grub: having mitigations on or off makes no difference GRUB_CMDLINE_LINUX_DEFAULT="intel_idle.max_cstate=1 drm.debug=14 log_buf_len=16M mitigations=on intel_iommu=on vfio-pci.ids=8086:8d26,10de:1184,10de:0e0a modprobe.blacklist=snd_hda_intel,snd_hda_core,snd_hda_codec,snd_hda_codec_hdmi,nouveau" Xorg crashdump traces: /var/crash/usr_lib_xorg_Xorg.0.crash Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -noliste'. Program terminated with signal SIGSEGV, Segmentation fault. #0
[Desktop-packages] [Bug 1563772] Re: Xorg crashes on systemctl suspend
*** This bug is a duplicate of bug 1839174 *** https://bugs.launchpad.net/bugs/1839174 ** This bug has been marked a duplicate of bug 1839174 Xorg crashes in stdio functions under pci_device_vgaarb_set_target() from VGAGet() from VGAarbiterSpriteMoveCursor() -- 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/1563772 Title: Xorg crashes on systemctl suspend Status in xorg-server package in Ubuntu: New Bug description: Xorg always crashes on Ubuntu 15.10 when trying to do systemctl suspend. Here is the Xorg.0.log.old: [15.924] (EE) Backtrace: [15.925] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55d2ea6c268e] [15.925] (EE) 1: /usr/bin/X (0x55d2ea50e000+0x1b89f9) [0x55d2ea6c69f9] [15.925] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f80eb64+0x352f0) [0x7f80eb6752f0] [15.925] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_set_target+0xf3) [0x7f80ecc34933] [15.925] (EE) 4: /usr/bin/X (0x55d2ea50e000+0xb8c10) [0x55d2ea5c6c10] [15.925] (EE) 5: /usr/bin/X (0x55d2ea50e000+0x96630) [0x55d2ea5a4630] [15.925] (EE) 6: /usr/bin/X (DPMSSet+0x76) [0x55d2ea5a4926] [15.925] (EE) 7: /usr/bin/X (0x55d2ea50e000+0x10f8d4) [0x55d2ea61d8d4] [15.925] (EE) 8: /usr/bin/X (0x55d2ea50e000+0x5818f) [0x55d2ea56618f] [15.925] (EE) 9: /usr/bin/X (0x55d2ea50e000+0x5c34b) [0x55d2ea56a34b] [15.925] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f80eb660a40] [15.925] (EE) 11: /usr/bin/X (_start+0x29) [0x55d2ea5546c9] [15.925] (EE) [15.925] (EE) Segmentation fault at address 0x30 [15.925] (EE) Fatal server error: [15.925] (EE) Caught signal 11 (Segmentation fault). Server aborting I'm using i3 and lightdm, kernel 4.5.0, and an Ivy Bridge i7-3547u. This is a possible duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1510998 but the stacktrace isn't the same. I can't pinpoint when it started to happen. I also tried all the fix proposed, both using UXA instead of SNA, or updating the Xorg driver. The problem persists with the oibaf ppa. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1563772/+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 1839174] Re: Xorg crashes in stdio functions under pci_device_vgaarb_set_target() from VGAGet() from VGAarbiterSpriteMoveCursor()
Thanks Seb. That means the fix is in the HWE packages for 18.04, not the regular packages for 18.04. ** Summary changed: - Xorg crashes - segfault error 6 in libc-2.27.so + Xorg crashes in stdio functions under pci_device_vgaarb_set_target() from VGAGet() from VGAarbiterSpriteMoveCursor() ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=101995 Importance: Unknown Status: Unknown ** Changed in: xorg-server (Ubuntu) Status: Fix Released => Confirmed ** Also affects: xorg-server-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server-hwe-18.04 (Ubuntu) Status: New => Fix Released ** Also affects: xorg-server (Ubuntu Eoan) Importance: High Status: Confirmed ** Also affects: xorg-server-hwe-18.04 (Ubuntu Eoan) Importance: High Status: Fix Released ** Also affects: xorg-server (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: xorg-server-hwe-18.04 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xorg-server-hwe-18.04 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Disco) Status: New => Fix Released ** Changed in: xorg-server (Ubuntu Eoan) Status: Confirmed => Fix Released ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Released ** No longer affects: xorg-server-hwe-18.04 (Ubuntu Disco) ** No longer affects: xorg-server-hwe-18.04 (Ubuntu Eoan) ** Changed in: xorg-server (Ubuntu Bionic) Status: New => Confirmed ** Changed in: xorg-server (Ubuntu Eoan) Importance: High => Undecided -- 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/1839174 Title: Xorg crashes in stdio functions under pci_device_vgaarb_set_target() from VGAGet() from VGAarbiterSpriteMoveCursor() Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Confirmed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server source package in Disco: Fix Released Status in xorg-server source package in Eoan: Fix Released Bug description: Issue xorg crashes, there doesn't seem to be any repeatable cause, it'll happen just watching hulu or youtube, it'll happen when using citrix, or when playing steam games. Steps to reproduce use xorg for a while Expected behaviour not crashing Other information issue only happens when using pci-e passthrough to qemu virtual machines Has been an issue since setting up pci-e passthrough, have reinstalled Linux Mint (from XFCE version) but error persists, have changed numerous bios settings without having an impact Upgraded bios to most recent version, also reset bios to factory defaults, didn't make a difference Tried latest Linux 5.x kernels from uuku, same issue The virtual machine doesn't have any problems, it never crashes and stays running when the host os xorg crashes. System:Host: drac Kernel: 4.15.0-55-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.2.3 Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic Machine: Type: Server System: Supermicro product: Super Server v: 0123456789 serial: Mobo: Supermicro model: X10SRL-F v: 1.01B serial: UEFI: American Megatrends v: 3.1c date: 05/02/2019 Graphics: Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Micro-Star MSI driver: nvidia v: 430.34 bus ID: 03:00.0 Device-2: NVIDIA GK104 [GeForce GTX 770] vendor: eVga.com. driver: vfio-pci v: 0.2 bus ID: 04:00.0 Device-3: ASPEED Graphics Family vendor: Super Micro driver: ast v: kernel bus ID: 0b:00.0 Display: x11 server: X.Org 1.19.6 driver: nvidia resolution: 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 430.34 direct render: Yes CPU: Topology: 6-Core model: Intel Xeon E5-1650 v4 bits: 64 type: MT MCP arch: Broadwell rev: 1 L2 cache: 15.0 MiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 86397 Speed: 1203 MHz min/max: N/A Core speeds (MHz): 1: 1203 2: 1206 3: 1330 4: 1200 5: 1201 6: 1201 7: 1200 8: 1200 9: 2046 10: 1202 11: 1202 12: 1201 Not using PPA builds Linux Mint 19.2 (Upgraded from 19.1) 64bit root@drac:/vms# apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100
[Desktop-packages] [Bug 1838902] Re: GNOME Control Center hangs for some time when I add other keyboard in settings
** Summary changed: - GNOME Control Center sticks when I add other keyboard in settings + GNOME Control Center hangs for some time when I add other keyboard in settings -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1838902 Title: GNOME Control Center hangs for some time when I add other keyboard in settings Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: But then the list of languages opens and I can choose needing variant. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.2-1ubuntu4 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 4 22:30:32 2019 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1838902/+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
