[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze
Looks like this issue does not exist when we use Ubuntu with Wayland in 18.04. I am using it now. Will update the details if there is any change. -- 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/1807056 Title: Occasional Keyboard freeze Status in gnome-shell package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/907 --- I am using 18.04 and sometimes, whatever I type does not work. It is as if there is no keyboard connected while I have my laptop keyboard and an external keyboard connected to the machine. I even enabled On Screen Keyboard and tried to type through it. Same result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Dec 6 05:41:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807056/+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 1815957] Re: SynPS/2 Synaptics TouchPad: Read error 19
** Changed in: libinput (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-input-libinput (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+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 829924] Re: cheese crashed with SIGSEGV in g_strconcat()
[Expired for cheese (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cheese (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/829924 Title: cheese crashed with SIGSEGV in g_strconcat() Status in cheese package in Ubuntu: Expired Bug description: on enable an effect ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: cheese 3.0.1-2ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 Architecture: amd64 CrashCounter: 1 Date: Sat Aug 20 09:21:04 2011 ExecutablePath: /usr/bin/cheese InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) MachineType: LENOVO 429136G ProcCmdline: cheese ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 RelatedPackageVersions: cheese3.0.1-2ubuntu2 cheese-common 3.0.1-2ubuntu2 SegvAnalysis: Segfault happened at: 0x7fcc01dd2c1f:pcmpeqb (%rdi),%xmm1 PC (0x7fcc01dd2c1f) ok source "(%rdi)" (0x0060) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cheese StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 g_strconcat () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/libcheese.so.1 cheese_camera_set_effect () from /usr/lib/libcheese.so.1 cheese_main_window_on_selected_effect_change () Title: cheese crashed with SIGSEGV in g_strconcat() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 04/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET42WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 429136G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET42WW(1.12):bd04/01/2011:svnLENOVO:pn429136G:pvrThinkPadX220:rvnLENOVO:rn429136G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429136G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/829924/+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 767440] Re: Cheese displays no image, though webcam is active
[Expired for cheese (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cheese (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/767440 Title: Cheese displays no image, though webcam is active Status in cheese package in Ubuntu: Expired Bug description: Binary package hint: cheese Whenever I start cheese, the webcam light comes on, but I get no image displayed. Earlier builds would display an image until I clicked the effects button and upon returning from selecting effects, the image would be gone. Now I never get an image. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cheese 2.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Apr 20 13:14:07 2011 EcryptfsInUse: Yes InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110303) MachineType: Dell Inc. Latitude E6510 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese2.32.0-0ubuntu2 cheese-common 2.32.0-0ubuntu2 SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/20/2010:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/767440/+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 1064332] Re: shotwell freeze when trying to save image
[Expired for One Hundred Papercuts because there has been no activity for 60 days.] ** Changed in: hundredpapercuts Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1064332 Title: shotwell freeze when trying to save image Status in One Hundred Papercuts: Expired Status in shotwell package in Ubuntu: Expired Bug description: Shotwell freeze every time when I want to save the image after a modification. In addition it takes a lot of time time save images. I use Shotwell 0.13.0-0ubuntu3 on Ubuntu 12.10. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1064332/+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 833849] Re: cheese crashed with SIGSEGV in g_slice_alloc()
[Expired for cheese (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cheese (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/833849 Title: cheese crashed with SIGSEGV in g_slice_alloc() Status in cheese package in Ubuntu: Expired Bug description: cheese crashes on start. lsb_release -rd Description: Ubuntu oneiric (development branch) Release: 11.10 apt-cache policy cheese cheese: Installed: 3.0.1-2ubuntu2 Candidate: 3.0.1-2ubuntu2 Version table: *** 3.0.1-2ubuntu2 0 500 http://in.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: cheese 3.0.1-2ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CrashCounter: 1 Date: Thu Aug 25 20:58:33 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/cheese InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: Dell Inc. Dell System XPS L702X ProcCmdline: cheese RelatedPackageVersions: cheese3.0.1-2ubuntu2 cheese-common 3.0.1-2ubuntu2 SegvAnalysis: Segfault happened at: 0x7f28255c9598 :mov 0x8(%rax),%rbx PC (0x7f28255c9598) ok source "0x8(%rax)" (0x10007) not located in a known VMA region (needed readable region)! destination "%rbx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: cheese StacktraceTop: g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_new_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: cheese crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to oneiric on 2011-08-23 (1 days ago) UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev sambashare video dmi.bios.date: 06/01/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0XN71K dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd06/01/2011:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L702X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/833849/+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 973797] Re: Webcam not working properly!
[Expired for cheese (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cheese (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/973797 Title: Webcam not working properly! Status in cheese package in Ubuntu: Expired Bug description: First of all it was almost impossible for me to install 12.04 beta, because the installation window always crashed when it came to the place where you take a photo of your self or choose a login picture. I had to download Kamerka (nothing else worked like cheese and some other) which kept ma camera busy so i could proceed whith the install. Cheese still doesnt work... I develop video recognition with OpenCV software so a camere is pretty important for me. I also have a Logitech C210 usb webcam which after the update streams only ~160x110p video. My built in laptop camera is Syntek Sonix 1.3MPixel USB 1.0 Camera which is having trouble with linux since ever(if the colors are ok, then the image is upside-down) now its come to just crashes. Oh, by the way my laptop is Asus F3 sereis. F3sr to be exact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/973797/+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 1064332] Re: shotwell freeze when trying to save image
[Expired for shotwell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: shotwell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1064332 Title: shotwell freeze when trying to save image Status in One Hundred Papercuts: Expired Status in shotwell package in Ubuntu: Expired Bug description: Shotwell freeze every time when I want to save the image after a modification. In addition it takes a lot of time time save images. I use Shotwell 0.13.0-0ubuntu3 on Ubuntu 12.10. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1064332/+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 1217119] Re: no device found
[Expired for cheese (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cheese (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1217119 Title: no device found Status in cheese package in Ubuntu: Expired Bug description: I have searched all of the the forums and have tried everything they say but it still won't find my device ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cheese 3.4.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17 Uname: Linux 3.5.0-39-generic i686 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Mon Aug 26 22:42:58 2013 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MachineType: Acer AOA110 MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.4.1-0ubuntu2.1 cheese-common 3.4.1-0ubuntu2.1 SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2008 dmi.bios.vendor: Acer dmi.bios.version: v0.3310 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrv0.3310:bd10/06/2008:svnAcer:pnAOA110:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: AOA110 dmi.product.version: 1 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1217119/+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 1743054] Re: Notifications - disappear, regression since xenial
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1743054 Title: Notifications - disappear, regression since xenial Status in gnome-shell package in Ubuntu: Expired Status in hexchat package in Ubuntu: Expired Bug description: In xenial, messenging menu would display hexchat irc highlights e.g. "#channel1 #channel2 nick1 nick2". Upon clicking one of them, the rest were preserved. Now, in gnome-shell, all notifications are cleared. A number bubble remains, and highlighted channels remain, but it is a lot more difficult to jump to each highlight, as previously I could could go back to the messaging menu and click #channel2 to open that hightlight. I'm not sure if this is a bug in hexchat, gnome-shell, or both. Is there an IRC client with better / preserving capacity of the highlights and gnome-shell integration? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743054/+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 1743054] Re: Notifications - disappear, regression since xenial
[Expired for hexchat (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hexchat (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1743054 Title: Notifications - disappear, regression since xenial Status in gnome-shell package in Ubuntu: Expired Status in hexchat package in Ubuntu: Expired Bug description: In xenial, messenging menu would display hexchat irc highlights e.g. "#channel1 #channel2 nick1 nick2". Upon clicking one of them, the rest were preserved. Now, in gnome-shell, all notifications are cleared. A number bubble remains, and highlighted channels remain, but it is a lot more difficult to jump to each highlight, as previously I could could go back to the messaging menu and click #channel2 to open that hightlight. I'm not sure if this is a bug in hexchat, gnome-shell, or both. Is there an IRC client with better / preserving capacity of the highlights and gnome-shell integration? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743054/+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 1810404] Re: printing options set in control center don't work
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1810404 Title: printing options set in control center don't work Status in gnome-control-center package in Ubuntu: Expired Bug description: 1. Open settings. 2. Go to Devices / Printers. 3. Click "Add..." and add a network printer with a duplex unit located automatically by the network scan. 4. Click the gear and elect "Printing Options". 5. Change the "Two-sided" option to enable two-sided printing. 6. Close the options dialog and settings window. 7. Print a document with multiple pages to that printer with "lp -d printer-name filename". 8. Observe how it prints single-sided. To get the setting to stick for real, I had to click on "Additional Printer Settings..." and change it there. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 07:04:33 2019 InstallationDate: Installed on 2019-01-02 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-01-02T11:29:50.338663 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1810404/+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 1810222] Re: "Record a short screecast" creates 0-byte WEBM files
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1810222 Title: "Record a short screecast" creates 0-byte WEBM files Status in gnome-shell package in Ubuntu: Expired Bug description: Fresh install of Ubuntu 18.04. When I press Shift+Ctrl+Alt+R, I see an orange dot in the upper-right corner, and a new .webm files in ~/Videos. Several problems: 1. There seems to be no actionable UI for this function. If I click the orange dot, I don't see any sort of menu, such as to pause or stop the recording. 2. The files is incorrectly named. The timestamp uses the DD-MM- HH:MM:SS format, but the HH is 05:26 when it's 5:26pm (it should be 17:26). 3. After I press Shift+Ctrl+Alt+R, the orange dot disappears, but the .webm file is empty. What am I doing wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1810222/+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 1815957] Re: SynPS/2 Synaptics TouchPad: Read error 19
Mark this as Incomplete for the request in #31 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+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 1819572] Re: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction
** Attachment added: "201606-22344-network-manager-nplusone-190312.var-log.tar.gz" https://bugs.launchpad.net/ubuntu/+bug/1819572/+attachment/5245585/+files/201606-22344-network-manager-nplusone-190312.var-log.tar.gz ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: Ubuntu Cosmic Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: Ubuntu Disco Importance: Undecided Status: New -- 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/1819572 Title: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction Status in Ubuntu: New Status in network-manager package in Ubuntu: New Status in The Cosmic Cuttlefish: New Status in network-manager source package in Cosmic: New Status in The Disco Dingo: New Status in network-manager source package in Disco: New Bug description: Hardware: Dell Vostro 5568 (CID 201606-22344) [Steps To Reproduce] 1. Install cosmic on this machine 2. Connect to the internet with ethernet 3. do-release-upgrade [Expected Result] Upgrade completes. The wired connection is ready to access the internet. [Actual Result] - The ethernet interface has an IP address assigned by the associated DHCP (checked by "ip -a") - "ping 8.8.8.8" will get "Destination Host Unreachable" [More Information] I tried the same steps on different machine-distro matrix[1] and could only reproduce the issue on this machine. [1] distro are: xenial-to-bionic, bionic-to-cosmic, cosmic-to-disco --- [Logs] - /var/log tarball of the system: the attachment 201606-22344-network- manager-nplusone-190312.var-log.tar.gz - Collected by "ubuntu-bug network-manager": /media/tai271828/certsd/201606-22344-network-manager- nplusone-190312.ubuntu.bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1819572/+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 1819567] [NEW] [HD-Audio Generic - HD-Audio Generic, playback] Bad quality 2.1 surround sound
Public bug reported: using a (2010?) 2.1 surround Creative speaker but the sound seems to fall back to a generic stereo output with only left and right channels (using the green plug). The subwoofer receives little sound and the left and right speakers receive the bulk of the sound. If I increase the sound level the bass gets almost muted. The Pulse Audio manager doesn't show also any 3rd channel (don't know if it was supposed to), only Left and Right. It seems a problem with mixing, since the sound goes with the same level to the front left and right speakers and the subwoofer only gets a small part of it, and it gets worst as the sound level is increased on the hardware volume control since the speakers handle almost all sound ranges. Tried to create Profiles and Mappings for an "analog-surround-21" and changed the LFE information on the usual config files, but nothing seems to work and I lack more deeply knowledge of how ALSA and Pulse Audio work to figure out how to implement a (up)mixing. I Win7 the speakers worked great, but in the new MoBo and Ryzen CPU Win7 is no longer supported and I want to finally use Linux (X)Ubuntu. This issue seems to have been tackled with previously here: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1286021 - lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: antonio 13557 F pulseaudio /dev/snd/controlC0: antonio 13557 F pulseaudio CurrentDesktop: XFCE Date: Tue Mar 12 02:06:24 2019 InstallationDate: Installed on 2019-01-10 (61 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Type: Volume slider, or mixer problems Title: [HD-Audio Generic - HD-Audio Generic, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd06/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1819567 Title: [HD-Audio Generic - HD-Audio Generic, playback] Bad quality 2.1 surround sound Status in alsa-driver package in Ubuntu: New Bug description: using a (2010?) 2.1 surround Creative speaker but the sound seems to fall back to a generic stereo output with only left and right channels (using the green plug). The subwoofer receives little sound and the left and right speakers receive the bulk of the sound. If I increase the sound level the bass gets almost muted. The Pulse Audio manager doesn't show also any 3rd channel (don't know if it was supposed to), only Left and Right. It seems a problem with mixing, since the sound goes with the same level to the front left and right speakers and the subwoofer only gets a small part of it, and it gets worst as the sound level is increased on the hardware volume control since the speakers handle almost all sound ranges. Tried to create Profiles and Mappings for an "analog-surround-21" and changed the LFE information on the usual config files, but nothing seems to work and I lack more deeply knowledge of how ALSA and Pulse Audio work to figure out how to implement a (up)mixing. I Win7 the speakers worked great, but in the new MoBo and Ryzen CPU Win7 is no longer supported and I want to finally use Linux (X)Ubuntu. This issue seems to have been tackled with previously here: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1286021 - lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64
[Desktop-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Also, does this bug apply to the laptop's internal speakers? Or are you using headphones? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Next, please wait until the audio has stopped working AND has later come back, then run: dmesg > dmesgafter.txt journalctl -b0 > journalafter.txt and send us the files 'dmesgafter.txt' and 'journalafter.txt'. ** Summary changed: - [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or the battery % is above 20 - 40% + [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+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 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
Remember this bug is only about "entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)". If you have any other problem then please open a new bug for it by running: ubuntu-bug gnome-shell -- 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/1772677 Title: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: In Progress Bug description: [Impact] I'm seeing a several gigs (more than 70GB) a day of org.gnome.Shell.desktop log entries. https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 [Test Case] With 2 monitors connected, simply lock the screen and leave it locked for a while. The error messages will be logged into syslog until all the empty space is filled up. More info: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/243 [Regression Potential] Low. The fix (https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/243) is a minor correction to window destroy logic, written by the main Gnome Shell maintainer. [Original Description] I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0
[Desktop-packages] [Bug 1812593] Re: gnome-shell[3159]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argumen
^^^ That is bug 1772677. Not this one. -- 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/1812593 Title: gnome-shell[3159]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got undefined Status in gnome-shell package in Ubuntu: Incomplete Bug description: $ journalctl -b [...] gnome-shell[3159]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got undefined setEngine@resource:///org/gnome/shell/misc/ibusManager.js:212:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 activateInputSource@resource:///org/gnome/shell/ui/status/keyboard.js:490:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _emit@resource:///org/gnome/gjs/modules/signals.js:128:27 activate@resource:///org/gnome/shell/ui/status/keyboard.js:65:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _inputSourcesChanged@resource:///org/gnome/shell/ui/status/keyboard.js:620:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 reload@resource:///org/gnome/shell/ui/status/keyboard.js:369:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _ibusSetContentType@resource:///org/gnome/shell/ui/status/keyboard.js:691:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _emit@resource:///org/gnome/gjs/modules/signals.js:128:27 _setContentType@resource:///org/gnome/shell/misc/ibusManager.js:188:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-1ubuntu1 Uname: Linux 4.20.3-042003-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 19:36:57 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-02 (49 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-12-02 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812593/+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 1818751] Re: can not switch between single displays
** Changed in: gnome-control-center Status: New => Fix Released -- 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/1818751 Title: can not switch between single displays Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Triaged Bug description: Ubuntu 19.04 apt policy gnome-settings-daemon gnome-settings-daemon: Installato: 3.31.90-1ubuntu1 Candidato: 3.31.90-1ubuntu1 Tabella versione: *** 3.31.90-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.30.2-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages When I change monitors in the single display and I want to go back to the previous monitor, it does not change me anymore, there's no button to apply the changes. I enclose a video to better demonstrate the problem To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1818751/+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 1818862] Re: Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.]
** Summary changed: - Totem player hangs when seeking video + Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.] ** No longer affects: totem (Ubuntu) ** Project changed: totem => libva -- 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/1818862 Title: Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.] Status in Libva: New Status in intel-vaapi-driver package in Ubuntu: Triaged Bug description: Totem player hangs as soon as I click on the bar at the bottom to seek to a specific time in an mp4 video. Video in question can be found here: https://cdn.media.ccc.de/congress/2018/h264-hd/35c3-9370-eng-deu- Hacking_how_we_see_hd.mp4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6.2 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: ubuntu:GNOME Date: Wed Mar 6 16:10:11 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-08 (453 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-05-02 (308 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1818862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
Yes I will be backporting the same fix to bionic. At least I will try to. I don't know what conflicts and incompatibilities might be in mutter 3.28. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Triaged Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] Gnome Shell redraws at 60 FPS at most, regardless of the hardware refresh rate, and regardless of the current display mode. This is particularly annoying for owners of 144Hz/120Hz/240Hz displays. [Test Case] 0. Find a monitor or laptop with a high refresh rate (120Hz or more), noting NOT to trust gnome-control-center or xrandr because an unrelated bug in mutter may cause those to report 120Hz even on 60Hz displays. Make sure the advertised hardware specs show the display is a high frame rate. 1. Edit /etc/environment and add: CLUTTER_SHOW_FPS=1 2. Reboot. 3. Open a terminal window and run: journalctl -f | grep FPS 4. In a new window run 'glmark2' or some other OpenGL benchmark that is not frame rate limited (note: glxgears for unrelated reasons IS frame rate limited in Wayland sessions, but can be used in Xorg sessions). 5. Verify the terminal window from step 4 shows high FPS values coming from the journalctl log that match the hardware spec, and are much higher than 60. [Regression Potential] Medium to low. This patch has been used upstream and in Ubuntu 19.04 for some months already without any issues. Although minor syntactical changes had to be made to avoid conflicts when backporting it from mutter 3.32 to mutter 3.30. If regressions did occur they would be visible in the frame rate of the entire screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815889]
I'm removing this from the 19.0 blocking tracker. Generally we don't add bugs to block a release if they were present in the previous release, additionally there doesn't seem to be any consensus on a solution, at this moment. If there is a fix implemented I'd be happy to pull that into a later 19.0 release. -- 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/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Confirmed Status in QEMU: New Status in mesa package in Ubuntu: Triaged Status in qemu package in Ubuntu: Triaged Status in mesa source package in Disco: Triaged Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+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 1819240] Re: Many sites will not connect. Very slow. Some siezing.
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1819240 Title: Many sites will not connect. Very slow. Some siezing. Status in xorg package in Ubuntu: New Bug description: N/A ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 8 19:20:55 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1] InstallationDate: Installed on 2016-09-11 (908 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard p6710f ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.07 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: 4CE0480TV4 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6710f dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 8 18:28:14 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 8 inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 9 inputLogitech USB Optical Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1819240/+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 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
** Information type changed from Private Security to Public -- 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/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gjs source package in Bionic: Confirmed Status in gnome-shell source package in Bionic: Confirmed Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+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 1819183] Re: FFe: Update pygobject to 3.32
This bug was fixed in the package pygobject - 3.32.0-1 --- pygobject (3.32.0-1) experimental; urgency=medium * New upstream release -- Jeremy Bicha Sun, 10 Mar 2019 12:59:34 -0400 pygobject (3.31.4-1) experimental; urgency=medium * New upstream release * Bump minimum glib to 2.48.0 -- Jeremy Bicha Fri, 08 Mar 2019 09:45:40 -0500 ** Changed in: pygobject (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1819183 Title: FFe: Update pygobject to 3.32 Status in pygobject package in Ubuntu: Fix Released Bug description: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.32.0-1 is in Debian experimental ready to be synced over once this FFe is approved. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+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 1819558] [NEW] Snap interfaces: openvswitch interface has typo
Public bug reported: Typo'd as openvtswitch ** Affects: gnome-software (Ubuntu) Importance: Low Assignee: Robert Ancell (robert-ancell) Status: Fix Committed ** Affects: gnome-software (Ubuntu Xenial) Importance: Low Assignee: Robert Ancell (robert-ancell) Status: Fix Committed ** Affects: gnome-software (Ubuntu Bionic) Importance: Low Assignee: Robert Ancell (robert-ancell) Status: Fix Committed ** Affects: gnome-software (Ubuntu Cosmic) Importance: Low Assignee: Robert Ancell (robert-ancell) Status: Fix Committed ** Affects: gnome-software (Ubuntu Disco) Importance: Low Assignee: Robert Ancell (robert-ancell) Status: Fix Committed ** Also affects: gnome-software (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu Disco) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Cosmic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Xenial) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Disco) Status: New => Fix Committed ** Changed in: gnome-software (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: gnome-software (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: gnome-software (Ubuntu Xenial) Status: New => In Progress ** Changed in: gnome-software (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: gnome-software (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu Disco) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu Cosmic) Importance: Undecided => Low -- 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/1819558 Title: Snap interfaces: openvswitch interface has typo Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Committed Status in gnome-software source package in Disco: Fix Committed Bug description: Typo'd as openvtswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1819558/+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 27867]
*** Bug 1497756 has been marked as a duplicate of this bug. *** -- 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/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+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 27867]
You can find the option here: https://bugs.edge.launchpad.net/firefox/+bug/27867 Thanks Ksharief https://www.fieldengineer.com/ -- 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/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+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 27867]
*** Bug 1265265 has been marked as a duplicate of this bug. *** -- 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/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+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 27867]
*** Bug 1256663 has been marked as a duplicate of this bug. *** -- 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/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+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 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp
It says the sender of this error is gnome-session-b? who's that? where's the code that generates this error? I'm on 18.10, upgraded from 18.04 CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 Status in gnome-session package in Ubuntu: Confirmed Bug description: That error is logged: org.gnome.ScreenSaver[1081]: Unable to init server: Could not connect: Connection refused then: gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 oem@ubuntu:~$ localectl System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: fr X11 Model: pc105 X11 Variant: oss So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8 and then ran 'sudo locale-gen' and finally rebooted. But the error is still logged after reboot: either i need to set also 'VC Keymap', but how ?, or it is related to the vte version actually used (and need an upgrade) (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.26.1-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 3 17:17:45 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+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 1819549] Re: Cannot Update Ubuntu MATE 16.04.2 RP1
** Package changed: network-manager (Ubuntu) => ubuntu -- 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/1819549 Title: Cannot Update Ubuntu MATE 16.04.2 RP1 Status in Ubuntu: New Bug description: When attempting to use the Update utility on Ubuntu MATE 16.04.2 on Raspberry Pi 3 for the latest security updates the user is informed that approximately 50MB of space is required and there is not enough space on /boot. The user is advised to use "sudo apt-get clean" to free up the necessary 4000KB of space required, however, this will not free enough space on /boot. The user is unable to download security updates. When looking into this issue it was noted that in the latest version of Ubuntu MATE the following change was made: Re-size file system Since Ubuntu MATE 16.04.2 the root parition is automatically resized, to fully utilise the all available space on the microSD card, on first boot. Source: https://ubuntu-mate.org/raspberry-pi/ This represents a significant impediment to installing security updates AND future use cases where more space is required on the primary partition. My suggestion would be removing the automatic file system re-size and allow the user to use parted or gparted to set partition sizes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1819549/+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 1819549] [NEW] Cannot Update Ubuntu MATE 16.04.2 RP1
Public bug reported: When attempting to use the Update utility on Ubuntu MATE 16.04.2 on Raspberry Pi 3 for the latest security updates the user is informed that approximately 50MB of space is required and there is not enough space on /boot. The user is advised to use "sudo apt-get clean" to free up the necessary 4000KB of space required, however, this will not free enough space on /boot. The user is unable to download security updates. When looking into this issue it was noted that in the latest version of Ubuntu MATE the following change was made: Re-size file system Since Ubuntu MATE 16.04.2 the root parition is automatically resized, to fully utilise the all available space on the microSD card, on first boot. Source: https://ubuntu-mate.org/raspberry-pi/ This represents a significant impediment to installing security updates AND future use cases where more space is required on the primary partition. My suggestion would be removing the automatic file system re-size and allow the user to use parted or gparted to set partition sizes. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Description changed: When attempting to use the Update utility on Ubuntu MATE 16.04.2 on Raspberry Pi 3 for the latest security updates the user is informed that approximately 50MB of space is required and there is not enough space on /boot. The user is advised to use "sudo apt-get clean" to free up the necessary 4000KB of space required, however, this will not free enough space on /boot. The user is unable to download security updates. When looking into this issue it was noted that in the latest version of Ubuntu MATE the following change was made: Re-size file system Since Ubuntu MATE 16.04.2 the root parition is automatically resized, to fully utilise the all available space on the microSD card, on first boot. Source: https://ubuntu-mate.org/raspberry-pi/ This represents a significant impediment to installing security updates AND future use cases where more space is required on the primary partition. My suggestion would be removing the automatic file system re-size and - allow the user to use parted or gparted set partition sizes. + allow the user to use parted or gparted to set partition sizes. -- 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/1819549 Title: Cannot Update Ubuntu MATE 16.04.2 RP1 Status in network-manager package in Ubuntu: New Bug description: When attempting to use the Update utility on Ubuntu MATE 16.04.2 on Raspberry Pi 3 for the latest security updates the user is informed that approximately 50MB of space is required and there is not enough space on /boot. The user is advised to use "sudo apt-get clean" to free up the necessary 4000KB of space required, however, this will not free enough space on /boot. The user is unable to download security updates. When looking into this issue it was noted that in the latest version of Ubuntu MATE the following change was made: Re-size file system Since Ubuntu MATE 16.04.2 the root parition is automatically resized, to fully utilise the all available space on the microSD card, on first boot. Source: https://ubuntu-mate.org/raspberry-pi/ This represents a significant impediment to installing security updates AND future use cases where more space is required on the primary partition. My suggestion would be removing the automatic file system re-size and allow the user to use parted or gparted to set partition sizes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1819549/+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 1818654] Re: unable to login in non-graphic terminal (e.g. tty1)
PS: the issue is not present any more. It had been for some two/three
weeks, now it's gone... (no, I have not been using hibernation or
suspend)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1818654
Title:
unable to login in non-graphic terminal (e.g. tty1)
Status in lightdm package in Ubuntu:
New
Bug description:
I am unable to login in non-graphic terminal (e.g. tty1) ending with
"Login incorrect" all the time because password prompt does not wait
for user input.
Steps to reproduce:
1) switch to non-graphical terminal (tty1) with CTRL+ALT+F1
2) you see prompt for login ("login:")
3) type-in user login -> ENTER
4) you see password prompt ("password:")
5) try to type password... what you see is that it behaves as just as if you
pressed ENTER before actually typing all the passwords characters
6) this repeats automatically 5 times and then screen is automatically reset
with blank login prompt
I do not know since when this has occured, but it is VERY SERIOUS bug - if
something happens in my X (tty7), I am unable to kill or manage it :/
What might be wrong?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
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: Tue Mar 5 13:09:49 2019
InstallationDate: Installed on 2018-09-03 (182 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1818654/+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 1692378] Re: Text in add-on "Messaging Menu and Unity Launcher integration" for Thunderbird doesn't fit to preferences
** Changed in: thunderbird (Ubuntu) Assignee: Rolf Leggewie (r0lf) => (unassigned) -- 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/1692378 Title: Text in add-on "Messaging Menu and Unity Launcher integration" for Thunderbird doesn't fit to preferences Status in thunderbird package in Ubuntu: Confirmed Bug description: There is a problem in Thunderbird preferences (Menu > Edit > Preferences). On the tab General, preferences doesn't fit in the window by default There is too much space at the bottom of the window, some preferences can be moved there. I've drawn example of it. Could you fix it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1692378/+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 1705689] Re: When adding an app to favourites, two icons are created.
I was affected but I haven't seen it since 17.10, I seem to remember it was actually fixed a long time ago, but this bug report must have been forgotten. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- 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/1705689 Title: When adding an app to favourites, two icons are created. Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Bug description: On Ubuntu 17.10, I wanted to add gnome-terminal to the favorites. Usually in Gnome, the item gets added one times. Instead, there were two items of gnome-terminal in the favorites. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705689/+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 1705689] Re: When adding an app to favourites, two icons are created.
*since 18.04 -- 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/1705689 Title: When adding an app to favourites, two icons are created. Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Bug description: On Ubuntu 17.10, I wanted to add gnome-terminal to the favorites. Usually in Gnome, the item gets added one times. Instead, there were two items of gnome-terminal in the favorites. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705689/+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 1729077] Re: wrong color of horizontally centered area of scan with CanoScan Lide 200
*** This bug is a duplicate of bug 1731459 *** https://bugs.launchpad.net/bugs/1731459 ** Also affects: sane-backends Importance: Undecided Status: New -- 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/1729077 Title: wrong color of horizontally centered area of scan with CanoScan Lide 200 Status in sane-backends: New Status in sane-backends package in Ubuntu: Confirmed Bug description: This problem is 100% reproducable, also across reboots. On a Ubuntu 16.04 and 17.04 and Windows7 system the Scanner CanoScan Lide 200 works still completely fine. Problem with Ubuntu 17.10 : In a horizontally centered zone of about 1 centimeter width of the scan surface, over the full height of the surface, estimated 90% of the pixel values are completely wrong. The distribution of the wrong pixels in this zone appears random. With lineart and gray scan, the wrong pixels are black. With color scan, the wrong pixels are black or similar to red. The other pixels in the zone are a bit too bright. The effect is the same at all resolutions. See attached example snippets. The effect would continue vertically over the entire scan surface. The original was uniformly colored. The scanner worked again with Ubuntu 17.10 after purging sane- utils,libsane1,libsane-common (by overriding dependency-errors) and installing libsane-common_1.0.25+git20150528-1ubuntu4_all.deb libsane_1.0.25+git20150528-1ubuntu4_amd64.deb sane- utils_1.0.25+git20150528-1ubuntu4_amd64.deb (again by overriding dependency-errors) (and maybe re-plug scanner / reboot) Trying these versions had the same problem as default Ubuntu 17.10: archive.ubuntu.com : 1.0.27-1~experimental2ubuntu2.1, launchpad.net/~rolfbensch/+archive/ubuntu/sane-git : 1.0.27+git20171012-artful0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 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.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Oct 31 20:48:39 2017 InstallationDate: Installed on 2015-12-31 (670 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/1729077/+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 1819497] Re: gnome-control-center autonomously uninstalling
Ok, thanks. It still feels like rather odd behavior. -- 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/1819497 Title: gnome-control-center autonomously uninstalling Status in gnome-control-center package in Ubuntu: Invalid Bug description: Over the last couple of weeks gnome-control-center has autonomously uninstalled (or perhaps just disabled) twice: once as I uninstalled wpa_supplicant, and the second time when I uninstalled NetworkManager (and installed WICD instead). In both cases, trying to run gnome-control-center from either the GUI or from the CLI failed (giving me a not installed error in the CLI), Simply installing using apt install gnome-control-center fixed it. I'm fairly certain that this isn't supposed to happen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 13:51:27 2019 InstallationDate: Installed on 2018-05-27 (287 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1819497/+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 1819497] Re: gnome-control-center autonomously uninstalling
Thank you for your bug report. It's not a bug though, gnome-control- center depends on network-manager since it's using it as a service and going to fail to work if that one is missing. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- 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/1819497 Title: gnome-control-center autonomously uninstalling Status in gnome-control-center package in Ubuntu: Invalid Bug description: Over the last couple of weeks gnome-control-center has autonomously uninstalled (or perhaps just disabled) twice: once as I uninstalled wpa_supplicant, and the second time when I uninstalled NetworkManager (and installed WICD instead). In both cases, trying to run gnome-control-center from either the GUI or from the CLI failed (giving me a not installed error in the CLI), Simply installing using apt install gnome-control-center fixed it. I'm fairly certain that this isn't supposed to happen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 13:51:27 2019 InstallationDate: Installed on 2018-05-27 (287 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1819497/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Changed in: virtualbox (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: libpdfbox-java (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: mongo-java-driver (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: openhft-chronicle-threads (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-l10n in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-threads package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in activemq source package in Bionic: Fix Committed Status in afterburner.fx source package in Bionic: Fix Committed Status in annotation-indexer source package in Bionic: Fix Committed Status in apache-directory-server source package in Bionic: Fix Committed Status in aspectj source package in Bionic: Fix Committed Status in aspectj-maven-plugin source package in Bionic: Fix Committed Status in batik source package in Bionic: Fix Committed Status in bindex source package in Bionic: Fix Committed Status in bridge-method-injector source package in Bionic: Fix Committed Status in carrotsearch-hppc source package in Bionic: Fix Committed Status in clojure source package in Bionic: Fix Committed Status in clojure1.8 source package in Bionic: Fix Committed Status in commons-httpclient source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in ecj source package in Bionic: Fix Committed Status in eclipselink source package in Bionic: Fix Committed Status in elki source package in Bionic: Fix Committed Status in figtree source package in Bionic: Fix Committed Status in fontawesomefx source package in Bionic: Fix Committed Status in gettext source package in Bionic: Fix Committed Status in gluegen2 source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in hikaricp source package in Bionic: Fix Committed Status in hsqldb source package in Bionic: Fix Committed Status in hsqldb1.8.0 source package in Bionic: Fix Committed Status in insubstantial source package in Bionic: Fix Committed Status in jabref source package in Bionic: Fix Committed Status in jackson-core source package in Bionic: Fix Committed Status in jackson-databind source package in Bionic: Fix Committed Status in jackson-dataformat-xml source package in Bionic: Fix Committed Status in jackson-module-jaxb-annotations source package in Bionic: Fix Committed Status in java-common source package in Bionic: Fix Committed Status in javafxsvg source package in Bionic: Fix Committed Status in javamail source package in Bionic: Fix Committed Status in javatools source package in Bionic: Fix Committed Status in jboss-classfilewriter source package in Bionic: Fix Committed Status in jboss-jdeparser2 source package in Bionic: Fix Committed Status in jboss-modules source package in Bionic: Fix Committed Status in jcommander source package in Bionic: Fix Committed Status in jersey1 source package in Bionic: Fix Committed Status in jftp source package in Bionic: Fix Committed Status in jhove source package in Bionic: Fix Committed Status in jmdns source package in Bionic: Fix Committed Status in jnr-posix source package in Bionic: Fix Committed Status in jruby source package in Bionic: Fix Committed Status in jruby-openssl source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in jts source package in Bionic: Fix Committed Status in junit4 source package in Bionic: Fix Committed Status in jxgrabkey source package in Bionic: Fix Committed Status in jython source package in Bionic: Fix
Re: [Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Same here on OpenSUSE Tumbleweed u,u El lun., 11 de mar. de 2019, 13:45, magdiychuk <1553...@bugs.launchpad.net> escribió: > I really hope that the problem will be solved. I use Arch Linux and the > same problem. The subwoofer does not work ... :-( It is a pity. I would > like to solve the problem. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1553685 > > Title: > Lenovo Y700-17ISK subwoofer doesn't work > > Status in alsa-driver package in Ubuntu: > Confirmed > > Bug description: > Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia > GTX960M 4GB) > Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, > kernel 4.4.0-10-generic, nvidia 361.28) > > Problem: Notebook subwoofer doesn't work. > > Judging from alsa-info.sh output, there is no pin declared for the bass > output by BIOS. > Please find a zip file attached: > 'alsa-info_hdajackretask-unconnected-pins' > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.4.0-10-generic 4.4.0-10.25 > ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 > Uname: Linux 4.4.0-10-generic x86_64 > ApportVersion: 2.20-0ubuntu3 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: aljosa 1776 F pulseaudio > CurrentDesktop: Unity > Date: Sun Mar 6 11:02:21 2016 > HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 > InstallationDate: Installed on 2016-03-05 (0 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 > (20160304) > MachineType: LENOVO 80Q0 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed > root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-4.4.0-10-generic N/A >linux-backports-modules-4.4.0-10-generic N/A >linux-firmware1.156 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/31/2016 > dmi.bios.vendor: LENOVO > dmi.bios.version: CDCN30WW > dmi.board.asset.tag: NO Asset Tag > dmi.board.name: Allsparks 7A > dmi.board.vendor: LENOVO > dmi.board.version: NO DPK > dmi.chassis.asset.tag: NO Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Lenovo ideapad Y700-17ISK > dmi.modalias: > dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: > dmi.product.name: 80Q0 > dmi.product.version: Lenovo ideapad Y700-17ISK > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions > -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10
[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
@Łukasz Will you not be following/patching bionic with this fix? (@Daniel) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Triaged Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] Gnome Shell redraws at 60 FPS at most, regardless of the hardware refresh rate, and regardless of the current display mode. This is particularly annoying for owners of 144Hz/120Hz/240Hz displays. [Test Case] 0. Find a monitor or laptop with a high refresh rate (120Hz or more), noting NOT to trust gnome-control-center or xrandr because an unrelated bug in mutter may cause those to report 120Hz even on 60Hz displays. Make sure the advertised hardware specs show the display is a high frame rate. 1. Edit /etc/environment and add: CLUTTER_SHOW_FPS=1 2. Reboot. 3. Open a terminal window and run: journalctl -f | grep FPS 4. In a new window run 'glmark2' or some other OpenGL benchmark that is not frame rate limited (note: glxgears for unrelated reasons IS frame rate limited in Wayland sessions, but can be used in Xorg sessions). 5. Verify the terminal window from step 4 shows high FPS values coming from the journalctl log that match the hardware spec, and are much higher than 60. [Regression Potential] Medium to low. This patch has been used upstream and in Ubuntu 19.04 for some months already without any issues. Although minor syntactical changes had to be made to avoid conflicts when backporting it from mutter 3.32 to mutter 3.30. If regressions did occur they would be visible in the frame rate of the entire screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or the battery % is above 20 - 40%
Hello, it seems like now audio is not working even when on full battery or plugged in. It's so weird. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or the battery % is above 20 - 40% Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+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 1819503] Re: Drop imagemagick-display from the default install [disco regression]
** Description changed: This is actually a regression in Disco from Artful, Bionic and Cosmic, where this was fixed in https://bugs.launchpad.net/bugs/1717951 - Since the update to Disco the unprofessional and childish ImageMagick - icon is back. It was removed in Artful, Bionic and Cosmic for the - following reasons, perfectly summed up by Jeremy Bicha (a copy and paste - from Bug #171951): + Since the update to Disco the unprofessional ImageMagick icon is back. + It was removed in Artful, Bionic and Cosmic for the following reasons, + perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): + + I tested this in the "Ubuntu", "Ubuntu on Wayland" and "GNOME" session + and it it returned in all three instances. Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) ** Description changed: This is actually a regression in Disco from Artful, Bionic and Cosmic, where this was fixed in https://bugs.launchpad.net/bugs/1717951 - Since the update to Disco the unprofessional ImageMagick icon is back. - It was removed in Artful, Bionic and Cosmic for the following reasons, - perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): - I tested this in the "Ubuntu", "Ubuntu on Wayland" and "GNOME" session - and it it returned in all three instances. + I tested this in the "Ubuntu", "Ubuntu on Wayland" and "GNOME" session and the bug is visible in all three instances. + + Since the update to Disco the rather unprofessional ImageMagick icon is + back. It was removed in Artful, Bionic and Cosmic for the following + reasons, perfectly summed up by Jeremy Bicha (a copy and paste from Bug + #171951): + Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1819503 Title: Drop imagemagick-display from the default install [disco regression] Status in ubuntu-settings package in Ubuntu: New Bug description: This is actually a regression in Disco from Artful, Bionic and Cosmic, where this was fixed in https://bugs.launchpad.net/bugs/1717951 I tested this in the "Ubuntu", "Ubuntu on Wayland" and "GNOME" session and the bug is visible in all three instances. Since the update to Disco the rather unprofessional ImageMagick icon is back. It was removed in Artful, Bionic and Cosmic for the following reasons, perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual,
[Desktop-packages] [Bug 1717951] Re: UIFe: Drop imagemagick-display from the default install
Filed https://bugs.launchpad.net/ubuntu/+source/ubuntu- settings/+bug/1819503 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1717951 Title: UIFe: Drop imagemagick-display from the default install Status in ubuntu-settings package in Ubuntu: Fix Released Status in imagemagick package in Debian: New Bug description: Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) List Notifications == https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html Other Info == I will be attaching a patch for review by the Desktop Team here soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1717951/+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 1819503] Re: Drop imagemagick-display from the default install [disco regression]
** Summary changed: - Drop imagemagick-display from the default install [regression] + Drop imagemagick-display from the default install [disco regression] ** Description changed: - This is actually a regression from - https://bugs.launchpad.net/bugs/1717951 + This is actually a regression in Disco from Artful, Bionic and Cosmic, + where this was fixed in https://bugs.launchpad.net/bugs/1717951 Since the update to Disco the unprofessional and childish ImageMagick icon is back. It was removed in Artful, Bionic and Cosmic for the following reasons, perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1819503 Title: Drop imagemagick-display from the default install [disco regression] Status in ubuntu-settings package in Ubuntu: New Bug description: This is actually a regression in Disco from Artful, Bionic and Cosmic, where this was fixed in https://bugs.launchpad.net/bugs/1717951 I tested this in the "Ubuntu", "Ubuntu on Wayland" and "GNOME" session and the bug is visible in all three instances. Since the update to Disco the rather unprofessional ImageMagick icon is back. It was removed in Artful, Bionic and Cosmic for the following reasons, perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1819503/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I really hope that the problem will be solved. I use Arch Linux and the same problem. The subwoofer does not work ... :-( It is a pity. I would like to solve the problem. -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1819503] [NEW] Drop imagemagick-display from the default install [disco regression]
Public bug reported: This is actually a regression in Disco from Artful, Bionic and Cosmic, where this was fixed in https://bugs.launchpad.net/bugs/1717951 Since the update to Disco the unprofessional and childish ImageMagick icon is back. It was removed in Artful, Bionic and Cosmic for the following reasons, perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1819503 Title: Drop imagemagick-display from the default install [disco regression] Status in ubuntu-settings package in Ubuntu: New Bug description: This is actually a regression in Disco from Artful, Bionic and Cosmic, where this was fixed in https://bugs.launchpad.net/bugs/1717951 Since the update to Disco the unprofessional and childish ImageMagick icon is back. It was removed in Artful, Bionic and Cosmic for the following reasons, perfectly summed up by Jeremy Bicha (a copy and paste from Bug #171951): Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1819503/+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 1777994] Re: the header xcb/xinput.h is missing
This bug was fixed in the package libxcb - 1.13-2~ubuntu18.04 --- libxcb (1.13-2~ubuntu18.04) bionic-proposed; urgency=medium [ Timo Aaltonen ] * Package libxcb-xinput0/libxcb-xinput-dev. (Closes: #733227) (LP: #1777994) [ Andreas Boll ] * control: Fix VCS urls. -- Jonathan Riddell Thu, 21 Jun 2018 13:52:59 +0300 ** Changed in: libxcb (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1777994 Title: the header xcb/xinput.h is missing Status in libxcb package in Ubuntu: Fix Released Status in libxcb source package in Bionic: Fix Released Bug description: [Impact] Allow Qt 5.12 to be compiled with full input support. This allows applications to be built using complex input devices such as drawing pads. This is used in e.g Krita which KDE builds into a Snap package for distribution. Currently Krita does not work with pen input devices with pressure sensitivity. [Test Case] Install Krita with Qt 5.12 from current Snap and note how pressure sensitivity does not work. [Regression Potential] None that I can see, it's just packaging a few new header files. I suspect this means there should be another package, libxcb-xinput-dev perhaps? I already did sudo apt install "libxcb*dev" to get all related dev packages, but none of them provide xcb/xinput.h. The result is that when building Qt from source, it's necessary to use a copy of this file which Qt provides (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing from the system. So if you don't give the option -qt-xcb to configure, then Qt will be built without multi-touch support. https://bugreports.qt.io/browse/QTBUG-69045 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxcb1-dev 1.13-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 08:32:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3802] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: libxcb UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1777994/+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 1777994] Update Released
The verification of the Stable Release Update for libxcb has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1777994 Title: the header xcb/xinput.h is missing Status in libxcb package in Ubuntu: Fix Released Status in libxcb source package in Bionic: Fix Released Bug description: [Impact] Allow Qt 5.12 to be compiled with full input support. This allows applications to be built using complex input devices such as drawing pads. This is used in e.g Krita which KDE builds into a Snap package for distribution. Currently Krita does not work with pen input devices with pressure sensitivity. [Test Case] Install Krita with Qt 5.12 from current Snap and note how pressure sensitivity does not work. [Regression Potential] None that I can see, it's just packaging a few new header files. I suspect this means there should be another package, libxcb-xinput-dev perhaps? I already did sudo apt install "libxcb*dev" to get all related dev packages, but none of them provide xcb/xinput.h. The result is that when building Qt from source, it's necessary to use a copy of this file which Qt provides (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing from the system. So if you don't give the option -qt-xcb to configure, then Qt will be built without multi-touch support. https://bugreports.qt.io/browse/QTBUG-69045 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxcb1-dev 1.13-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 08:32:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3802] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: libxcb UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1777994/+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 1819471] Re: gsd-power is not using lid-close-suspend-with-external-monitor value
** Also affects: systemd Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1819471 Title: gsd-power is not using lid-close-suspend-with-external-monitor value Status in GNOME Settings Daemon: New Status in systemd: New Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: I'm using 18.10 on Lenovo T480. Suspending on lid close is not possible with external monitor attached. Even if everything is set properly: $ gsettings get org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor true $ dconf read /org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor true gsp-power is still blocking system suspend: $ systemd-inhibit --list --mode=block Who: kpucynski (UID 1000/kpucynski, PID 1956/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Even with LidSwitchIgnoreInhibited=yes set systemd-logind is not ignoring it: $ grep -v ^# /etc/systemd/logind.conf [Login] HandleSuspendKey=suspend HandleHibernateKey=suspend HandleLidSwitch=suspend HandleLidSwitchExternalPower=suspend HandleLidSwitchDocked=suspend SuspendKeyIgnoreInhibited=no LidSwitchIgnoreInhibited=yes $ journalctl -f -u systemd-logind mar 11 16:08:43 kp-t480 systemd-logind[4822]: Lid closed. mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class mar 11 16:08:43 kp-t480 systemd-logind[4822]: External (1) displays connected. mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1819471/+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 1819497] Re: gnome-control-center autonomously uninstalling
These are the commands I used to cause the bug: 1st time: sudo apt purge wpasupplicant 2nd time: sudo apt install wicd-gtk sudo apt remove network-manager-gnome network-manager -- 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/1819497 Title: gnome-control-center autonomously uninstalling Status in gnome-control-center package in Ubuntu: New Bug description: Over the last couple of weeks gnome-control-center has autonomously uninstalled (or perhaps just disabled) twice: once as I uninstalled wpa_supplicant, and the second time when I uninstalled NetworkManager (and installed WICD instead). In both cases, trying to run gnome-control-center from either the GUI or from the CLI failed (giving me a not installed error in the CLI), Simply installing using apt install gnome-control-center fixed it. I'm fairly certain that this isn't supposed to happen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 13:51:27 2019 InstallationDate: Installed on 2018-05-27 (287 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1819497/+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 1819497] [NEW] gnome-control-center autonomously uninstalling
Public bug reported: Over the last couple of weeks gnome-control-center has autonomously uninstalled (or perhaps just disabled) twice: once as I uninstalled wpa_supplicant, and the second time when I uninstalled NetworkManager (and installed WICD instead). In both cases, trying to run gnome-control-center from either the GUI or from the CLI failed (giving me a not installed error in the CLI), Simply installing using apt install gnome-control-center fixed it. I'm fairly certain that this isn't supposed to happen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 13:51:27 2019 InstallationDate: Installed on 2018-05-27 (287 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1819497 Title: gnome-control-center autonomously uninstalling Status in gnome-control-center package in Ubuntu: New Bug description: Over the last couple of weeks gnome-control-center has autonomously uninstalled (or perhaps just disabled) twice: once as I uninstalled wpa_supplicant, and the second time when I uninstalled NetworkManager (and installed WICD instead). In both cases, trying to run gnome-control-center from either the GUI or from the CLI failed (giving me a not installed error in the CLI), Simply installing using apt install gnome-control-center fixed it. I'm fairly certain that this isn't supposed to happen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 13:51:27 2019 InstallationDate: Installed on 2018-05-27 (287 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1819497/+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 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
I had the same issue, followed David's instructions, but I still get a rapidly expanding syslog file when I lock the screen. I am running Ubuntu 18.04.02 with gnome shell 3.28.3, dual monitor and intel graphics. Something I can see is that when locked the screens are first turned to black, then they go in sleep mode, and then they suddenly come back to life, without any input. The continue these steps cyclically. My interpretation is that the asynchronous sleep mode between the two screens triggers a change in resolution that wakes the screens up and so on. But I can't confirm that. -- 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/1772677 Title: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: In Progress Bug description: [Impact] I'm seeing a several gigs (more than 70GB) a day of org.gnome.Shell.desktop log entries. https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 [Test Case] With 2 monitors connected, simply lock the screen and leave it locked for a while. The error messages will be logged into syslog until all the empty space is filled up. More info: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/243 [Regression Potential] Low. The fix (https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/243) is a minor correction to window destroy logic, written by the main Gnome Shell maintainer. [Original Description] I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I
[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
@seb128 please see "In 16.04 the NetworkManager package used to carry this patch..." in the bug description above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: * Impact When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not * Test case Configure the system to send all the traffic to a VPN, do a name resolution, the request should not go to the public DNS server (to be checked by capturing the traffic by example with wireshark) * Regression potential The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
I am looking for if the patch was included before the release of mesa "19.0.0-rc7" -- 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/1815236 Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Committed Status in totem package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME) --- I'm not sure, but this happened after updating to gstreamer 1.15.1, I have problems when I maximize totem. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815236/+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 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
They could pass to [1]mesa_19.0.0~rc7 [1] https://metadata.ftp-master.debian.org/changelogs/main/m/mesa/mesa_19.0.0~rc7-1_changelog https://bugs.freedesktop.org/show_bug.cgi?id=109535 The error is corrected in master. ** Bug watch added: freedesktop.org Bugzilla #109535 https://bugs.freedesktop.org/show_bug.cgi?id=109535 -- 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/1815236 Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Committed Status in totem package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME) --- I'm not sure, but this happened after updating to gstreamer 1.15.1, I have problems when I maximize totem. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815236/+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 1819471] Re: gsd-power is not using lid-close-suspend-with-external-monitor value
** Changed in: gnome-settings-daemon Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1819471 Title: gsd-power is not using lid-close-suspend-with-external-monitor value Status in GNOME Settings Daemon: New Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: I'm using 18.10 on Lenovo T480. Suspending on lid close is not possible with external monitor attached. Even if everything is set properly: $ gsettings get org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor true $ dconf read /org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor true gsp-power is still blocking system suspend: $ systemd-inhibit --list --mode=block Who: kpucynski (UID 1000/kpucynski, PID 1956/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Even with LidSwitchIgnoreInhibited=yes set systemd-logind is not ignoring it: $ grep -v ^# /etc/systemd/logind.conf [Login] HandleSuspendKey=suspend HandleHibernateKey=suspend HandleLidSwitch=suspend HandleLidSwitchExternalPower=suspend HandleLidSwitchDocked=suspend SuspendKeyIgnoreInhibited=no LidSwitchIgnoreInhibited=yes $ journalctl -f -u systemd-logind mar 11 16:08:43 kp-t480 systemd-logind[4822]: Lid closed. mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class mar 11 16:08:43 kp-t480 systemd-logind[4822]: External (1) displays connected. mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1819471/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: openhft-chronicle-threads (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation2 in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-threads package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in activemq source package in Bionic: Fix Committed Status in afterburner.fx source package in Bionic: Fix Committed Status in annotation-indexer source package in Bionic: Fix Committed Status in apache-directory-server source package in Bionic: Fix Committed Status in aspectj source package in Bionic: Fix Committed Status in aspectj-maven-plugin source package in Bionic: Fix Committed Status in batik source package in Bionic: Fix Committed Status in bindex source package in Bionic: Fix Committed Status in bridge-method-injector source package in Bionic: Fix Committed Status in carrotsearch-hppc source package in Bionic: Fix Committed Status in clojure source package in Bionic: Fix Committed Status in clojure1.8 source package in Bionic: Fix Committed Status in commons-httpclient source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in ecj source package in Bionic: Fix Committed Status in eclipselink source package in Bionic: Fix Committed Status in elki source package in Bionic: Fix Committed Status in figtree source package in Bionic: Fix Committed Status in fontawesomefx source package in Bionic: Fix Committed Status in gettext source package in Bionic: Fix Committed Status in gluegen2 source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in hikaricp source package in Bionic: Fix Committed Status in hsqldb source package in Bionic: Fix Committed Status in hsqldb1.8.0 source package in Bionic: Fix Committed Status in insubstantial source package in Bionic: Fix Committed Status in jabref source package in Bionic: Fix Committed Status in jackson-core source package in Bionic: Fix Committed Status in jackson-databind source package in Bionic: Fix Committed Status in jackson-dataformat-xml source package in Bionic: Fix Committed Status in jackson-module-jaxb-annotations source package in Bionic: Fix Committed Status in java-common source package in Bionic: Fix Committed Status in javafxsvg source package in Bionic: Fix Committed Status in javamail source package in Bionic: Fix Committed Status in javatools source package in Bionic: Fix Committed Status in jboss-classfilewriter source package in Bionic: Fix Committed Status in jboss-jdeparser2 source package in Bionic: Fix Committed Status in jboss-modules source package in Bionic: Fix Committed Status in jcommander source package in Bionic: Fix Committed Status in jersey1 source package in Bionic: Fix Committed Status in jftp source package in Bionic: Fix Committed Status in jhove source package in Bionic: Fix Committed Status in jmdns source package in Bionic: Fix Committed Status in jnr-posix source package in Bionic: Fix Committed Status in jruby source package in Bionic: Fix Committed Status in jruby-openssl source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in jts source package in Bionic: Fix Committed Status in junit4 source package in Bionic: Fix Committed Status in jxgrabkey source package in Bionic: Fix Committed Status in jython source package in Bionic: Fix Committed Status in libapache-poi-java source package in Bionic: Fix Committed Status in libbtm-java source package in Bionic: Fix Committed Status in libcommons-collections3-java source package in Bionic: Fix Committed Status in
[Desktop-packages] [Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
** Changed in: mesa (Ubuntu) Importance: Undecided => High ** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Committed -- 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/1815236 Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Committed Status in totem package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME) --- I'm not sure, but this happened after updating to gstreamer 1.15.1, I have problems when I maximize totem. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815236/+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 1818862] Re: Totem player hangs when seeking video
** Changed in: intel-vaapi-driver (Ubuntu) Status: Incomplete => Triaged ** Changed in: intel-vaapi-driver (Ubuntu) Importance: Undecided => High -- 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/1818862 Title: Totem player hangs when seeking video Status in Totem: New Status in intel-vaapi-driver package in Ubuntu: Triaged Status in totem package in Ubuntu: Incomplete Bug description: Totem player hangs as soon as I click on the bar at the bottom to seek to a specific time in an mp4 video. Video in question can be found here: https://cdn.media.ccc.de/congress/2018/h264-hd/35c3-9370-eng-deu- Hacking_how_we_see_hd.mp4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6.2 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: ubuntu:GNOME Date: Wed Mar 6 16:10:11 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-08 (453 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-05-02 (308 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1818862/+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 1816308] Re: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed() when changing workspace after several minutes of work in one workspace
*** This bug is a duplicate of bug 1812527 *** https://bugs.launchpad.net/bugs/1812527 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1816308 Title: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed() when changing workspace after several minutes of work in one workspace Status in gnome-shell package in Ubuntu: Confirmed Bug description: After some recent update, I face the following issue: Working on a workspace for some time (cannot say how much time), with or without lots of windows open, the workspace takes 2-3 minutes to recover, shows a crash dialog and restarts gnome. In fewer cases, after days of not rebooting, the gnome-shell dies instead of restarting, killing the session. I normally click to submit the bug reports, which should be in: https://errors.ubuntu.com/user/b56fc2894b10f99f5b9629befd4030528cf0fe943fd6d376f53b724791abcc83b582e15ae82346f04a637b2c7be643f2749a1bdec23b9bc4b9d8cd4c4aa1070e There are both created the /var/lib/whoopsie/whoopsie-id and /var/crash/_usr_bin_gnome-shell.1000.crash . The ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash does not work. Seems like apport-gtk is frozen. The next updates did not fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1816308/+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 1818936] Re: Found hard-coded secret-key for challenge-response on libfprint
Thanks
** Changed in: libfprint (Ubuntu)
Status: New => Triaged
** Also affects: libfprint via
https://gitlab.freedesktop.org/libfprint/libfprint/issues/151
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1818936
Title:
Found hard-coded secret-key for challenge-response on libfprint
Status in libfprint:
Unknown
Status in libfprint package in Ubuntu:
Triaged
Bug description:
Dear all,
We need to fix hard-coded symmetric-key for challenge-response
authentication on `uru4000 driver`.
The driver uses a symmetric-key technique to encrypt the challenge
data using AES encryption algorithm for authentication.
"2nd generation MS devices added an AES-based challenge/response
authentication scheme, where the device challenges the authenticity of the
driver."
link:
https://gitlab.freedesktop.org/libfprint/libfprint/blob/master/libfprint/drivers/uru4000.c#L348
Unfortunately, the driver creates risk by exposing a hard-coded secret
key as follows:
/* For 2nd generation MS devices */
static const unsigned char crkey[] = {
0x79, 0xac, 0x91, 0x79, 0x5c, 0xa1, 0x47, 0x8e,
0x98, 0xe0, 0x0f, 0x3c, 0x59, 0x8f, 0x5f, 0x4b,
};
link:
https://gitlab.freedesktop.org/libfprint/libfprint/blob/master/libfprint/drivers/uru4000.c#L150
If the library wants to use challenge-response authentication, we need
to introduce a new key distribution scheme also.
Furthermore, I don't know why the library is really necessary to use
it such a resource constrained environment.
Lastly, is it a kind of CWE-321: Use of Hard-coded Cryptographic Key? (see
https://cwe.mitre.org/data/definitions/321.html)
Many thanks!!
To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint/+bug/1818936/+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 1819471] Re: gsd-power is not using lid-close-suspend-with-external-monitor value
Thank you for your bug report, the key is ubuntu specific and buggy, but the feature request is also discussion upstream on https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/111 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #111 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/111 ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Triaged ** Also affects: gnome-settings-daemon via https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/111 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1819471 Title: gsd-power is not using lid-close-suspend-with-external-monitor value Status in GNOME Settings Daemon: Unknown Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: I'm using 18.10 on Lenovo T480. Suspending on lid close is not possible with external monitor attached. Even if everything is set properly: $ gsettings get org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor true $ dconf read /org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor true gsp-power is still blocking system suspend: $ systemd-inhibit --list --mode=block Who: kpucynski (UID 1000/kpucynski, PID 1956/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Even with LidSwitchIgnoreInhibited=yes set systemd-logind is not ignoring it: $ grep -v ^# /etc/systemd/logind.conf [Login] HandleSuspendKey=suspend HandleHibernateKey=suspend HandleLidSwitch=suspend HandleLidSwitchExternalPower=suspend HandleLidSwitchDocked=suspend SuspendKeyIgnoreInhibited=no LidSwitchIgnoreInhibited=yes $ journalctl -f -u systemd-logind mar 11 16:08:43 kp-t480 systemd-logind[4822]: Lid closed. mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class mar 11 16:08:43 kp-t480 systemd-logind[4822]: External (1) displays connected. mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1819471/+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 1816415] Re: gjs-console crashed with SIGSEGV in g_socket_receive_message_with_timeout()
Fixed in gobject-introspection (1.60.0-1). ** Changed in: glib2.0 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1816415 Title: gjs-console crashed with SIGSEGV in g_socket_receive_message_with_timeout() Status in glib2.0 package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/434b8b4abd971c7f84ca824ef5878a00d547753a https://gitlab.gnome.org/GNOME/gjs/issues/227 --- I have performance problems, after updating. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gjs 1.54.3-1build1 Uname: Linux 5.0.0-05rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 07:39:11 2019 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gjs /home/username/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/daemon.js SegvAnalysis: Segfault happened at: 0x7f224b1fafd8:mov(%r15),%edx PC (0x7f224b1fafd8) ok source "(%r15)" (0xfff98002) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gjs StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_socket_receive_message () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/libgjs.so.0 Title: gjs-console crashed with SIGSEGV in g_socket_receive_message() UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816415/+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 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
Please see if this kernel helps: https://people.canonical.com/~khfeng/lp1809856/ -- 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/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1815374] Re: Please adjust dependencies so that policykit-1-gnome can be demoted to universe
** Changed in: screen-resolution-extra (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1815374 Title: Please adjust dependencies so that policykit-1-gnome can be demoted to universe Status in screen-resolution-extra package in Ubuntu: In Progress Bug description: The Ubuntu Desktop Team would like to get policykit-1-gnome demoted to universe since it is no longer used in the default install. (See its package description.) I believe screen-resolution-extra is the last thing holding that package in main. gnome-shell provides polkit-1-auth-agent. You can see provides and reverse depends for a virtual package by running $ apt-cache showpkg polkit-1-auth-agent In my experience with demoting xterm to universe, it looked to me like Ubuntu's germinate doesn't handle virtual packages and alternate dependencies very well. I ended up having to put gnome-terminal as the first dependency in the list of alternates. Suggestion 1 Change screen-resolution-extra's dependency to: gnome-shell | policykit-1-gnome | polkit-1-auth-agent Suggestion 2 Change nvidia-settings to Suggest instead of Depend on screen-resolution-extra. From the package's description, it sounds like screen-resolution-extra is not useful for a default Ubuntu install? If so, we can demote both screen-resolution-extra and policykit-1-gnome to universe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1815374/+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 1819471] Re: gsd-power is not using lid-close-suspend-with-external-monitor value
** Description changed: - I'm using 18.04 on Lenovo T480. Suspending on lid close is not possible with external monitor attached. + I'm using 18.10 on Lenovo T480. Suspending on lid close is not possible with external monitor attached. Even if everything is set properly: $ gsettings get org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor true $ dconf read /org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor true gsp-power is still blocking system suspend: $ systemd-inhibit --list --mode=block - Who: kpucynski (UID 1000/kpucynski, PID 1956/gsd-power) - What: handle-lid-switch - Why: Multiple displays attached - Mode: block + Who: kpucynski (UID 1000/kpucynski, PID 1956/gsd-power) + What: handle-lid-switch + Why: Multiple displays attached + Mode: block + + Even with LidSwitchIgnoreInhibited=yes set systemd-logind is not + ignoring it: + + $ grep -v ^# /etc/systemd/logind.conf + + [Login] + HandleSuspendKey=suspend + HandleHibernateKey=suspend + HandleLidSwitch=suspend + HandleLidSwitchExternalPower=suspend + HandleLidSwitchDocked=suspend + SuspendKeyIgnoreInhibited=no + LidSwitchIgnoreInhibited=yes + + + $ journalctl -f -u systemd-logind + mar 11 16:08:43 kp-t480 systemd-logind[4822]: Lid closed. + mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs + mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus + mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class + mar 11 16:08:43 kp-t480 systemd-logind[4822]: External (1) displays connected. + mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. + mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs + mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus + mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class + mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1819471 Title: gsd-power is not using lid-close-suspend-with-external-monitor value Status in gnome-settings-daemon package in Ubuntu: New Bug description: I'm using 18.10 on Lenovo T480. Suspending on lid close is not possible with external monitor attached. Even if everything is set properly: $ gsettings get org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor true $ dconf read /org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor true gsp-power is still blocking system suspend: $ systemd-inhibit --list --mode=block Who: kpucynski (UID 1000/kpucynski, PID 1956/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Even with LidSwitchIgnoreInhibited=yes set systemd-logind is not ignoring it: $ grep -v ^# /etc/systemd/logind.conf [Login] HandleSuspendKey=suspend HandleHibernateKey=suspend HandleLidSwitch=suspend HandleLidSwitchExternalPower=suspend HandleLidSwitchDocked=suspend SuspendKeyIgnoreInhibited=no LidSwitchIgnoreInhibited=yes $ journalctl -f -u systemd-logind mar 11 16:08:43 kp-t480 systemd-logind[4822]: Lid closed. mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class mar 11 16:08:43 kp-t480 systemd-logind[4822]: External (1) displays connected. mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1819471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
I think we can assume that at least the mutter cosmic SRU does not introduce regressions and does fix the bug for certain testers. In case there's a follow-up fix needed, please file a separate bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Triaged Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] Gnome Shell redraws at 60 FPS at most, regardless of the hardware refresh rate, and regardless of the current display mode. This is particularly annoying for owners of 144Hz/120Hz/240Hz displays. [Test Case] 0. Find a monitor or laptop with a high refresh rate (120Hz or more), noting NOT to trust gnome-control-center or xrandr because an unrelated bug in mutter may cause those to report 120Hz even on 60Hz displays. Make sure the advertised hardware specs show the display is a high frame rate. 1. Edit /etc/environment and add: CLUTTER_SHOW_FPS=1 2. Reboot. 3. Open a terminal window and run: journalctl -f | grep FPS 4. In a new window run 'glmark2' or some other OpenGL benchmark that is not frame rate limited (note: glxgears for unrelated reasons IS frame rate limited in Wayland sessions, but can be used in Xorg sessions). 5. Verify the terminal window from step 4 shows high FPS values coming from the journalctl log that match the hardware spec, and are much higher than 60. [Regression Potential] Medium to low. This patch has been used upstream and in Ubuntu 19.04 for some months already without any issues. Although minor syntactical changes had to be made to avoid conflicts when backporting it from mutter 3.32 to mutter 3.30. If regressions did occur they would be visible in the frame rate of the entire screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
This bug was fixed in the package mutter - 3.30.2-1~ubuntu18.10.4 --- mutter (3.30.2-1~ubuntu18.10.4) cosmic; urgency=medium * Add support for high frame rate displays (LP: #1763892): - Drop clutter-Smooth-out-master-clock-to-smooth-visuals.patch - Add lp1763892-a-renderer-native-Add-hardware-presentation-timing.patch - Add lp1763892-b-renderer-native-Advertise-_FEATURE_SWAP_THROTTLE.patch -- Daniel van Vugt Thu, 28 Feb 2019 17:43:10 + ** Changed in: mutter (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Triaged Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] Gnome Shell redraws at 60 FPS at most, regardless of the hardware refresh rate, and regardless of the current display mode. This is particularly annoying for owners of 144Hz/120Hz/240Hz displays. [Test Case] 0. Find a monitor or laptop with a high refresh rate (120Hz or more), noting NOT to trust gnome-control-center or xrandr because an unrelated bug in mutter may cause those to report 120Hz even on 60Hz displays. Make sure the advertised hardware specs show the display is a high frame rate. 1. Edit /etc/environment and add: CLUTTER_SHOW_FPS=1 2. Reboot. 3. Open a terminal window and run: journalctl -f | grep FPS 4. In a new window run 'glmark2' or some other OpenGL benchmark that is not frame rate limited (note: glxgears for unrelated reasons IS frame rate limited in Wayland sessions, but can be used in Xorg sessions). 5. Verify the terminal window from step 4 shows high FPS values coming from the journalctl log that match the hardware spec, and are much higher than 60. [Regression Potential] Medium to low. This patch has been used upstream and in Ubuntu 19.04 for some months already without any issues. Although minor syntactical changes had to be made to avoid conflicts when backporting it from mutter 3.32 to mutter 3.30. If regressions did occur they would be visible in the frame rate of the entire screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763892] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Triaged Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] Gnome Shell redraws at 60 FPS at most, regardless of the hardware refresh rate, and regardless of the current display mode. This is particularly annoying for owners of 144Hz/120Hz/240Hz displays. [Test Case] 0. Find a monitor or laptop with a high refresh rate (120Hz or more), noting NOT to trust gnome-control-center or xrandr because an unrelated bug in mutter may cause those to report 120Hz even on 60Hz displays. Make sure the advertised hardware specs show the display is a high frame rate. 1. Edit /etc/environment and add: CLUTTER_SHOW_FPS=1 2. Reboot. 3. Open a terminal window and run: journalctl -f | grep FPS 4. In a new window run 'glmark2' or some other OpenGL benchmark that is not frame rate limited (note: glxgears for unrelated reasons IS frame rate limited in Wayland sessions, but can be used in Xorg sessions). 5. Verify the terminal window from step 4 shows high FPS values coming from the journalctl log that match the hardware spec, and are much higher than 60. [Regression Potential] Medium to low. This patch has been used upstream and in Ubuntu 19.04 for some months already without any issues. Although minor syntactical changes had to be made to avoid conflicts when backporting it from mutter 3.32 to mutter 3.30. If regressions did occur they would be visible in the frame rate of the entire screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817766] Re: [SRU] libreoffice 6.1.5 for cosmic
This bug was fixed in the package libreoffice - 1:6.1.5-0ubuntu0.18.10.1 --- libreoffice (1:6.1.5-0ubuntu0.18.10.1) cosmic; urgency=medium * New upstream release (LP: #1817766) * Drop upstreamed patches: - debian/patches/poppler-dropped-gbool.patch - debian/patches/poppler-fix-build-0-70.patch -- Olivier Tilloy Thu, 28 Feb 2019 12:01:51 +0100 ** Changed in: libreoffice (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1817766 Title: [SRU] libreoffice 6.1.5 for cosmic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Bug description: [Impact] * LibreOffice 6.1.5 is the fifth bugfix release of the still 6.1 line. Version 6.1.4 is currently in cosmic. For a list of fixed bugs compared to 6.1.4 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.1.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.1.5/RC2#List_of_fixed_bugs (that's a total of 78 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 78 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1817766/+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 1819471] [NEW] gsd-power is not using lid-close-suspend-with-external-monitor value
Public bug reported: I'm using 18.10 on Lenovo T480. Suspending on lid close is not possible with external monitor attached. Even if everything is set properly: $ gsettings get org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor true $ dconf read /org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor true gsp-power is still blocking system suspend: $ systemd-inhibit --list --mode=block Who: kpucynski (UID 1000/kpucynski, PID 1956/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Even with LidSwitchIgnoreInhibited=yes set systemd-logind is not ignoring it: $ grep -v ^# /etc/systemd/logind.conf [Login] HandleSuspendKey=suspend HandleHibernateKey=suspend HandleLidSwitch=suspend HandleLidSwitchExternalPower=suspend HandleLidSwitchDocked=suspend SuspendKeyIgnoreInhibited=no LidSwitchIgnoreInhibited=yes $ journalctl -f -u systemd-logind mar 11 16:08:43 kp-t480 systemd-logind[4822]: Lid closed. mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class mar 11 16:08:43 kp-t480 systemd-logind[4822]: External (1) displays connected. mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: suspend-resume -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1819471 Title: gsd-power is not using lid-close-suspend-with-external-monitor value Status in gnome-settings-daemon package in Ubuntu: New Bug description: I'm using 18.10 on Lenovo T480. Suspending on lid close is not possible with external monitor attached. Even if everything is set properly: $ gsettings get org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor true $ dconf read /org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor true gsp-power is still blocking system suspend: $ systemd-inhibit --list --mode=block Who: kpucynski (UID 1000/kpucynski, PID 1956/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Even with LidSwitchIgnoreInhibited=yes set systemd-logind is not ignoring it: $ grep -v ^# /etc/systemd/logind.conf [Login] HandleSuspendKey=suspend HandleHibernateKey=suspend HandleLidSwitch=suspend HandleLidSwitchExternalPower=suspend HandleLidSwitchDocked=suspend SuspendKeyIgnoreInhibited=no LidSwitchIgnoreInhibited=yes $ journalctl -f -u systemd-logind mar 11 16:08:43 kp-t480 systemd-logind[4822]: Lid closed. mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class mar 11 16:08:43 kp-t480 systemd-logind[4822]: External (1) displays connected. mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scan all dirs mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/bus mar 11 16:08:43 kp-t480 systemd-logind[4822]: device-enumerator: scanning /sys/class mar 11 16:08:43 kp-t480 systemd-logind[4822]: Refusing operation, handle-lid-switch is inhibited. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1819471/+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 1817766] Update Released
The verification of the Stable Release Update for libreoffice has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1817766 Title: [SRU] libreoffice 6.1.5 for cosmic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Bug description: [Impact] * LibreOffice 6.1.5 is the fifth bugfix release of the still 6.1 line. Version 6.1.4 is currently in cosmic. For a list of fixed bugs compared to 6.1.4 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.1.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.1.5/RC2#List_of_fixed_bugs (that's a total of 78 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 78 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1817766/+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 1817766] Re: [SRU] libreoffice 6.1.5 for cosmic
This bug was fixed in the package libreoffice-l10n - 1:6.1.5-0ubuntu0.18.10.1 --- libreoffice-l10n (1:6.1.5-0ubuntu0.18.10.1) cosmic; urgency=medium * New upstream release (LP: #1817766) * Drop upstreamed patches: - debian/patches/poppler-dropped-gbool.patch - debian/patches/poppler-fix-build-0-70.patch -- Olivier Tilloy Thu, 28 Feb 2019 12:01:51 +0100 ** Changed in: libreoffice-l10n (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1817766 Title: [SRU] libreoffice 6.1.5 for cosmic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Bug description: [Impact] * LibreOffice 6.1.5 is the fifth bugfix release of the still 6.1 line. Version 6.1.4 is currently in cosmic. For a list of fixed bugs compared to 6.1.4 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.1.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.1.5/RC2#List_of_fixed_bugs (that's a total of 78 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 78 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1817766/+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 1637988] Re: gvfsd-nfs not present in gvfs-backends, why?
** Tags added: sts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1637988 Title: gvfsd-nfs not present in gvfs-backends, why? Status in gvfs package in Ubuntu: Fix Released Bug description: We're at the end of 2016 and it's still impossible to browse nfs shares through nautilus, even though this is supported since version 1.23 of gvfs. What's keeping gvfsd-nfs out of the gvfs-backends package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1637988/+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 1818395] Re: Please demote lightdm greeter recommends to suggests
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1818395 Title: Please demote lightdm greeter recommends to suggests Status in lightdm package in Ubuntu: Confirmed Bug description: Please see https://bugs.launchpad.net/ubuntu/+source/indicator- datetime/+bug/1754872/comments/25 for some background on this bug report. I'd like to request that the lightdm greeter Recommends... unity-greeter | lightdm-greeter (virtual package) | lightdm-kde-greeter be moved to Suggests. It seems the apt installation order causes unity-greeter (and other unity components) to be installed along with lightdm-gtk-greeter when installing the xubuntu-desktop task. Since each of the lightdm greeters should depend on lightdm, I think this change helps make greeter installation more explicit and should prevent the installation of multiple greeters when only one is needed or requested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1818395/+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 1746598] Re: [MIR] libnfs
@cyphermox, It was "Fix Released" for disco only[1], can we complete it for stable releases ? [1] - rmadison libnfs | 1.2.0-3| precise/universe | source libnfs | 1.3.0-2ubuntu1 | trusty/universe | source libnfs | 1.9.8-1| xenial/universe | source libnfs | 2.0.0-1~exp1 | bionic/universe | source libnfs | 2.0.0-1~exp1 | cosmic/universe | source => libnfs | 3.0.0-2| disco| source ** Also affects: libnfs (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: libnfs (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: libnfs (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnfs in Ubuntu. https://bugs.launchpad.net/bugs/1746598 Title: [MIR] libnfs Status in libnfs package in Ubuntu: Fix Released Status in libnfs source package in Xenial: New Status in libnfs source package in Bionic: New Status in libnfs source package in Cosmic: New Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = gvfs 1.24 added an NFS backend 3 years ago. It was enabled in Debian a year ago, but we can't enable it in Ubuntu until libnfs is promoted to main. The Ubuntu bug for this feature to be enabled in gvfs is LP: #1637988 qemu-block-extra could also enable libnfs support. Security No known CVEs. https://security-tracker.debian.org/tracker/source-package/libnfs https://launchpad.net/ubuntu/+source/libnfs/+cve Quality assurance = - Desktop Packages team is subscribed. - dh_auto_test runs but the tests shipped by upstream cant'b be run at build time since they modify the system. - Autopkgtests are added in 3.0.0-1, running upstream's test suite which includes running tests with valgrind, too. https://bugs.launchpad.net/ubuntu/+source/libnfs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libnfs https://github.com/sahlberg/libnfs/issues https://autopkgtest.ubuntu.com/packages/libn/libnfs (failing, never passed: see https://bugs.debian.org/921578 ) https://ci.debian.net/packages/libn/libnfs/ (tests aren't run in Debian because they request machine isolation which isn't implemented there yet) Dependencies No universe binary dependencies Standards compliance 3.9.8, debhelper compat 9, dh7 simple rules Maintenance === Actively maintained: https://github.com/sahlberg/libnfs Not team maintained in Debian. https://tracker.debian.org/pkg/libnfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Also affects: virtualbox-hwe (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation2 in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in activemq source package in Bionic: Fix Committed Status in afterburner.fx source package in Bionic: Fix Committed Status in annotation-indexer source package in Bionic: Fix Committed Status in apache-directory-server source package in Bionic: Fix Committed Status in aspectj source package in Bionic: Fix Committed Status in aspectj-maven-plugin source package in Bionic: Fix Committed Status in batik source package in Bionic: Fix Committed Status in bindex source package in Bionic: Fix Committed Status in bridge-method-injector source package in Bionic: Fix Committed Status in carrotsearch-hppc source package in Bionic: Fix Committed Status in clojure source package in Bionic: Fix Committed Status in clojure1.8 source package in Bionic: Fix Committed Status in commons-httpclient source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in ecj source package in Bionic: Fix Committed Status in eclipselink source package in Bionic: Fix Committed Status in elki source package in Bionic: Fix Committed Status in figtree source package in Bionic: Fix Committed Status in fontawesomefx source package in Bionic: Fix Committed Status in gettext source package in Bionic: Fix Committed Status in gluegen2 source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in hikaricp source package in Bionic: Fix Committed Status in hsqldb source package in Bionic: Fix Committed Status in hsqldb1.8.0 source package in Bionic: Fix Committed Status in insubstantial source package in Bionic: Fix Committed Status in jabref source package in Bionic: Fix Committed Status in jackson-core source package in Bionic: Fix Committed Status in jackson-databind source package in Bionic: Fix Committed Status in jackson-dataformat-xml source package in Bionic: Fix Committed Status in jackson-module-jaxb-annotations source package in Bionic: Fix Committed Status in java-common source package in Bionic: Fix Committed Status in javafxsvg source package in Bionic: Fix Committed Status in javamail source package in Bionic: Fix Committed Status in javatools source package in Bionic: Fix Committed Status in jboss-classfilewriter source package in Bionic: Fix Committed Status in jboss-jdeparser2 source package in Bionic: Fix Committed Status in jboss-modules source package in Bionic: Fix Committed Status in jcommander source package in Bionic: Fix Committed Status in jersey1 source package in Bionic: Fix Committed Status in jftp source package in Bionic: Fix Committed Status in jhove source package in Bionic: Fix Committed Status in jmdns source package in Bionic: Fix Committed Status in jnr-posix source package in Bionic: Fix Committed Status in jruby source package in Bionic: Fix Committed Status in jruby-openssl source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in jts source package in Bionic: Fix Committed Status in junit4 source package in Bionic: Fix Committed Status in jxgrabkey source package in Bionic: Fix Committed Status in jython source package in Bionic: Fix Committed Status in libapache-poi-java source package in Bionic: Fix Committed Status in libbtm-java source package in Bionic: Fix Committed Status in libcommons-collections3-java source package in Bionic: Fix Committed Status in
[Desktop-packages] [Bug 1819184] Re: LO 6.2.1.1 Popup on Files, Edits, etc out of position
This appears to be a GTK3 bug, will withdraw issue. ** Changed in: libreoffice (Ubuntu) Status: New => Invalid -- 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/1819184 Title: LO 6.2.1.1 Popup on Files, Edits, etc out of position Status in libreoffice package in Ubuntu: Invalid Bug description: When one clicks on the Files, Edit, View, Insert, etc the popup window is positions to the top of the desktop. In addition the spacing between the popup items is much larger than 6.1 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Mar 8 08:57:51 2019 InstallationDate: Installed on 2019-03-01 (6 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190131) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1819184/+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 1819184] Re: LO 6.2.1.1 Popup on Files, Edits, etc out of position
Its also visible on a higher resolution system: ** Attachment added: "Selection_106.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1819184/+attachment/5245400/+files/Selection_106.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1819184 Title: LO 6.2.1.1 Popup on Files, Edits, etc out of position Status in libreoffice package in Ubuntu: New Bug description: When one clicks on the Files, Edit, View, Insert, etc the popup window is positions to the top of the desktop. In addition the spacing between the popup items is much larger than 6.1 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Mar 8 08:57:51 2019 InstallationDate: Installed on 2019-03-01 (6 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190131) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1819184/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: mongo-java-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation2 in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in saaj package in Ubuntu: New Status in activemq source package in Bionic: Fix Committed Status in afterburner.fx source package in Bionic: Fix Committed Status in annotation-indexer source package in Bionic: Fix Committed Status in apache-directory-server source package in Bionic: Fix Committed Status in aspectj source package in Bionic: Fix Committed Status in aspectj-maven-plugin source package in Bionic: Fix Committed Status in batik source package in Bionic: Fix Committed Status in bindex source package in Bionic: Fix Committed Status in bridge-method-injector source package in Bionic: Fix Committed Status in carrotsearch-hppc source package in Bionic: Fix Committed Status in clojure source package in Bionic: Fix Committed Status in clojure1.8 source package in Bionic: Fix Committed Status in commons-httpclient source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in ecj source package in Bionic: Fix Committed Status in eclipselink source package in Bionic: Fix Committed Status in elki source package in Bionic: Fix Committed Status in figtree source package in Bionic: Fix Committed Status in fontawesomefx source package in Bionic: Fix Committed Status in gettext source package in Bionic: Fix Committed Status in gluegen2 source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in hikaricp source package in Bionic: Fix Committed Status in hsqldb source package in Bionic: Fix Committed Status in hsqldb1.8.0 source package in Bionic: Fix Committed Status in insubstantial source package in Bionic: Fix Committed Status in jabref source package in Bionic: Fix Committed Status in jackson-core source package in Bionic: Fix Committed Status in jackson-databind source package in Bionic: Fix Committed Status in jackson-dataformat-xml source package in Bionic: Fix Committed Status in jackson-module-jaxb-annotations source package in Bionic: Fix Committed Status in java-common source package in Bionic: Fix Committed Status in javafxsvg source package in Bionic: Fix Committed Status in javamail source package in Bionic: Fix Committed Status in javatools source package in Bionic: Fix Committed Status in jboss-classfilewriter source package in Bionic: Fix Committed Status in jboss-jdeparser2 source package in Bionic: Fix Committed Status in jboss-modules source package in Bionic: Fix Committed Status in jcommander source package in Bionic: Fix Committed Status in jersey1 source package in Bionic: Fix Committed Status in jftp source package in Bionic: Fix Committed Status in jhove source package in Bionic: Fix Committed Status in jmdns source package in Bionic: Fix Committed Status in jnr-posix source package in Bionic: Fix Committed Status in jruby source package in Bionic: Fix Committed Status in jruby-openssl source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in jts source package in Bionic: Fix Committed Status in junit4 source package in Bionic: Fix Committed Status in jxgrabkey source package in Bionic: Fix Committed Status in jython source package in Bionic: Fix Committed Status in libapache-poi-java source package in Bionic: Fix Committed Status in libbtm-java source package in Bionic: Fix Committed Status in libcommons-collections3-java source package in Bionic: Fix Committed Status in libcommons-collections4-java source package in Bionic: Fix Committed Status in libcommons-compress-java source package in Bionic: Fix Committed Status in
[Desktop-packages] [Bug 1818862] Re: Totem player hangs when seeking video
** Changed in: totem Status: Unknown => New -- 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/1818862 Title: Totem player hangs when seeking video Status in Totem: New Status in intel-vaapi-driver package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: Totem player hangs as soon as I click on the bar at the bottom to seek to a specific time in an mp4 video. Video in question can be found here: https://cdn.media.ccc.de/congress/2018/h264-hd/35c3-9370-eng-deu- Hacking_how_we_see_hd.mp4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6.2 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: ubuntu:GNOME Date: Wed Mar 6 16:10:11 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-08 (453 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-05-02 (308 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1818862/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: libpdfbox-java (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation2 in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in octave package in Ubuntu: New Status in saaj package in Ubuntu: New Status in activemq source package in Bionic: Fix Committed Status in afterburner.fx source package in Bionic: Fix Committed Status in annotation-indexer source package in Bionic: Fix Committed Status in apache-directory-server source package in Bionic: Fix Committed Status in aspectj source package in Bionic: Fix Committed Status in aspectj-maven-plugin source package in Bionic: Fix Committed Status in batik source package in Bionic: Fix Committed Status in bindex source package in Bionic: Fix Committed Status in bridge-method-injector source package in Bionic: Fix Committed Status in carrotsearch-hppc source package in Bionic: Fix Committed Status in clojure source package in Bionic: Fix Committed Status in clojure1.8 source package in Bionic: Fix Committed Status in commons-httpclient source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in ecj source package in Bionic: Fix Committed Status in eclipselink source package in Bionic: Fix Committed Status in elki source package in Bionic: Fix Committed Status in figtree source package in Bionic: Fix Committed Status in fontawesomefx source package in Bionic: Fix Committed Status in gettext source package in Bionic: Fix Committed Status in gluegen2 source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in hikaricp source package in Bionic: Fix Committed Status in hsqldb source package in Bionic: Fix Committed Status in hsqldb1.8.0 source package in Bionic: Fix Committed Status in insubstantial source package in Bionic: Fix Committed Status in jabref source package in Bionic: Fix Committed Status in jackson-core source package in Bionic: Fix Committed Status in jackson-databind source package in Bionic: Fix Committed Status in jackson-dataformat-xml source package in Bionic: Fix Committed Status in jackson-module-jaxb-annotations source package in Bionic: Fix Committed Status in java-common source package in Bionic: Fix Committed Status in javafxsvg source package in Bionic: Fix Committed Status in javamail source package in Bionic: Fix Committed Status in javatools source package in Bionic: Fix Committed Status in jboss-classfilewriter source package in Bionic: Fix Committed Status in jboss-jdeparser2 source package in Bionic: Fix Committed Status in jboss-modules source package in Bionic: Fix Committed Status in jcommander source package in Bionic: Fix Committed Status in jersey1 source package in Bionic: Fix Committed Status in jftp source package in Bionic: Fix Committed Status in jhove source package in Bionic: Fix Committed Status in jmdns source package in Bionic: Fix Committed Status in jnr-posix source package in Bionic: Fix Committed Status in jruby source package in Bionic: Fix Committed Status in jruby-openssl source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in jts source package in Bionic: Fix Committed Status in junit4 source package in Bionic: Fix Committed Status in jxgrabkey source package in Bionic: Fix Committed Status in jython source package in Bionic: Fix Committed Status in libapache-poi-java source package in Bionic: Fix Committed Status in libbtm-java source package in Bionic: Fix Committed Status in libcommons-collections3-java source package in Bionic: Fix Committed Status in libcommons-collections4-java source package in Bionic: Fix Committed Status in libcommons-compress-java source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in
[Desktop-packages] [Bug 1811908] Re: gnome-shell: JS ERROR: ReferenceError: GLib is not defined
Tested in gnome-shell 3.28.3+git20190124-0ubuntu18.04.1, No error is spawned here. ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1811908 Title: gnome-shell: JS ERROR: ReferenceError: GLib is not defined Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Bug description: [ Impact ] Gnome-shell in Bionic spams the journal with error such as: giu 05 17:33:24 tricky gnome-shell[4049]: JS ERROR: ReferenceError: GLib is not defined _sliderChanged/this._notifyVolumeChangeId<@resource:///org/gnome/shell/ui/status/volume.js:163:17 When changing the volume scrolling over the volume indicator. [ Test case ] - Run `journalctl -ef -b0 /usr/bin/gnome-shell` - Scroll with the mouse over the volume indicator - No error should be spammed by gnome-shell metnioning a ReferenceError [ Regression potential ] None, a JS include is missing, and adding it can't canuse any trouble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811908/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Kay-Heng, what's the status of the linux image landing on bionic? Can you help in verify this once we've all there? -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend
** 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1805444 Title: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Bug description: [ Description ] Wayland sessions don't work with the Nvidia driver in 18.04, even after enabling them via the kernel command line 'nvidia- drm.modeset=1'. [ Fix ] See below for the changes from upstream that fix this, which we're uploading to disco-proposed now. [ QA ] Under the GNOME Micro Release Exception, you can believe this is fixed. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME It might be a good idea to test an nvidia machine, but it doesn't need explicit verification. [Original description] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due to following missing changes in mutter 3.28.3-2~ubuntu18.04.2 commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84 Author: Miguel A. Vico Date: Thu Jun 7 16:29:44 2018 -0700 renderer/native: Choose first EGL config for non-GBM backends Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only choose EGL configs that match the GBM_FORMAT_XRGB pixel format. However, there won't be any EGL config satisfying such criteria for non-GBM backends, such as EGLDevice. This change will let us choose the first EGL config for the EGLDevice backend, while still forcing GBM_FORMAT_XRGB configs for the GBM one. Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2 commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b Author: Jonas Ådahl Date: Tue Nov 14 16:08:52 2017 +0800 renderer/native: Also wrap flip closures for EGLStreams When using the EGLStream backend, the MetaRendererNative passed a GClosure to KMS when using EGLStreams, but KMS flip callback event handler in meta-gpu-kms.c expected a closure wrapped in a closure container, meaning it'd instead crash when using EGLStreams. Make the flip handler get what it expects also when using EGLStreams by wrapping the flip closure in the container before handing it over to EGL. https://bugzilla.gnome.org/show_bug.cgi?id=790316 apt-cache policy mutter mutter: Installed: 3.28.3-2~ubuntu18.04.2 Candidate: 3.28.3-2~ubuntu18.04.2 Version table: *** 3.28.3-2~ubuntu18.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+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 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
Daniel, while the fix¹ didn't landed yet it will land on 3.32.1². [1] TBH this isn't really a fix for the problem itself but at least in ubuntu where we compile without `G_DISABLE_CHECKS` will mute the crash, making things for us at least good enough to close this. [2] https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/438 -- 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796606/+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 1819126] Re: gnome-shell crashed with SIGABRT [St:ERROR:../src/st/st-image-content.c:155:st_image_content_get_preferred_size: assertion failed (priv->width > -1): (-1 > -1)]
** Tags added: fixed-3.32.0 -- 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/1819126 Title: gnome-shell crashed with SIGABRT [St:ERROR:../src/st/st-image- content.c:155:st_image_content_get_preferred_size: assertion failed (priv->width > -1): (-1 > -1)] Status in gnome-shell package in Ubuntu: Fix Committed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1027 https://errors.ubuntu.com/problem/40bb6815b23393e7dfa95f5895de4b0603ac431b --- The crash happened when a new application or system crash report window from update-notifier showed up. Reproducer: 1. sleep 1000 on one terminal 2. kill -SIGSEGV $(pidof sleep) -> wait for update-notifier to try showing up apport (application crash) or update-notifier (system crash) windows. This can take up to 180s. - ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.92-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 09:32:41 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-05-24 (287 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/bin/gnome-shell Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_cmpnum () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so clutter_actor_get_preferred_size () at /usr/lib/x86_64-linux-gnu/mutter-4/libmutter-clutter-4.so.0 clutter_actor_get_transformed_size () at /usr/lib/x86_64-linux-gnu/mutter-4/libmutter-clutter-4.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: Upgraded to disco on 2019-01-08 (58 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819126/+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 1818516] Re: FFe: Mesa 19.0.x for disco
what testing has happened / what are the risks? -- 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/1818516 Title: FFe: Mesa 19.0.x for disco Status in mesa package in Ubuntu: New Bug description: Mesa 19.0.0 will be soon released, and we should get that for disco, and then follow point-releases until the last one is released (roughly next July, will need an SRU). We'll also migrate it to use LLVM 8. New features according to upstream release notes: GL_AMD_texture_texture4 on all GL 4.0 drivers. GL_EXT_shader_implicit_conversions on all drivers (ES extension). GL_EXT_texture_compression_bptc on all GL 4.0 drivers (ES extension). GL_EXT_texture_compression_rgtc on all GL 3.0 drivers (ES extension). GL_EXT_render_snorm on gallium drivers (ES extension). GL_EXT_texture_view on drivers supporting texture views (ES extension). GL_OES_texture_view on drivers supporting texture views (ES extension). GL_NV_shader_atomic_float on nvc0 (Fermi/Kepler only). Shader-based software implementations of GL_ARB_gpu_shader_fp64, GL_ARB_gpu_shader_int64, GL_ARB_vertex_attrib_64bit, and GL_ARB_shader_ballot on i965. VK_ANDROID_external_memory_android_hardware_buffer on Intel Fixed and re-exposed VK_EXT_pci_bus_info on Intel and RADV VK_EXT_scalar_block_layout on Intel and RADV VK_KHR_depth_stencil_resolve on Intel VK_KHR_draw_indirect_count on Intel VK_EXT_conditional_rendering on Intel VK_EXT_memory_budget on RADV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+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 1819183] Re: FFe: Update pygobject to 3.32
Yep, sure. (Ideally as a sync.) It'd be nicer for me in future if you could paste the NEWS entries and other things, so that I can read it all and reply directly from my email client. :-) ** Changed in: pygobject (Ubuntu) Status: New => Confirmed ** Changed in: pygobject (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1819183 Title: FFe: Update pygobject to 3.32 Status in pygobject package in Ubuntu: Confirmed Bug description: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.32.0-1 is in Debian experimental ready to be synced over once this FFe is approved. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
I also opened a bug report for Mesa (https://bugs.freedesktop.org/show_bug.cgi?id=109958) as the glxgears problem occurs on different distributions, not just (K)ubuntu. ** Bug watch added: freedesktop.org Bugzilla #109958 https://bugs.freedesktop.org/show_bug.cgi?id=109958 -- 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/1815693 Title: Kubuntu 18.10 Xorg severe memory leak Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-vmware package in Ubuntu: Confirmed Bug description: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR; I have today logged the memory consumption while I was handling some bills and linked is a log of constantly increasing Xorg memory usage. So it goes until it chokes the machine and only a hard reboot is possible. My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see how the Xorg usage creeps up. https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0 I should add that this bug seems specific to Kubuntu, and (I guess) associated with running under Virtualbox. I have another Ubuntu 18.04 (i.e. not _K_ubuntu) running on bare metal and it is not having any problems. Please advise what additional information I should post to have this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Feb 13 01:00:13 2019 DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2015-10-22 (1209 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1815693/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1803127] Re: remmina not able to redirect smart card reader
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: remmina (Ubuntu) Status: New => Confirmed -- 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/1803127 Title: remmina not able to redirect smart card reader Status in remmina package in Ubuntu: Confirmed Bug description: Linux Mint 19 1.2.0-rcgit-29 (git rcgit-29) Cinamon Windows 7 Pro RDP remmina: Installed: 1.2.0-rcgit.29+dfsg-1ubuntu1 Candidate: 1.2.0-rcgit.29+dfsg-1ubuntu1 Version table: *** 1.2.0-rcgit.29+dfsg-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages I expect to see working solution for this problem. The same problem is and with Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1803127/+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 1803127] Re: remmina not able to redirect smart card reader
Ubuntu Mate 18.04 1.2.0-rcgit-29 (git rcgit-29) Package: remmina Architecture: amd64 Version: 1.2.0-rcgit.29+dfsg-1ubuntu1 Multi-Arch: foreign Priority: optional Section: gnome Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian Remote Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 441 Depends: libappindicator3-1 (>= 0.4.90), libavahi-client3 (>= 0.6.16), libavahi-common3 (>= 0.6.16), libavahi-ui-gtk3-0 (>= 0.6.30), libc6 (>= 2.15), libcairo2 (>= 1.6.0), libgcrypt20 (>= 1.8.0), libglib2.0-0 (>= 2.41.2), libgtk-3-0 (>= 3.21.5), libjson-glib-1.0-0 (>= 1.2.0), libpango-1.0-0 (>= 1.14.0), libsoup2.4-1 (>= 2.41.90), libssh-4 (>= 0.6.1), libssl1.1 (>= 1.1.0), libvte-2.91-0 (>= 0.49.92), remmina-common (= 1.2.0-rcgit.29+dfsg-1ubuntu1), default-dbus-session-bus | dbus-session-bus Recommends: remmina-plugin-rdp, remmina-plugin-vnc, remmina-plugin-secret Suggests: remmina-plugin-exec, remmina-plugin-nx, remmina-plugin-spice, remmina-plugin-telepathy, remmina-plugin-xdmcp Filename: pool/main/r/remmina/remmina_1.2.0-rcgit.29+dfsg-1ubuntu1_amd64.deb It happens the same to me too. The smart card is not shared. -- 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/1803127 Title: remmina not able to redirect smart card reader Status in remmina package in Ubuntu: Confirmed Bug description: Linux Mint 19 1.2.0-rcgit-29 (git rcgit-29) Cinamon Windows 7 Pro RDP remmina: Installed: 1.2.0-rcgit.29+dfsg-1ubuntu1 Candidate: 1.2.0-rcgit.29+dfsg-1ubuntu1 Version table: *** 1.2.0-rcgit.29+dfsg-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages I expect to see working solution for this problem. The same problem is and with Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1803127/+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 1812593] Re: gnome-shell[3159]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argumen
Hi, I believe my problem is related to this bug report. I am running Ubuntu 18.04.2 with GNOME 3.28.2, intel graphics and dual screen. The /var/log/syslog file keeps on expanding out of control. I believe this is happening when the screen is locked. If the screen is locked for a long time, it is impossible to unlock it (it becomes kind of frozen). Eventually, the syslog file fills the whole disk (it grows well beyond 100 GB) and the system does not boot any longer. Also when the screen is locked the system keeps on cycling between turning on and off the monitors. As far as I can tell from gnome-shell-extension-prefs (I am new to Gnome), I do not have any active extensions. Here are some examples from the log files: Mar 11 11:23:42 ctt73 gnome-shell[1726]: Object St.BoxLayout (0x5632e3e0ee50), has been already finalized. Impossible to set any property to it. Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #5 0x7ffd1fb51fa0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff05c1b5de0 @ 71) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #6 0x7ffd1fb52060 b self-hosted:916 (0x7ff05c1f12b8 @ 367) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: == Stack trace for context 0x5632e1d1d330 == Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #0 0x7ffd1fb51140 b resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7ff04c5c7780 @ 273) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #1 0x7ffd1fb511a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff05c1b5de0 @ 71) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #2 0x7ffd1fb51260 b self-hosted:916 (0x7ff05c1f12b8 @ 367) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #3 0x7ffd1fb51350 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7ff05c1d2230 @ 386) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #4 0x5632e20ac1c0 i resource:///org/gnome/shell/ui/layout.js:531 (0x7ff04c5042b8 @ 127) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #5 0x7ffd1fb51fa0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff05c1b5de0 @ 71) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #6 0x7ffd1fb52060 b self-hosted:916 (0x7ff05c1f12b8 @ 367) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: == Stack trace for context 0x5632e1d1d330 == Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #0 0x7ffd1fb51140 b resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7ff04c5c7780 @ 231) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #1 0x7ffd1fb511a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff05c1b5de0 @ 71) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #2 0x7ffd1fb51260 b self-hosted:916 (0x7ff05c1f12b8 @ 367) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #3 0x7ffd1fb51350 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7ff05c1d2230 @ 386) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #4 0x5632e20ac1c0 i resource:///org/gnome/shell/ui/layout.js:531 (0x7ff04c5042b8 @ 127) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #5 0x7ffd1fb51fa0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff05c1b5de0 @ 71) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #6 0x7ffd1fb52060 b self-hosted:916 (0x7ff05c1f12b8 @ 367) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: == Stack trace for context 0x5632e1d1d330 == Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #0 0x7ffd1fb51140 b resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7ff04c5c7780 @ 273) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #1 0x7ffd1fb511a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff05c1b5de0 @ 71) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #2 0x7ffd1fb51260 b self-hosted:916 (0x7ff05c1f12b8 @ 367) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #3 0x7ffd1fb51350 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7ff05c1d2230 @ 386) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #4 0x5632e20ac1c0 i resource:///org/gnome/shell/ui/layout.js:531 (0x7ff04c5042b8 @ 127) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #5 0x7ffd1fb51fa0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff05c1b5de0 @ 71) Mar 11 11:23:42 ctt73 org.gnome.Shell.desktop[1726]: #6 0x7ffd1fb52060 b self-hosted:916 (0x7ff05c1f12b8 @ 367) [...] Mar 11 11:23:42 ctt73 gsd-color[1869]: failed to set screen _ICC_PROFILE: Failed to open file “/var/lib/gdm3/.local/share/icc/edid-4a23aee44db8689f4e3980330b1875c2.icc”: Permission denied Mar 11 11:23:42 ctt73 gsd-color[1869]: message repeated 4 times: [ failed to set screen _ICC_PROFILE: Failed to open file “/var/lib/gdm3/.local/share/icc/edid-4a23aee44db8689f4e3980330b1875c2.icc”: Permission denied] Mar 11 11:24:05 ctt73 gnome-shell[1726]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got
[Desktop-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or the battery % is above 20 - 40%
There you go ** Attachment added: "allpackages.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+attachment/5245381/+files/allpackages.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or the battery % is above 20 - 40% Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+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 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)
I have the same bug. I used to work around this by installing an alternative sound device selector shell extension but this one broke down when Gnome shell upgraded to 3.31.91. So now there is no way for me to switch to HDMI output any more. The select box shows the correct devices but selecting a different one has no effect. It is also not saved and when reopening control center the default device is once again selected. -- 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/1817338 Title: HDMI sound output not selectable in 19.04 (but works in 18.10) Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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
