[Desktop-packages] [Bug 1699637] Re: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1699637 Title: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Status in Light Display Manager: New Status in lightdm package in Ubuntu: New Bug description: lightdm work fine with xfce4(arch linux),but when i check it's status by systemd,it show this message. Jun 21 15:55:38 archlinux systemd[1]: Starting Light Display Manager... Jun 21 15:55:38 archlinux systemd[1]: Started Light Display Manager. Jun 21 15:55:38 archlinux lightdm[417]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jun 21 15:55:38 archlinux lightdm[465]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid Jun 21 15:55:47 archlinux lightdm[417]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jun 21 15:55:47 archlinux lightdm[607]: pam_unix(lightdm:session): session opened for user jaken by (uid=0) Jun 21 17:58:33 archlinux lightdm[417]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1699637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode
don't know what's the difference between #10 and LP: #1731873 #4 for version 1:0.4.17.4 in Xenial, #9 and LP: #1731873 #3 for version 1:0.4.22.2 in zesty. btw, anyway, will switch it to verification-done. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1728547 Title: SRU: Add support for keeping the dGPU on in power saving mode Status in HWE Next: New Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Committed Status in ubuntu-drivers-common source package in Zesty: Fix Committed Status in ubuntu-drivers-common source package in Artful: Fix Committed Bug description: SRU Request: [Impact] Some systems don't play well when the dGPU is disabled. It should still be possible to use the Intel iGPU without disabling the dGPU. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common" 2) Make sure the nvidia packages are installed, and enable power saving mode: sudo prime-select intel 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Install the mesa-utils package: sudo apt install mesa-utils 5) Check the output of the following command (which should mention Intel): glxinfo | grep OpenGL [Regression Potential] Low, as the feature is disabled by default. This is only for hardware specific workarounds. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1728547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731873] Re: Backport amdgpu-pro support
based on https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1728547 #10 and #9 , the verification was done. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1731873 Title: Backport amdgpu-pro support Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Committed Status in ubuntu-drivers-common source package in Zesty: Fix Committed Bug description: SRU Request: [Impact] Support for the amdgpu-pro driver has been available in Artful since May 2017. We need to backport the code to the other stable releases. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common" 2) Make sure the amdgpu-pro packages are installed (if not, install them, and restart your system). 3) Check that power saving mode is supported: amdgpu-pro-px --ispx If it returns true, then it is supported by the hardware. 4) Set power saving mode: sudo amdgpu-pro-px --mode powersaving 5) Restart your computer and check that the "Enabling power saving mode for amdgpu-pro" line is in your /var/log/gpu-manager.log. 6) Install the mesa-utils package: sudo apt install mesa-utils 7) Check the output of the following command (which should mention Intel): glxinfo | grep OpenGL [Regression Potential] Low, as the feature is disabled by default, unless users set power saving manually. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1731873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
About the Iscan, PNG and JPEG phenomenon: Iscan's png support still depends on an very old version of libpng. If this library isn't found support for the PNG format is dropped. I guess, libjpeg has been renamed (and most probably has changed its interface), as well. -- 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/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
Tim, are you really saying just that one-line change fixed it?... I can confirm at least that /usr/share/gdm/generate-config is introduced only by Debian/Ubuntu packaging. It's not part of the upstream GDM project. So if Fedora's approach of running under xinit works then we should probably do the same. I can't yet see why it works though. ** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu) ** Tags added: multimonitor -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: New Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736232] Re: GNOME Software shows U1 login for snaps
** Tags removed: verification-needed verification-needed-zesty ** Tags added: verification-done verification-done-zesty -- 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/1736232 Title: GNOME Software shows U1 login for snaps Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: As I understood it, GNOME Software is no longer supposed to be asking for U1 logins when installing snaps. I just did a clean up to date install of 16.04.3 and tried launching G-S and it asked me for a U1 login. Steps to reproduce: Install 16.04.3 Update to latest software in the repo Open Ubuntu Software Click the "hiri" banner Click install button Expected behaviour:- Policykit login box appears Actual behaviour:- Ubuntu One login/sign up box appears ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.5-0ubuntu0.16.04.6 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 4 19:56:34 2017 InstallationDate: Installed on 2017-12-04 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1736232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727310] Re: Screen brightness slider isn't working on Acer Aspire v5 571g
I'm experiencing the same. Acer Aspire S7 392. Worked under 17.04, not under 17.10. The only way I can change my screen brightness currently is via the command line: sudo tee /sys/class/backlight/intel_backlight/brightness <<< 200 -- 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/1727310 Title: Screen brightness slider isn't working on Acer Aspire v5 571g Status in gnome-shell package in Ubuntu: New Bug description: changing the screen brightness does not work when you try to change the slider on the toolbar at the top right ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 17:10:04 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-08-27 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1561278] Re: internal sound card not detected HP X2
I just installed Ubuntu Mate 16.04 and kernel 4.12, it gives me the best results so far: - Internal audio: no sound, detected as bytcht-nocodec 1 ouput/1 input - HDMI audio: works fine, tested with chrome and rhythmbox - HDMI video: works fine - Touchscreen: simple touch only, for example: on web pages can scroll, but on text editors select text instead of scroll - Card Reader: not mounted automatically on startup, unless lock session and session restarts, sd mounts automatically, sometimes gives error, but still mounts - Battery icon: works fine - Bluethooth: seems to work fine, detects devices - Lock button: not working - Start button: not working - up/down volume: not working - wifi: some times get stuck, but in general works great - camera: tried webcamoid, but doesn't start. Cheese says device not found. -- 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/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Phillip: You were banned from the Ubuntu Forms not by me personally, but rather by the Forums Council after repeated violations of the CoC and difficult interactions with the Forums Staff including both moderators and Forums Council Members. You appealed your ban to the Community Council, and your ban was upheld. This is not the appropriate place to protest you ban. I am no longer an active staff member, please contact the current Forums Council if you wish to discuss any potential future use of the Forums https://wiki.ubuntu.com/ForumCouncil As far as the technical discussion I am afraid we will have to agree to disagree. I can not always follow what you are saying, but I have the impression, perhaps falsely, you do not understand or that you intermingle issues of Wayland, X (XWayland, Xhost), and Weston, those are fairly diverse features / functions. At any rate, I also think you do not understand that Wayland is in rapid development and not all the mechanisms of security have been agreed on up stream or resolved. I believe Upstream has made their security intentions very clear in their mailing list and security blog, which I have provided for your consideration. The fedora experience makes this very clear in their bug reports as well. The Fedora project has raised most if not all of your issues, and as they are a bit further ahead, the Fedora Bug Reports are referenced here. This thread makes it clear that Ubuntu is working not on revamping wayland security, but by rewriting applications and the way they obtain elevated privileges. I also see your bugs getting closed as "wont fix" here on Ubuntu. My best suggestion would be that you engage into a technical discussion with your LP mentor, the community council, perhaps Norbert, or one of the Gnome Developers whom you respect rather than continue a discussion with myself, here, on this bug report. I suggest you conduct such a technical discussion outside this bug report, perhaps on the gnome or wayland mailing list or IRC or whatever channel you feel benefits you most. I have given you the Wayland mailing list and links to security discussions and can send them again if you would like. I believe this bug report is not the best place to obtain the clarification and answers to your questions and I have in good faith provided you and others what I would hope would be helpful information and sources of further information. bodhi@daemon:~$sudo gedit No protocol specified Unable to init server: Could not connect: Connection refused (gedit:7374): Gtk-WARNING **: cannot open display: :0 bodhi@daemon:~$sudo su - root@daemon:~#gedit Unable to init server: Could not connect: Connection refused (gedit:7346): Gtk-WARNING **: cannot open display: I believe once Upstream (Wayland) feels the wayland code has matured their long term intentions will be to drop XWayland and support for circumventing wayland security via the mechanisms you currently use / exploit such as Xhost , su - , etc. I believe Xwayland and Xhost are intended to give downstream projects such a Fedora and Ubuntu time to transition from X to Wayland and time for Wayland to mature. Obviously this is a large project, both for Wayland and Ubuntu . I do not believe that because mechanisms currently exist to run applications as root on Wayland at this time that you should assume that such mechanisms will either be maintained or expanded in the future. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status i
[Desktop-packages] [Bug 1723197] Re: cups-browsed crashed with signal 7 in elf_machine_rel_relative()
[Expired for cups-filters (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups-filters (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1723197 Title: cups-browsed crashed with signal 7 in elf_machine_rel_relative() Status in cups-filters package in Ubuntu: Expired Bug description: I was booting using kernel 4.13.0-14-generic-i686 to see if bug #1723033 occurred. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-browsed 1.17.9-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-14.15-generic 4.13.4 Uname: Linux 4.13.0-14-generic i686 ApportVersion: 2.20.7-0ubuntu3 Architecture: i386 Date: Thu Oct 12 18:17:39 2017 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2017-07-28 (75 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170725.1) Lpstat: device for Brother-HL-2250DN-series: dnssd://Brother%20HL-2250DN%20series._pdl-datastream._tcp.local/ MachineType: NOVATECH LTD PERSONAL COMPUTER Papersize: a4 PpdFiles: Brother-HL-2250DN-series: Brother HL-2250DN - CUPS+Gutenprint v5.2.13 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-14-generic root=UUID=650586f6-4f8f-4d72-853f-15154b747716 ro quiet splash vt.handoff=7 Signal: 7 SourcePackage: cups-filters StacktraceTop: elf_machine_rel_relative (reloc_addr_arg=0xb721f28c, reloc=0xb7158464, l_addr=3071598592) at ../sysdeps/i386/dl-machine.h:636 elf_dynamic_do_Rel (skip_ifunc=, lazy=, nrelative=, relsize=, reladdr=, map=0xb728c650) at do-rel.h:112 _dl_relocate_object (scope=, reloc_mode=, consider_profiling=) at dl-reloc.c:259 dl_main (phdr=, phnum=, user_entry=, auxv=) at rtld.c:2187 _dl_sysdep_start (start_argptr=0xbfe792a0, dl_main=0xb7f65cc0 ) at ../elf/dl-sysdep.c:253 Title: cups-browsed crashed with signal 7 in elf_machine_rel_relative() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: xxx-xxx dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: PERSONAL COMPUTER dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1723197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
Celebratory fireworks from me. It seems to work. For ubuntu the only difference is [Service] ExecStartPre=/usr/share/gdm/generate-config becomes [Service] ExecStartPre=/usr/bin/xinit /usr/share/gdm/generate-config I have a proper ubuntu gnome session running with gdm, an external monitor and laptop panel, with prime sync on and no flickering, running 'ubuntu on xorg' *** FOR THE FIRST TIME EVER *** on my thinkpad W520 which is old but is a genuine Optimus laptop with Quadro graphics on the nvidia 387.34 binary driver in Optimus mode. -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gnome-shell package in Ubuntu: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
** Tags added: hidpi -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling Status in Mutter: In Progress Status in Ubuntu GNOME: Triaged Status in gnome-shell package in Ubuntu: In Progress Bug description: https://trello.com/c/r12LY9iA (for 17.04 was https://trello.com/c/TvwNvXOo) --- I'm using fully updated Ubuntu GNOME 17.04. In Ubuntu Gnome, you only allow for integer scaling of things for high DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor like mine, restricting it to integers is a problem. 1x is annoyingly small, and 2x is WAY too big. You need a 1.5x, and presumably to just allow most noninteger values to future proof the distribution given 8k monitors and all sorts of new and weird things coming out, like windows 10 has. Photos of the two annoying sizes are available here (it won't let me attach two files): http://i.imgur.com/vWrvZxq.jpg http://i.imgur.com/11p19k7.jpg I apologize for my photography skills in advance., you'll have to look at the ruler for scale to see the problem. Please contact me if you need any more information etc. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
ubuntu user Hon Weng Chong has emailed me as he continues to investigate the
problem.
He believes he has proof that it is is GDM configuration issue and has provided
the following fix
Hey Tim,
I figured out a hack solution to the GDM prime issue. If you replace
/lib/systemd/system/gdm3.service with this file:
https://gist.github.com/hwchong/b3634b387e91b38d355a0500ffecfc7d
and /etc/X11/xorg.conf with this:
https://gist.github.com/hwchong/28d7c70aafd62a0d3114c5746da7da36
You should be able to use Prime Sync with your Intel graphics card and
have an external monitor connected to the Nvidia GPU without using
LightDM.
Cheers,
Hon
His proposed changes to xorg are probably not significant. He is proposing to
add this to nvidia options, but this can be done via the GUI or command line.
Option "metamodes" "nvidia-auto-select +0+0
{ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
The revised /lib/systemd/system/gdm3.service he proposes is
is
--> Compared to Fedora 27's config, changes seem to be the addition of
ExecStartPre=/usr/bin/xinit /usr/share/gdm/generate-config
.
.
.
RestartSec=1s
ExecReload=/usr/share/gdm/generate-config
[Unit]
Description=GNOME Display Manager
# replaces the getty
Conflicts=getty@tty1.service
After=getty@tty1.service
# replaces plymouth-quit since it quits plymouth on its own
Conflicts=plymouth-quit.service
After=plymouth-quit.service
# Needs all the dependencies of the services it's replacing
# pulled from getty@.service and plymouth-quit.service
# (except for plymouth-quit-wait.service since it waits until
# plymouth is quit, which we do)
After=rc-local.service plymouth-start.service systemd-user-sessions.service
# GDM takes responsibility for stopping plymouth, so if it fails
# for any reason, make sure plymouth still stops
OnFailure=plymouth-quit.service
[Service]
ExecStartPre=/usr/bin/xinit /usr/share/gdm/generate-config
ExecStart=/usr/sbin/gdm3
KillMode=mixed
Restart=always
RestartSec=1s
IgnoreSIGPIPE=no
BusName=org.gnome.DisplayManager
StandardOutput=syslog
StandardError=inherit
EnvironmentFile=-/etc/default/locale
ExecReload=/usr/share/gdm/generate-config
ExecReload=/bin/kill -SIGHUP $MAINPID
--
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/1716857
Title:
gdm3, hybrid nvidia with modeset=1, no external monitors detected
Status in gnome-shell package in Ubuntu:
New
Bug description:
Context:
17.10 development packages, nvidia binary driver 375, modeset=1 for the
nvidia driver.
ubuntu desktop (gnome shell), fresh install
ThinkPad W520 in Nvidia Optimus bios mode.
Nvidia profile.
Result:
no external monitors are detected.
xrandr does not even list them as disconnected (normally it would list five
external disconnected monitors)
lsmod
shows that nvidia driver is loaded
and the modesetting is working at some level because there is no tearing on
the laptop panel
Note: modeset=1 is the only way to get flicker-free graphics on the laptop
panel. modeset=1 is not the default setting but it is highly desirable.
It works if lightdm is used which is why I have reported this against gdm3
My sessions in this configuration have mostly crashed after a few minutes
with a gdm3 fail whale message in syslog but nothing else looks interesting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716857/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731873] Re: Backport amdgpu-pro support
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1731873 Title: Backport amdgpu-pro support Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Committed Status in ubuntu-drivers-common source package in Zesty: Fix Committed Bug description: SRU Request: [Impact] Support for the amdgpu-pro driver has been available in Artful since May 2017. We need to backport the code to the other stable releases. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common" 2) Make sure the amdgpu-pro packages are installed (if not, install them, and restart your system). 3) Check that power saving mode is supported: amdgpu-pro-px --ispx If it returns true, then it is supported by the hardware. 4) Set power saving mode: sudo amdgpu-pro-px --mode powersaving 5) Restart your computer and check that the "Enabling power saving mode for amdgpu-pro" line is in your /var/log/gpu-manager.log. 6) Install the mesa-utils package: sudo apt install mesa-utils 7) Check the output of the following command (which should mention Intel): glxinfo | grep OpenGL [Regression Potential] Low, as the feature is disabled by default, unless users set power saving manually. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1731873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737853] Re: PCI/internal sound card not detected on Dell XPS 13 9343
Fixed by adding the following line to /etc/modprobe.d/alsa-base.conf options snd-hda-intel index=1,0 jackpoll_ms=500 -- 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/1737853 Title: PCI/internal sound card not detected on Dell XPS 13 9343 Status in alsa-driver package in Ubuntu: New Bug description: Internal sound card not recognized on fresh install of ubuntu 17.10 on Dell XPS 13 (9343) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dangar 1219 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 13 01:03:41 2017 InstallationDate: Installed on 2017-12-12 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1737853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts
Should be mostly fixed in current 0.92.x branch of Inkscape. Related commits: https://gitlab.com/inkscape/inkscape/commit/e5d477fa2df049ea731d2a0809ebd6fe03f660d6 https://gitlab.com/inkscape/inkscape/commit/8221730a84375f91b4f791bbad8b7b6d9547cdd8 Any remaining issues should be tracked in more targeted bugs. ** Changed in: inkscape Status: New => Fix Committed ** Changed in: inkscape Milestone: None => 0.92.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: Fix Committed Status in Intellij Idea: New Status in monodevelop: New Status in Mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in kdevelop package in Ubuntu: Confirmed Status in mc package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in kdevelop source package in Xenial: Confirmed Status in mc source package in Xenial: Confirmed Status in openjdk-7 source package in Xenial: Incomplete Status in unity source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: In Progress Status in gnome-shell package in Fedora: Won't Fix Status in openoffice package in Fedora: Won't Fix Bug description: Keyboard shortcuts are key combinations like Alt+F (usually opens the File menu) and Ctrl+O (usually opens the File→Open... dialog box). There is an issue with non-latin keyboard layouts that the keys under F or O (for Alt+F and Ctrl+O respectively) would correspond to some other character. What should happen then? There is some smart functionality (at least in the GTK+ library) that when we press a shortcut, it will try to make Alt+F or Ctrl+O work, even if the active keyboard layout is not English. For this smart functionality to work, it requires us to have as first keyboard layout the English (en) layout. Then, GTK+ will be able to check whether the shortcut makes sense for English, and if so, will run it. All that even if the active layout is Greek or Russian or something else. This report has over 300 comments and these comments include all sort of corner cases that indeed shortcuts do not work. In general, shortcuts work, but in specific cases there are issues that need to be fixed. What we need to do, is collect those corner cases and create new separate reports. Here are the corner cases: 1. In Dash (in Unity 7), shortcuts like Super+S/W work (for example, Greek, Russian), but they do not work for Super+A/F/M/C/V. Report: 2. Java GUI applications on Linux do not support shortcuts in non-latin languages. This is an issue with Java and should be reported there. Java GUI apps are not included in any of the Ubuntu ISOs. Report: 3. Shortcuts that use Ctrl on LibreOffice work for several languages (like Greek, Russian), but has been reported not to work on Hebrew. This should be a separate bug report specific to Hebrew and other languages affected in the same way. Report: To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737853] [NEW] PCI/internal sound card not detected on Dell XPS 13 9343
Public bug reported: Internal sound card not recognized on fresh install of ubuntu 17.10 on Dell XPS 13 (9343) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dangar 1219 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 13 01:03:41 2017 InstallationDate: Installed on 2017-12-12 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1737853 Title: PCI/internal sound card not detected on Dell XPS 13 9343 Status in alsa-driver package in Ubuntu: New Bug description: Internal sound card not recognized on fresh install of ubuntu 17.10 on Dell XPS 13 (9343) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dangar 1219 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 13 01:03:41 2017 InstallationDate: Installed on 2017-12-12 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1737853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417470] Re: PDF+Latex export creates multipage pdf, pages missing
All recent fixes related to PDF+LaTeX export backported in https://gitlab.com/inkscape/inkscape/compare/af5ac6bc522ff4b715d482d3eda11e0e0408ad15...cb54205aa21bcd227c62fce1a356f6f2c6039b64 This should fix all remaining issues with missing pages in the output and produce proper stacking order of text and graphics in all cases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1417470 Title: PDF+Latex export creates multipage pdf, pages missing Status in Inkscape: Fix Released Status in inkscape package in Ubuntu: Fix Released Status in inkscape package in Debian: Fix Released Bug description: In 0.91 the z-order information in svg is used to create multipage PDF+LaTeX documents as per bug 771957. However, for the SVGs I have been converting to PDF+LaTeX in this way, the TeX-file instructs to load more pages than the PDF has, for example the PDF has only three pages and the TeX file also includes page=4. This basically breaks the PDF+LaTeX export for me and I have to use EPS+LaTeX + epstopdf package. The bug occurs on OpenSuse 13.1 and Windows 8.1. Attached a zip file with two svg files and their broken PDF+LaTeX counterparts. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1417470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Partial from logfile. Dell 5378 13 i7 KabyLake fresh re-install of Artful Priority 3dbus: Failed to construct signal dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none (src/devices/nm-device.c:1452)): assertion '' failed It's a shame that this bug has been around so long without fixes. -- 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/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' Status in network-manager package in Ubuntu: Confirmed Bug description: The Wifi network can't connect after the wake up from suspend. Xubuntu 15.04 I'll post more useful details (journalctl log) as a comment to this bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 Uname: Linux 4.0.0-04rc5-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 2 18:18:56 2015 InstallationDate: Installed on 2015-03-27 (5 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737762] Re: i wont let me update and my terminal is going crazy
** Changed in: xorg (Ubuntu) Assignee: brandon cunningham (brandonkilecunningham) => (unassigned) -- 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/1737762 Title: i wont let me update and my terminal is going crazy Status in xorg package in Ubuntu: New Bug description: it wont let me update and terminal is crazy ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Dec 12 06:57:52 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 3450/3470] [103c:30dc] InstallationDate: Installed on 2017-03-14 (272 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PCD Ver. F.17 dmi.board.name: 30DC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 87.2A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCDVer.F.17:bd03/05/2010:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.17:rvnHewlett-Packard:rn30DC:rvrKBCVersion87.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 6930p dmi.product.version: F.17 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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: Tue Dec 12 02:50:18 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1737762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737850] [NEW] /usr/bin/remmina:11:remmina_rdp_cliprdr_send_format_list:remmina_rdp_event_process_clipboard:remmina_rdp_event_queue_ui:gdk_threads_dispatch:g_main_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding remmina. This problem was most recently seen with package version 1.1.2-4ubuntu1, the problem page at https://errors.ubuntu.com/problem/5e9a9b4ec390dff3f8c48676f1137eb6ef88203d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: artful wily xenial yakkety zesty -- 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/1737850 Title: /usr/bin/remmina:11:remmina_rdp_cliprdr_send_format_list:remmina_rdp_event_process_clipboard:remmina_rdp_event_queue_ui:gdk_threads_dispatch:g_main_dispatch Status in remmina package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding remmina. This problem was most recently seen with package version 1.1.2-4ubuntu1, the problem page at https://errors.ubuntu.com/problem/5e9a9b4ec390dff3f8c48676f1137eb6ef88203d 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/remmina/+bug/1737850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728378] Re: NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed
This bug affects my Dell 5378 13 i7 KabyLake. New re-install of Artful. NetworkManager (src/devices/nm-device.c:1452)): assertion '' failed -- 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/1728378 Title: NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed Status in network-manager package in Ubuntu: Confirmed Bug description: This error shows up in boot logs: "NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed". Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722000] Re: gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 00007f22c7bdf877 sp 00007ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+
*** This bug is a duplicate of bug 1722811 *** https://bugs.launchpad.net/bugs/1722811 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/1722000 Title: gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 7f22c7bdf877 sp 7ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+141000]) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Attached screenshots for "before applying" and after. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 21:57:36 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737843] [NEW] Consider demoting xchat-gnome to universe
Public bug reported: xchat-gnome came up today in a discussion of main components that aren't ready for openssl 1.1. https://lists.ubuntu.com/archives/ubuntu-devel/2017-December/040087.html See Steve's response https://lists.ubuntu.com/archives/ubuntu-devel/2017-December/040089.html "Ubuntu-only package (dropped in Debian, dropped subsequently in Ubuntu, then brought back). Did not ship in yakkety or zesty; when restored in artful it went straight to main because it was still seeded, but it's unclear this was ever reviewed by the Desktop Team or whether they want this package still in main. (The re-uploader is not a member of the Desktop Team.)" xchat-gnome is seeded in the supported-desktop-extra seed. Do we still need an IRC desktop client in main? (irssi is in main) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Affects: xchat-gnome (Ubuntu) Importance: Undecided Status: New ** Also affects: xchat-gnome (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1737843 Title: Consider demoting xchat-gnome to universe Status in ubuntu-meta package in Ubuntu: New Status in xchat-gnome package in Ubuntu: New Bug description: xchat-gnome came up today in a discussion of main components that aren't ready for openssl 1.1. https://lists.ubuntu.com/archives/ubuntu- devel/2017-December/040087.html See Steve's response https://lists.ubuntu.com/archives/ubuntu-devel/2017-December/040089.html "Ubuntu-only package (dropped in Debian, dropped subsequently in Ubuntu, then brought back). Did not ship in yakkety or zesty; when restored in artful it went straight to main because it was still seeded, but it's unclear this was ever reviewed by the Desktop Team or whether they want this package still in main. (The re-uploader is not a member of the Desktop Team.)" xchat-gnome is seeded in the supported-desktop-extra seed. Do we still need an IRC desktop client in main? (irssi is in main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1737843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737772] Re: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit statu
Reassigning to gnome-software, which should take care to not let the debconf frontend die while dpkg is still running. ** Package changed: shim-signed (Ubuntu) => gnome-software (Ubuntu) -- 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/1737772 Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in gnome-software package in Ubuntu: New Bug description: VM Box installation could not be finished ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Tue Dec 12 15:32:38 2017 EFITables: Dez 12 10:55:40 udo-All-Series kernel: efi: EFI v2.40 by American Megatrends Dez 12 10:55:40 udo-All-Series kernel: efi: ESRT=0x9779e118 ACPI=0x964fc000 ACPI 2.0=0x964fc000 SMBIOS=0xf05b0 MPS=0xfd610 Dez 12 10:55:40 udo-All-Series kernel: esrt: Reserving ESRT space from 0x9779e118 to 0x9779e150. Dez 12 10:55:40 udo-All-Series kernel: Secure boot enabled ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-17 (24 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1737772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737772] [NEW] package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit sta
You have been subscribed to a public bug: VM Box installation could not be finished ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Tue Dec 12 15:32:38 2017 EFITables: Dez 12 10:55:40 udo-All-Series kernel: efi: EFI v2.40 by American Megatrends Dez 12 10:55:40 udo-All-Series kernel: efi: ESRT=0x9779e118 ACPI=0x964fc000 ACPI 2.0=0x964fc000 SMBIOS=0xf05b0 MPS=0xfd610 Dez 12 10:55:40 udo-All-Series kernel: esrt: Reserving ESRT space from 0x9779e118 to 0x9779e150. Dez 12 10:55:40 udo-All-Series kernel: Secure boot enabled ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-17 (24 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/1737772 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 498137] Re: Weather data for Coventry (UK) no longer available
** Changed in: libgweather Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/498137 Title: Weather data for Coventry (UK) no longer available Status in libgweather: Fix Released Status in libgweather package in Ubuntu: Invalid Bug description: Since Coventry airport closed at the beginning of December 09 (http://news.bbc.co.uk/1/hi/england/coventry_warwickshire/8401690.stm) no weather information has been available for Coventry (UK). The data currently being displayed originates from the 8th of December 09. To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/498137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737836] Re: Standard clock applet is oversized in Artful
Second screenshot. ** Attachment added: "Screenshot from 2017-12-12 15-23-53.png" https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+attachment/5021860/+files/Screenshot%20from%202017-12-12%2015-23-53.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1737836 Title: Standard clock applet is oversized in Artful Status in gnome-panel package in Ubuntu: New Bug description: In Artful if the standard clock applet is used there is a dead-space to the left of it. In my first screenshot you can see the dead-space between the indicator-applet and the clock applet. In the second screenshot you can see I've moved the clock applet to the left and the same dead-space exists between it and the inhibit-applet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 12 15:19:25 2017 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 'workspace-switcher', 'clock', 'indicator-applet', 'inhibit-applet', 'menu-button', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']" InstallationDate: Installed on 2017-12-11 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737836] [NEW] Standard clock applet is oversized in Artful
Public bug reported: In Artful if the standard clock applet is used there is a dead-space to the left of it. In my first screenshot you can see the dead-space between the indicator-applet and the clock applet. In the second screenshot you can see I've moved the clock applet to the left and the same dead-space exists between it and the inhibit-applet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 12 15:19:25 2017 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 'workspace-switcher', 'clock', 'indicator-applet', 'inhibit-applet', 'menu-button', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']" InstallationDate: Installed on 2017-12-11 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "Screenshot from 2017-12-12 15-23-24.png" https://bugs.launchpad.net/bugs/1737836/+attachment/5021856/+files/Screenshot%20from%202017-12-12%2015-23-24.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1737836 Title: Standard clock applet is oversized in Artful Status in gnome-panel package in Ubuntu: New Bug description: In Artful if the standard clock applet is used there is a dead-space to the left of it. In my first screenshot you can see the dead-space between the indicator-applet and the clock applet. In the second screenshot you can see I've moved the clock applet to the left and the same dead-space exists between it and the inhibit-applet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 12 15:19:25 2017 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 'workspace-switcher', 'clock', 'indicator-applet', 'inhibit-applet', 'menu-button', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']" InstallationDate: Installed on 2017-12-11 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737835] [NEW] libunity fails to build, test failure
Public bug reported: libunity fails to build from source in current bionic. Full build log at https://launchpad.net/~jbicha/+archive/ubuntu/dev/+build/13847861 Build log excerpt = TEST: test-vala... (pid=18081) /Unit/ResultsSynchronizer: OK /Unit/IO/AsyncDesktopFile: OK /Unit/IO/AsyncOpenFromDataDirs: OK /Unit/Utils/AsyncOnce: OK /Unit/Utils/AsyncMutex: OK /Unit/AppInfoManager/Allocation: OK /Unit/AppInfoManager/ClearEmpty: OK /Unit/AppInfoManager/SyncLookupMissing: OK /Unit/AppInfoManager/AsyncLookupMissing: OK /Unit/AppInfoManager/SyncLookupOk: OK /Unit/AppInfoManager/AsyncLookupOk: OK /Unit/Launcher/EmptyEntry: (test-vala:18081): libunity-CRITICAL **: unity-launcher.vala:154: Unable to connect to session bus: Could not connect: Connection refused FAIL ** Affects: libunity (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ftbfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1737835 Title: libunity fails to build, test failure Status in libunity package in Ubuntu: New Bug description: libunity fails to build from source in current bionic. Full build log at https://launchpad.net/~jbicha/+archive/ubuntu/dev/+build/13847861 Build log excerpt = TEST: test-vala... (pid=18081) /Unit/ResultsSynchronizer: OK /Unit/IO/AsyncDesktopFile: OK /Unit/IO/AsyncOpenFromDataDirs: OK /Unit/Utils/AsyncOnce: OK /Unit/Utils/AsyncMutex: OK /Unit/AppInfoManager/Allocation: OK /Unit/AppInfoManager/ClearEmpty: OK /Unit/AppInfoManager/SyncLookupMissing: OK /Unit/AppInfoManager/AsyncLookupMissing: OK /Unit/AppInfoManager/SyncLookupOk: OK /Unit/AppInfoManager/AsyncLookupOk: OK /Unit/Launcher/EmptyEntry: (test-vala:18081): libunity-CRITICAL **: unity-launcher.vala:154: Unable to connect to session bus: Could not connect: Connection refused FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1737835/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
I have an Epson Stylus TX235W which I used to print and scan wirelessly. Even after creating the /usr/lib/x86_64-linux-gnu soft links, scanimage -L still doesn't find my printer through the epkowa backend. However, it does find it through the epson2 backend, so that I can use xscan or Simple Scan. Indeed libsane1 has broken the epkowa sane backend. -- 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/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts
** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Invalid ** Changed in: mate-terminal (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1667227 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts Status in gnome-terminal package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Invalid Bug description: 1) $ lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 2) $ apt-cache policy mate-terminal mate-terminal: Installed: 1.17.0-0ubuntu1 Candidate: 1.17.0-0ubuntu1 3) Open mate-terminal Select "Edit" -> "Keyboard Shortcuts" Select "Help"->"Contents", click on default shortcut key "F1" to change Try to set it to various key sequences. Sometimes bug is triggered by pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting Ctrl-Shift-W / Crtl-Shift-Alt-W Expected: changed keyboard shortcut for "Help"->"Contents" 4) Abort and closed mate-terminal ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-terminal 1.17.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Feb 23 09:33:19 2017 ExecutablePath: /usr/bin/mate-terminal ExecutableTimestamp: 1484233434 InstallationDate: Installed on 2017-02-22 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: mate-terminal ProcCwd: /home/user SegvAnalysis: Segfault happened at: 0x7f883e41c321 : testb $0x4,0x16(%rax) PC (0x7f883e41c321) ok source "$0x4" ok destination "0x16(%rax)" (0x7001e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1667227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737805] Re: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured
*** This bug is a duplicate of bug 545790 *** https://bugs.launchpad.net/bugs/545790 ** Package changed: glib2.0 (Ubuntu) => dpkg (Ubuntu) ** This bug has been marked a duplicate of bug 545790 package PACKAGE failed to install/upgrade: error writing to '': Success -- 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/1737805 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured Status in dpkg package in Ubuntu: New Bug description: the instalation failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.14 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Tue Dec 12 20:28:43 2017 DuplicateSignature: package:libglib2.0-0:amd64:2.48.2-0ubuntu1 Unpacking qtdeclarative5-dialogs-plugin:amd64 (5.5.1-1ubuntu1) ... dpkg: error processing package uuid-runtime (--configure): package uuid-runtime is already installed and configured ErrorMessage: package libglib2.0-0:amd64 is already installed and configured InstallationDate: Installed on 2016-07-07 (523 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1737805/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704765] Re: can't drag file from desktop to folder window on Artful
JLuc, I don't see that option on Ubuntu 17.10. The only Experimental option in the Nautilus preferences is "Use the new views", which I have unchecked (as is the default), and this bug still occurs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1704765 Title: can't drag file from desktop to folder window on Artful Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: I'm running Ubuntu 17.10 (Artful). If I create a text file on my desktop and then attempt to drag it into a Nautilus folder window, it fails: when I release the mouse cursor over the folder window nothing happens and the file is not moved. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1704765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1461082] Re: patch - fix crash with long one-line XML documents
Debian maintainers showed no interest in this patch for more than 2 years, so let it be gone from here. ** No longer affects: gtksourceview2 (Debian) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview2 in Ubuntu. https://bugs.launchpad.net/bugs/1461082 Title: patch - fix crash with long one-line XML documents Status in gtksourceview2 package in Ubuntu: Fix Released Status in gtksourceview2 source package in Precise: Fix Released Status in gtksourceview2 source package in Trusty: Fix Released Status in gtksourceview2 source package in Utopic: Fix Released Status in gtksourceview2 source package in Vivid: Fix Released Status in gtksourceview2 source package in Wily: Fix Released Bug description: [Impact] When editing a long one-line document with some markup (e.g. XML) with Pluma (or any other editor using gtksourceview2), you cannot delete a selected portion of text because the editor will crash. This has been reported upstream and fixed in [1], but the commit never made it to GTK+2 version of gtksourceview. So, I propose fixing it in current stable Ubuntu releases with the patch which fixes the crash for good. The debdiffs for every stable release are in the attachments below. [Test Case] Steps to reproduce: 1. Open a long one-line XML document (e.g. [2]) with Pluma. Any other editor using gtksourceview2 will also fit I think. 2. Select a portion of text. 3. Press Backspace (or Delete) key. 4. Pluma crashes. The full backtrace is at [3]. If you're running Pluma from the command-line, you'll notice a warning: GtkSourceView-CRITICAL **: Highlighting a single line took too much time, syntax highlighting will be disabled That's the key. The library tries to invalidate the region when text is deleted and the engine is disabled (i.e. syntax highlighting is off). [Regression Potential] After several months of testing the patch in Debian Jessie, I haven't noticed any regressions. [1] https://git.gnome.org/browse/gtksourceview/commit/?id=abef41da8c541c814bf631f69c92e0c431c610ad [2] http://pastebin.com/nNdYzFXE [3] http://pastebin.com/YgDT0iKh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1461082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340067] Re: Drop 20_add_alt_screen_toggle_ui.patch - it does nothing with vte3 >= 0.34.9
Somebody please mark it as wontfix for Trusty if it's not going to be patched there. I'm fine with it, I just don't have the rights to mark it so. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1340067 Title: Drop 20_add_alt_screen_toggle_ui.patch - it does nothing with vte3 >= 0.34.9 Status in gnome-terminal package in Ubuntu: Fix Released Status in gnome-terminal source package in Trusty: New Status in gnome-terminal source package in Utopic: Won't Fix Bug description: On 2013-09-30, the alternate scroll mode has been implemented in vte3 upstream [1]. In the same commit, vte_terminal_set_alternate_screen_scroll function has been added which does nothing and is there only for the compatibility with the previously patched Ubuntu's vte3 (the patch has been dropped in vte3 0.34.9-1ubuntu1). Since this function now does nothing, Ubuntu's 20_add_alt_screen_toggle_ui.patch for gnome-terminal does nothing too. It doesn't matter whether you turn the alt.scroll on or off in gnome- terminal's preferences window - the mouse scroll in console apps like man is ALWAYS turned on. Seems like it's always turned on in vte3 >= 0.34.9 (again, see [1] for more info). So I propose to drop this 20_add_alt_screen_toggle_ui.patch since it's useless now. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1340067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather
Uploaded debdiffs to the SRU queue where they will need to be manually approved by the SRU Team before being built as proposed updates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Xenial: In Progress Status in libgweather source package in Zesty: In Progress Status in libgweather source package in Artful: In Progress Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1294699] Re: Xubuntu desktop crashes in call to cairo after setting fixed-width bitmap (pcf) GTK font
Ok. But sorry, I won't be able to provide the proper fix for Xenial. The only fix I know is the one that caused the mentioned regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-murrine in Ubuntu. https://bugs.launchpad.net/bugs/1294699 Title: Xubuntu desktop crashes in call to cairo after setting fixed-width bitmap (pcf) GTK font Status in gtk2-engines-murrine package in Ubuntu: Fix Released Status in gtk2-engines-murrine source package in Xenial: Triaged Status in gtk2-engines-murrine package in Debian: Fix Released Bug description: [Impact] Due to a problem in the Murrine engine, using bitmap fonts and Murrine-based themes at the same time might lead to crash of various GTK+2 apps. This issue was around for about 3-4 years, or maybe even more. It affects a lot of Xfce and MATE users who choose to use bitmap fonts, and it's present in two current LTS releases, so it would be really nice to apply the fix there. The patch which is posted below fixes the crashes for good and allows people to use bitmap fonts and Murrine-based themes together again. [Test Case] Steps to reproduce: 1. Have Xubuntu (or Xfce in any other Ubuntu edition) installed. It can be any release from 14.04 to 16.10. 2. Install gtk2-engines-murrine, murrine-themes and shimmer-themes packages, if they're not installed. 3. Install some package with bitmap fonts, for example, xfonts-terminus. 4. Run xfce4-appearance-settings and select some Murrine-based theme, for example, Greybird or Murrine-Light. 5. Switch to the Fonts tab and select some bitmap font, for example, Terminus. 6. Exit xfce4-appearance-settings. Now some GTK+2 apps will crash right on start with the following error message: ../../../../src/cairo-scaled-font.c:459: _cairo_scaled_glyph_page_destroy: Assertion `!scaled_font->cache_frozen' failed. It's reproducible with mousepad, gimp, geany. With some Murrine-based themes, like Greybird, it's also reproducible with xfce4-panel and Xfce configuration apps: xfce4-appearance-settings, xfce4-mouse-settings, xfce4-session-settings, etc. It also affects some MATE apps, like mate-panel or mate-control- center. [Regression Potential] After several months of testing the fix in Debian Jessie and a few Ubuntu releases, I hadn't found any regressions. Since the patch is very small and it fixes all the crashes for good, I don't think there's much space for the regressions. [Other Info] Appearance settings being affected is a nasty thing. However, you can reset the font to default via the console tool: $ xfconf-query -c xsettings -p /Gtk/FontName -r The patch was made following the proposed solution at: https://bugs.freedesktop.org/show_bug.cgi?id=78787#c9 Similar report seen in archlinux/xfce4: https://bbs.archlinux.org/viewtopic.php?id=169433 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk2.0-0 2.24.20-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Wed Mar 19 10:41:54 2014 InstallationDate: Installed on 2013-11-01 (138 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-murrine/+bug/1294699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737805] Re: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured
** Tags removed: need-duplicate-check -- 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/1737805 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured Status in glib2.0 package in Ubuntu: New Bug description: the instalation failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.14 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Tue Dec 12 20:28:43 2017 DuplicateSignature: package:libglib2.0-0:amd64:2.48.2-0ubuntu1 Unpacking qtdeclarative5-dialogs-plugin:amd64 (5.5.1-1ubuntu1) ... dpkg: error processing package uuid-runtime (--configure): package uuid-runtime is already installed and configured ErrorMessage: package libglib2.0-0:amd64 is already installed and configured InstallationDate: Installed on 2016-07-07 (523 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1737805/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737805] [NEW] package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured
Public bug reported: the instalation failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.14 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Tue Dec 12 20:28:43 2017 DuplicateSignature: package:libglib2.0-0:amd64:2.48.2-0ubuntu1 Unpacking qtdeclarative5-dialogs-plugin:amd64 (5.5.1-1ubuntu1) ... dpkg: error processing package uuid-runtime (--configure): package uuid-runtime is already installed and configured ErrorMessage: package libglib2.0-0:amd64 is already installed and configured InstallationDate: Installed on 2016-07-07 (523 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package xenial -- 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/1737805 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured Status in glib2.0 package in Ubuntu: New Bug description: the instalation failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.14 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Tue Dec 12 20:28:43 2017 DuplicateSignature: package:libglib2.0-0:amd64:2.48.2-0ubuntu1 Unpacking qtdeclarative5-dialogs-plugin:amd64 (5.5.1-1ubuntu1) ... dpkg: error processing package uuid-runtime (--configure): package uuid-runtime is already installed and configured ErrorMessage: package libglib2.0-0:amd64 is already installed and configured InstallationDate: Installed on 2016-07-07 (523 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1737805/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 365094] Re: there isn't in the list a place (Falconara Ancona - Italia) in weather applet
** Changed in: libgweather Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/365094 Title: there isn't in the list a place (Falconara Ancona - Italia) in weather applet Status in libgweather: Fix Released Status in libgweather package in Ubuntu: Incomplete Bug description: sorry for my bad english, In ubuntu 8.04 I've my place but in ubuntu 8.10 it missing. City name Ancona/Falconara Italy Latitude 43,616665 Longitude 13,37 Airport Ancona/Falconara Airport ICAO code LIPY Codice WMO16191 tahnks To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/365094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
Marco, thanks for the context and the steps you and the team are taking to resolve this issue more broadly. Linking js and C is bound to have these problems. And it seems that the extensions are also maturing and dealing with the bug reports. -- 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/1714989 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() Status in GNOME Shell: Fix Released Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Incomplete Bug description: Saw some reports with the same title but they're all for previous versions. error report: https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 16:52:13 2017 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-04-21 (135 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd97c8e7e5d : movzbl 0x16(%rax),%edx PC (0x7fd97c8e7e5d) ok source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so 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: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 192629] Re: "Cannot move file to trash, do you want to delete immediately?" on NTFS / VFAT partitions
ubuntu 17.10 same issue -- 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/192629 Title: "Cannot move file to trash, do you want to delete immediately?" on NTFS / VFAT partitions Status in GLib: New Status in glib2.0 package in Ubuntu: Triaged Bug description: Trying to delete files with nautilus from a vfat partition "fails". Well, the file can be deleted OK, but it seems gvfs can't send the file to the trashcan, so only permanent delete is available. Furthermore, the name of the file appears in little boxes, similar to viewing a chinese site using Latin-1 encoding (will attach screenshot). Distro: Hardy up to date (17-february 2008) Steps to reproduce: Copy a file to an vfat partition. Select it and delete using nautilus. A message error will appear: "Can't move file to trashcan. Do you want to delete it inmediately?" "File <>cannot be moved to trashcan" Versions: Nautilus 1:2.21.91-0ubuntu2 gvfs 0.1.7-0ubuntu4 /etc/fstab for the vfat partition: UUID=9445-A956 /fat32 vfatdefaults,utf8,umask=007,gid=46 0 1 To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/192629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737784] Re: systematically fails to connect to gmail account with the correct password
https://support.google.com/accounts/answer/6010255 https://blogs.msmvps.com/jcoehoorn/blog/2017/05/04/what-are-less-secure- apps-in-google/ I think the "less secure" issue is fixed in Ubuntu 17.10. In April, the next LTS version of Ubuntu, Ubuntu 18.04 LTS, will be released with all fixes from 17.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1737784 Title: systematically fails to connect to gmail account with the correct password Status in evolution package in Ubuntu: New Bug description: I installed Evolution just for the sake of trying and help diagnosing an unrelated bug. Not that I intend to use it. The first time I ran it, it asked me to insert an email address for creating an account, so I did, I entered a gmail address and the correct password, but the mail authentication request keeps failing. I have double-checked that the password is correct by logging in to that very same gmail account in a new incognito browser window. I wanted to report this upstream but the version of Evolution is obsolete upstream. So, can't even begin to use it. Fortunately I wasn't going to, so I don't care, but it's pathetic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 12 16:59:49 2017 InstallationDate: Installed on 2013-10-11 (1522 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1737784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1640180] Re: gnome-todo doesn't load CalDav task list from EDS
** Changed in: evolution-data-server (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1640180 Title: gnome-todo doesn't load CalDav task list from EDS Status in GNOME To Do: Confirmed Status in Ubuntu GNOME: New Status in evolution-data-server package in Ubuntu: Confirmed Status in gnome-todo package in Ubuntu: Triaged Bug description: Since the upgrade to Yakkety Gnome-TODO doesn't show my remote CalDav task list that were set through evolution. The list are still available in working in Evolution. I tried to set them up again but they didn't appear. I tried upgrading to version available in various gnome3-ppa (still 3.20.* though) and it didn't help. The bug seems to have been handled in Fedora : https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1363848 and https://bodhi.fedoraproject.org/updates/FEDORA-2016-db729be3e1 (I found those while searching the web for a solution). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-todo/+bug/1640180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
My Current system is ubuntu 17.10. If I delete file under home it moves to trash. But if I delete file in other location. It dont go to trash -- 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/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: Fix Released Status in glib2.0 source package in Yakkety: Fix Released Bug description: [ Description ] Can't trash files if the directory they are in is a symlink to another device [ QA ] Steps: 1. Install system and partition disk into root and data partitions 2. create ~/Data folder, and mount data partition on it 3. create symlinks for ~/whatever/ to ~/Data/something/ 4. delete files directly inside ~/whatever/ What happen: Then Nautilus says: "File can't be put in the trash. Do you want to delete it immediately?". What should happen: The files moved into Trash. [ Regression potential ] The proposed fix uses g_stat instead of g_stat to follow symlinks, so we know where to place the trash (you can't rename() across filesystems). If that is wrong, then it could regress trashing other kinds of files. [ Original ] I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721833] Re: Can't type numbers in the evolution search box
** Changed in: evolution (Ubuntu Artful) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1721833 Title: Can't type numbers in the evolution search box Status in Evolution: Fix Released Status in evolution package in Ubuntu: Fix Released Status in evolution source package in Artful: In Progress Bug description: Trying to type numeric characters into the evolution search box is not working when using the numeric keys above the letters on the keyboard. Shift+numeric key for a special symbol works, and then numpad keys work, but the "regular" number keys don't appear to do anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evolution 3.26.1-1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 6 10:35:25 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (777 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1721833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728655] Re: Update evolution to 3.26.3
** Summary changed: - Update evolution to 3.26.2 + Update evolution to 3.26.3 ** Changed in: evolution (Ubuntu Artful) Status: Triaged => In Progress ** Description changed: Impact == - evolution has released a new stable bugfix release. (These will happen about once every month or two until 3.28 is released.) + evolution has released a new stable bugfix release. (These will happen about once a month until 3.28 is released.) https://git.gnome.org/browse/evolution/tree/NEWS/?h=gnome-3-26 https://git.gnome.org/browse/evolution/log/?h=gnome-3-26 The update also fixes LP: #1721833 Test Case = After installing this update, please restart your computer. Verify that evolution still works as well as it did before. Optionally, you can go through some of the fixed bugs to verify the bug and the fix. Regression Potential GNOME 3.26 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME Ubuntu GNOME stopped including Evolution by default in 17.04. Upgraders may still have Evolution installed and it's a popular app. (It was demoted to universe before 16.04 LTS.) Other Info == - This update depends on evolution-data-server 3.26.2 (LP: #1728653) + This update depends on evolution-data-server 3.26.3 (LP: #1728653) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1728655 Title: Update evolution to 3.26.3 Status in evolution package in Ubuntu: Fix Released Status in evolution source package in Artful: In Progress Bug description: Impact == evolution has released a new stable bugfix release. (These will happen about once a month until 3.28 is released.) https://git.gnome.org/browse/evolution/tree/NEWS/?h=gnome-3-26 https://git.gnome.org/browse/evolution/log/?h=gnome-3-26 The update also fixes LP: #1721833 Test Case = After installing this update, please restart your computer. Verify that evolution still works as well as it did before. Optionally, you can go through some of the fixed bugs to verify the bug and the fix. Regression Potential GNOME 3.26 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME Ubuntu GNOME stopped including Evolution by default in 17.04. Upgraders may still have Evolution installed and it's a popular app. (It was demoted to universe before 16.04 LTS.) Other Info == This update depends on evolution-data-server 3.26.3 (LP: #1728653) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1728655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728653] Re: Update evolution-data-server to 3.26.3
** Summary changed: - Update evolution-data-server to 3.26.2 + Update evolution-data-server to 3.26.3 ** Description changed: Impact == evolution-data-server (e-d-s) has released a new stable bugfix release. - (These will happen about once every month or two until 3.28 is released.) + (These will happen about once every month until 3.28 is released.) - Updating e-d-s is required to update evolution to 3.26.2 (LP: #1728655) + Updating e-d-s is required to update evolution to 3.26.3 (LP: #1728655) https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-26 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-26 Test Case = After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. Regression Potential GNOME 3.26 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME 3.22.6 introduced a regression in pop3 support that was fixed within a week by 3.22.7. ** Changed in: evolution-data-server (Ubuntu Artful) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1728653 Title: Update evolution-data-server to 3.26.3 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Artful: In Progress Bug description: Impact == evolution-data-server (e-d-s) has released a new stable bugfix release. (These will happen about once every month until 3.28 is released.) Updating e-d-s is required to update evolution to 3.26.3 (LP: #1728655) https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-26 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-26 Test Case = After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. Regression Potential GNOME 3.26 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME 3.22.6 introduced a regression in pop3 support that was fixed within a week by 3.22.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1728653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1449112] Re: can't move files to trash without any owner/permission issues
*** This bug is a duplicate of bug 1638245 *** https://bugs.launchpad.net/bugs/1638245 Ubuntu 17.10 same issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1449112 Title: can't move files to trash without any owner/permission issues Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: This is something that wouldn't happen before upgrading from Ubuntu 14.10 / Nautilus 3.10 to Ubuntu 15.04 / Nautilus 3.14: I have a proper HOME partition and most User folders there (Documents, Downloads, Music, Pictures, Videos) are merely SYMLINKS to folders with the same names in a DATA partition which is mounted automatically at startup with proper options in fstab. Now -- unlike before -- when I attempt to delete an item in one of these folders after I open it via the SYMLINK I get the message "... can't be put in the trash. Do you want to delete it immediately?" although it is immediately moved to the Trash after I open the folder via the Data partition in the sidebar. (Naturally there are no such problems with items in other (real) items in my Home folder. Nautilus now seems confused about / not knowing where to move the item in question; to the Trash folder in the Home partition (symlink location) or the Data partition (real item location). To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1449112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1496542] Re: Running processes left after disabling screen reader
Hello all, What's described here is not a bug but the old behavior of speech- dispatcher. Orca is a screen reader, the speech output uses speech-dispatcher. speech-dispatcher is a daemon that run in background. In the new release like 16.04 or newer speech-dispatcher stops when there is no client connected to it. Best regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1496542 Title: Running processes left after disabling screen reader Status in speech-dispatcher package in Ubuntu: Triaged Bug description: After I disabled my screen reader, I noticed that when running "ps xa | grep -P 'speech-dispatcher.*\.conf'" I get: 17906 tty2 Sl+0:09 /usr/lib/speech-dispatcher-modules/sd_espeak /etc/speech-dispatcher/modules/espeak.conf 17911 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_cicero /etc/speech-dispatcher/modules/cicero.conf 17915 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/generic.conf 17918 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf 24407 pts/0S+ 0:00 grep --color=auto -P speech-dispatcher.*\.conf So it seems as though it left some running processes behind after I disabled it. I have also attached a screenshot of my Sound settings which show that they are still running (Sound_Application_List2.png). --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid Package Information: speech-dispatcher: Installed: 0.8.1-0ubuntu1 Candidate: 0.8.1-0ubuntu1 Version table: *** 0.8.1-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: speech-dispatcher 0.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 16 20:27:00 2015 InstallationDate: Installed on 2015-07-29 (49 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: speech-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1496542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734132] Re: LibreOffice doesn't seem to have a right click context-menu
Let's try a different approach for a clean downgrade: sudo apt remove "libreoffice*" sudo apt autoremove sudo apt install libreoffice=1:5.4.1-0ubuntu1 Then try and reproduce the issue initially reported here, and let me know what you're seeing. Thanks! -- 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/1734132 Title: LibreOffice doesn't seem to have a right click context-menu Status in libreoffice package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1) Run libreoffice -env:UserInstallation=file:///tmp/tmp_profile 2) Create a new writer document. 3) Type some silly stuff 4) Right click on a word I'd expect a context menu to be shown, but there is none. The mouse cursor changes though as if the context menu was shown. Pressing Escape make the cursor return to the normal caret. The attached screenshot is not really telling much. You can see how there is no context menu although I've just right clicked. The mouse cursor changed. The about dialog shows Version: 5.4.2.2 Build ID: 1:5.4.2-0ubuntu0.17.10.1 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group This bug does not show when using LibreOffice's x11 backend, i.e. when run with env SAL_USE_VCLPLUGIN=gen. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-common 1:5.4.2-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 23 15:05:24 2017 InstallationDate: Installed on 2017-10-13 (40 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) PackageArchitecture: all 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/1734132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737784] Re: systematically fails to connect to gmail account with the correct password
I see, it's Google blocking access from Evolution because it is known to have security issues. So, not only Ubuntu is distributing an obsolete version of the application, but even une that is known to be a security hazard. Cool! ** Attachment added: "Untitled.png" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1737784/+attachment/5021761/+files/Untitled.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1737784 Title: systematically fails to connect to gmail account with the correct password Status in evolution package in Ubuntu: New Bug description: I installed Evolution just for the sake of trying and help diagnosing an unrelated bug. Not that I intend to use it. The first time I ran it, it asked me to insert an email address for creating an account, so I did, I entered a gmail address and the correct password, but the mail authentication request keeps failing. I have double-checked that the password is correct by logging in to that very same gmail account in a new incognito browser window. I wanted to report this upstream but the version of Evolution is obsolete upstream. So, can't even begin to use it. Fortunately I wasn't going to, so I don't care, but it's pathetic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 12 16:59:49 2017 InstallationDate: Installed on 2013-10-11 (1522 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1737784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737784] Re: systematically fails to connect to gmail account with the correct password
(unless Google is wrong, of course) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1737784 Title: systematically fails to connect to gmail account with the correct password Status in evolution package in Ubuntu: New Bug description: I installed Evolution just for the sake of trying and help diagnosing an unrelated bug. Not that I intend to use it. The first time I ran it, it asked me to insert an email address for creating an account, so I did, I entered a gmail address and the correct password, but the mail authentication request keeps failing. I have double-checked that the password is correct by logging in to that very same gmail account in a new incognito browser window. I wanted to report this upstream but the version of Evolution is obsolete upstream. So, can't even begin to use it. Fortunately I wasn't going to, so I don't care, but it's pathetic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 12 16:59:49 2017 InstallationDate: Installed on 2013-10-11 (1522 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1737784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737784] [NEW] systematically fails to connect to gmail account with the correct password
Public bug reported: I installed Evolution just for the sake of trying and help diagnosing an unrelated bug. Not that I intend to use it. The first time I ran it, it asked me to insert an email address for creating an account, so I did, I entered a gmail address and the correct password, but the mail authentication request keeps failing. I have double-checked that the password is correct by logging in to that very same gmail account in a new incognito browser window. I wanted to report this upstream but the version of Evolution is obsolete upstream. So, can't even begin to use it. Fortunately I wasn't going to, so I don't care, but it's pathetic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 12 16:59:49 2017 InstallationDate: Installed on 2013-10-11 (1522 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1737784 Title: systematically fails to connect to gmail account with the correct password Status in evolution package in Ubuntu: New Bug description: I installed Evolution just for the sake of trying and help diagnosing an unrelated bug. Not that I intend to use it. The first time I ran it, it asked me to insert an email address for creating an account, so I did, I entered a gmail address and the correct password, but the mail authentication request keeps failing. I have double-checked that the password is correct by logging in to that very same gmail account in a new incognito browser window. I wanted to report this upstream but the version of Evolution is obsolete upstream. So, can't even begin to use it. Fortunately I wasn't going to, so I don't care, but it's pathetic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 12 16:59:49 2017 InstallationDate: Installed on 2013-10-11 (1522 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1737784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1562875] Re: Totem can't play H264 on fresh 16.04 beta install
In ubuntu 17.10, this issue disappeared after I installed gstreamer1.0-libav. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1562875 Title: Totem can't play H264 on fresh 16.04 beta install Status in gstreamer1.0 package in Ubuntu: Fix Released Bug description: Totem can't play neither find the correct codec to play H264 *.mp4 video in last 16.04 beta. Terminal says : ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, stream-format=(string)avc, alignment=(string)au, level=(string)4, profile=(string)main, max- input-size=(int)51696, parsed=(boolean)true (H.264 (Main Profile) decoder) Totem tries to find the correct codec but fails, see attachment ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.0-1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 28 15:51:47 2016 InstallationDate: Installed on 2016-03-26 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: amixer: Mixer attach default error: No such file or directory ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1562875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737702] Re: gnome-shell-calendar-server crashed with SIGSEGV in icaltimezone_get_utc_offset()
** Information type changed from Private 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/1737702 Title: gnome-shell-calendar-server crashed with SIGSEGV in icaltimezone_get_utc_offset() Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell-calendar-server crashed with SIGSEGV in icaltimezone_get_utc_offset() ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 11:57:30 2017 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'google-chrome.desktop', 'libreoffice-startcenter.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop', 'org.gnome.Screenshot.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-11-15 (26 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171114) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7feb6b6963a8 : mov0x30(%rdi),%rbp PC (0x7feb6b6963a8) ok source "0x30(%rdi)" (0x0031) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: icaltimezone_get_utc_offset () from /usr/lib/x86_64-linux-gnu/libical.so.3 icaltimezone_convert_time () from /usr/lib/x86_64-linux-gnu/libical.so.3 icaltime_convert_to_zone () from /usr/lib/x86_64-linux-gnu/libical.so.3 icaltime_compare () from /usr/lib/x86_64-linux-gnu/libical.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19 Title: gnome-shell-calendar-server crashed with SIGSEGV in icaltimezone_get_utc_offset() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1737702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737535] Re: Falha ao executar processo filho "duplicity" (Arquivo ou diretório não encontrado)
olá, Esta mensagem aparace quando eu inicio o aplicativo na tentativa de fazer um backup do sistema. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1737535 Title: Falha ao executar processo filho "duplicity" (Arquivo ou diretório não encontrado) Status in deja-dup package in Ubuntu: New Bug description: Não Consigo executar o programa! Aparece a seguinte mensagem: Falha ao executar processo filho "duplicity" (Arquivo ou diretório não encontrado) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1737535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1537057] Re: rhytembox-client --print-playing-format %te partially broken
thanks, closing the bug then ** Changed in: rhythmbox (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1537057 Title: rhytembox-client --print-playing-format %te partially broken Status in rhythmbox package in Ubuntu: Fix Released Bug description: Hello Launchpad, I was setting up keyboard shortcuts for controlling rhytembox entirely via keyboard in the background. While most of the commands can be bound quite easily using the rhytembox-client, i found a weird behavior when using the current time to skip ahead (using seek) In order to get the current position in the track, in use the command rhytembox-client --print-playing-format %te As this gives me the format in hour:minute:seconds. This works up to a track length of 1:11:34, then there seems to be an error, and counting starts from 0 again; here is an example of the output while listening to a long track: while true; do rhythmbox-client --print-playing-format %te; sleep 1; done 1:11:30 1:11:31 1:11:32 1:11:33 1:11:34 Unbekannt 0:01 0:02 0:03 0:04 0:05 0:06 0:07 ^C I've tested this with several tracks - they all split behave the same. So my guess is that this is some kind of overflow in the timing ? Of course, not many tracks are that long, but i'd still like to point this out. Makes the while skipping forward via the client very hard, as the time playing is not really reliable. Not sure if this should be mentioned here or go into the wishlist, but it would be great if the output format could also print seconds. It would be very useful with seek to easily fast forward/backward. Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1537057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
@Łukasz, Do you think it's easier for us to SRU: #1693756, #17 ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: In Progress Status in libmbim source package in Xenial: New Status in libqmi source package in Xenial: New Status in modemmanager source package in Xenial: New Bug description: [Impact] * the new modemmanager packages bring in DW5816 supporting. * These modemmanager packages is needed to support new devices. [Test Case] * install modemmanager and it's dependencies from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054 libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1 libmbim-proxy 1.14.0-1ubuntu0.16.04.1 libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1 libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1 libqmi-proxy 1.16.2-1ubuntu0.16.04.1 modemmanager 1.6.4-1ubuntu0.16.04.1 * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network-manager, gnome-control-center etc.) [Regression Potential] * The package comes from Zesty and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
@Łukasz, Do you think it's easier for us to SRU LP: #1693756, #17 ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: In Progress Status in libmbim source package in Xenial: New Status in libqmi source package in Xenial: New Status in modemmanager source package in Xenial: New Bug description: [Impact] * the new modemmanager packages bring in DW5816 supporting. * These modemmanager packages is needed to support new devices. [Test Case] * install modemmanager and it's dependencies from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054 libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1 libmbim-proxy 1.14.0-1ubuntu0.16.04.1 libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1 libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1 libqmi-proxy 1.16.2-1ubuntu0.16.04.1 modemmanager 1.6.4-1ubuntu0.16.04.1 * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network-manager, gnome-control-center etc.) [Regression Potential] * The package comes from Zesty and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737741] Re: rhythembox-client --seek fails at more than 2148 seconds
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: rhythmbox (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1737741 Title: rhythembox-client --seek fails at more than 2148 seconds Status in rhythmbox package in Ubuntu: New Bug description: System Information: Description: Ubuntu 17.04 Release: 17.04 rhythmbox: Installiert: 3.4.1-2ubuntu1 Installationskandidat: 3.4.1-2ubuntu1 Versionstabelle: *** 3.4.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status Behavior: via the commandline the rythembox client can skip to a specific second via the command rhythmbox-client --seek This works for seeking up to second 2147. Any number beyond that skips to the next track, even if the track is longer instead of going to the correct position in the file itself (the track has over 4000 seconds) my guess is that that the internal format is a signed 32-Bit Int that overflows. 2148 seconds = 214800 milliseconds -> cast to Int32 is -2146967296 which would certainly produce an error (seeking to a negative number) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1737741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1496542] Re: Running processes left after disabling screen reader
Do we know what's launching the process? It's not systemd as I checked. There should be a workaround, no? I'm going to try to set /usr/bin/speech-dispatcher and the binaries under /usr/lib/speech-dispatcher-modules with chmod -x to see what happens. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1496542 Title: Running processes left after disabling screen reader Status in speech-dispatcher package in Ubuntu: Triaged Bug description: After I disabled my screen reader, I noticed that when running "ps xa | grep -P 'speech-dispatcher.*\.conf'" I get: 17906 tty2 Sl+0:09 /usr/lib/speech-dispatcher-modules/sd_espeak /etc/speech-dispatcher/modules/espeak.conf 17911 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_cicero /etc/speech-dispatcher/modules/cicero.conf 17915 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/generic.conf 17918 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf 24407 pts/0S+ 0:00 grep --color=auto -P speech-dispatcher.*\.conf So it seems as though it left some running processes behind after I disabled it. I have also attached a screenshot of my Sound settings which show that they are still running (Sound_Application_List2.png). --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid Package Information: speech-dispatcher: Installed: 0.8.1-0ubuntu1 Candidate: 0.8.1-0ubuntu1 Version table: *** 0.8.1-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: speech-dispatcher 0.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 16 20:27:00 2015 InstallationDate: Installed on 2015-07-29 (49 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: speech-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1496542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 559105] Re: Temperature in The Hague, The Netherlands is always the same
** Changed in: libgweather Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/559105 Title: Temperature in The Hague, The Netherlands is always the same Status in libgweather: Fix Released Status in libgweather package in Ubuntu: Triaged Bug description: Binary package hint: gnome-panel In gnome-panel under clock the weather an temperature is shown for The Netherland. The temperature is always shown as 5 degrees Centugrade (day and night), This is not the temperature in the netherlands right now. Changing the location pe Rotterdam for The Hague has no influence. The clock keeps showing 5 degrees centigrade ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-panel 1:2.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 NonfreeKernelModules: wl fglrx Architecture: amd64 Date: Fri Apr 9 12:20:39 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-panel To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/559105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245245] Re: MMIO write FAULT
liang, please test http://cdimage.ubuntu.com/daily-live/current/ to confirm. If reproducible file a new report via https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+filebug and feel free to subscribe me to it. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Confirmed => Incomplete ** Attachment removed: "Error screenshot" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1245245/+attachment/5021706/+files/IMG_20171212_211139.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1245245 Title: MMIO write FAULT Status in xserver-xorg-video-nouveau package in Ubuntu: Incomplete Bug description: Hi there, I'm not sure if I am right here. I installed ubuntu 13.10 i had mint for a while now (1,5 years), but now this happens: When I use unity, it sometime crashes, so the system really stays, there is nothing more able to to. I will give you a dmesg, please check if it could help you. Of course this is before the sytsem realy gives up, but I hope that can help. Is there any ppa to try for a newer version? Thanks my dmesg: http://ubuntuone.com/3ris30VkDHx2WSzo2VGhcZ Thanks, Martin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1245245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
Sadly the test results got wiped out from Bileto for unknown reasons, I have re-run the tests. They should appear here https://bileto.ubuntu.com/#/ticket/3054 under the Automated Test Results. What about my question about cherry-picking the new modem code to the xenial version of modemmanager? As said, seeing how many packages this SRU involves I'm starting to get worried about if this will get accepted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: In Progress Status in libmbim source package in Xenial: New Status in libqmi source package in Xenial: New Status in modemmanager source package in Xenial: New Bug description: [Impact] * the new modemmanager packages bring in DW5816 supporting. * These modemmanager packages is needed to support new devices. [Test Case] * install modemmanager and it's dependencies from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054 libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1 libmbim-proxy 1.14.0-1ubuntu0.16.04.1 libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1 libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1 libqmi-proxy 1.16.2-1ubuntu0.16.04.1 modemmanager 1.6.4-1ubuntu0.16.04.1 * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network-manager, gnome-control-center etc.) [Regression Potential] * The package comes from Zesty and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather
** Also affects: libgweather (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-weather (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: gnome-weather (Ubuntu Xenial) ** Also affects: libgweather (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gnome-weather (Ubuntu Zesty) Importance: Undecided Status: New ** No longer affects: gnome-weather (Ubuntu Zesty) ** Changed in: libgweather (Ubuntu Xenial) Status: New => In Progress ** Changed in: libgweather (Ubuntu Xenial) Importance: Undecided => High ** Changed in: libgweather (Ubuntu Zesty) Status: New => In Progress ** Changed in: libgweather (Ubuntu Zesty) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Xenial: In Progress Status in libgweather source package in Zesty: In Progress Status in libgweather source package in Artful: In Progress Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245245] Re: MMIO write FAULT
Attached my error screenshot ** Attachment added: "Error screenshot" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1245245/+attachment/5021706/+files/IMG_20171212_211139.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1245245 Title: MMIO write FAULT Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Hi there, I'm not sure if I am right here. I installed ubuntu 13.10 i had mint for a while now (1,5 years), but now this happens: When I use unity, it sometime crashes, so the system really stays, there is nothing more able to to. I will give you a dmesg, please check if it could help you. Of course this is before the sytsem realy gives up, but I hope that can help. Is there any ppa to try for a newer version? Thanks my dmesg: http://ubuntuone.com/3ris30VkDHx2WSzo2VGhcZ Thanks, Martin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1245245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737762] [NEW] i wont let me update and my terminal is going crazy
Public bug reported: it wont let me update and terminal is crazy ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Dec 12 06:57:52 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 3450/3470] [103c:30dc] InstallationDate: Installed on 2017-03-14 (272 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PCD Ver. F.17 dmi.board.name: 30DC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 87.2A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCDVer.F.17:bd03/05/2010:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.17:rvnHewlett-Packard:rn30DC:rvrKBCVersion87.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 6930p dmi.product.version: F.17 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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: Tue Dec 12 02:50:18 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Assignee: brandon cunningham (brandonkilecunningham) Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial ** Changed in: xorg (Ubuntu) Assignee: (unassigned) => brandon cunningham (brandonkilecunningham) -- 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/1737762 Title: i wont let me update and my terminal is going crazy Status in xorg package in Ubuntu: New Bug description: it wont let me update and terminal is crazy ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Dec 12 06:57:52 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 3450/3470] [103c:30dc] InstallationDate: Installed on 2017-03-14 (272 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE
[Desktop-packages] [Bug 1312780] Re: Floating menu mostly disappears in fullscreen mode
** Changed in: vinagre (Fedora) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/1312780 Title: Floating menu mostly disappears in fullscreen mode Status in vinagre package in Ubuntu: Confirmed Status in vinagre package in Fedora: Won't Fix Bug description: When going into full screen mode on Ubuntu 14.04 (connecting to a Ubuntu 14.04 running Unity and x11vnc), the floating menu at the top of the screen is mostly inaccessible. I say mostly because you can wave your mouse around at the top center of the screen where the menu should appear and you will occasionally see something flash up for a split second. If you click continuously while waving the mouse around, you will occasionally hit a button. Here are some more details: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center vinagre: Installed: 3.10.2-0ubuntu1 Candidate: 3.10.2-0ubuntu1 Version table: *** 3.10.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Menu would appear at the top of the full screen window or at least when mouse hovers at top of full screen window. 4) What happened instead Occasional split second pop up of window and tool tips. Can also click buttons if you are lucky. Please let me know if there are logs I can pull. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/1312780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen
Jumping cursor sounds like a separate issue -- 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/1723857 Title: onscreen keyboard appears whenever i touch touchscreen Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Artful: Triaged Bug description: Impact == I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is disabled in System Preferences > Universal Access. This didn't happen in any previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based. Test Case = 0. Find a laptop with a touch screen that works. 1. Settings > Universal Access > Typing > Screen Keyboard = OFF 2. Touch the screen. Regression Potential Workaround == https://extensions.gnome.org/extension/1326/block-caribou/ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737751] [NEW] nvidia-graphics-drivers-340 340.104-0ubuntu3 ADT test failure with linux 4.15.0-1.2
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-340/20171212_010125_cd550@/log.gz armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/armhf/n/nvidia-graphics-drivers-340/20171212_021246_cd550@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-340/20171212_013858_cd550@/log.gz ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1737751 Title: nvidia-graphics-drivers-340 340.104-0ubuntu3 ADT test failure with linux 4.15.0-1.2 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-340/20171212_010125_cd550@/log.gz armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/armhf/n/nvidia-graphics-drivers-340/20171212_021246_cd550@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-340/20171212_013858_cd550@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1737751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737750] [NEW] nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz ** Affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2
** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1737750/+attachment/5021698/+files/make.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737751] Re: nvidia-graphics-drivers-340 340.104-0ubuntu3 ADT test failure with linux 4.15.0-1.2
** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1737751/+attachment/5021699/+files/make.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1737751 Title: nvidia-graphics-drivers-340 340.104-0ubuntu3 ADT test failure with linux 4.15.0-1.2 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-340/20171212_010125_cd550@/log.gz armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/armhf/n/nvidia-graphics-drivers-340/20171212_021246_cd550@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-340/20171212_013858_cd550@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1737751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1312780]
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/1312780 Title: Floating menu mostly disappears in fullscreen mode Status in vinagre package in Ubuntu: Confirmed Status in vinagre package in Fedora: Won't Fix Bug description: When going into full screen mode on Ubuntu 14.04 (connecting to a Ubuntu 14.04 running Unity and x11vnc), the floating menu at the top of the screen is mostly inaccessible. I say mostly because you can wave your mouse around at the top center of the screen where the menu should appear and you will occasionally see something flash up for a split second. If you click continuously while waving the mouse around, you will occasionally hit a button. Here are some more details: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center vinagre: Installed: 3.10.2-0ubuntu1 Candidate: 3.10.2-0ubuntu1 Version table: *** 3.10.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Menu would appear at the top of the full screen window or at least when mouse hovers at top of full screen window. 4) What happened instead Occasional split second pop up of window and tool tips. Can also click buttons if you are lucky. Please let me know if there are logs I can pull. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/1312780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245245] Re: MMIO write FAULT
I'm using ubuntu 16.04. This bug also affects me. The machine can only start to emergency mode because of this bug. Error: [Hardware Error] nouveau bus: MMIO write of xx FAULT ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1245245 Title: MMIO write FAULT Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Hi there, I'm not sure if I am right here. I installed ubuntu 13.10 i had mint for a while now (1,5 years), but now this happens: When I use unity, it sometime crashes, so the system really stays, there is nothing more able to to. I will give you a dmesg, please check if it could help you. Of course this is before the sytsem realy gives up, but I hope that can help. Is there any ppa to try for a newer version? Thanks my dmesg: http://ubuntuone.com/3ris30VkDHx2WSzo2VGhcZ Thanks, Martin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1245245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1312780]
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/1312780 Title: Floating menu mostly disappears in fullscreen mode Status in vinagre package in Ubuntu: Confirmed Status in vinagre package in Fedora: Won't Fix Bug description: When going into full screen mode on Ubuntu 14.04 (connecting to a Ubuntu 14.04 running Unity and x11vnc), the floating menu at the top of the screen is mostly inaccessible. I say mostly because you can wave your mouse around at the top center of the screen where the menu should appear and you will occasionally see something flash up for a split second. If you click continuously while waving the mouse around, you will occasionally hit a button. Here are some more details: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center vinagre: Installed: 3.10.2-0ubuntu1 Candidate: 3.10.2-0ubuntu1 Version table: *** 3.10.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Menu would appear at the top of the full screen window or at least when mouse hovers at top of full screen window. 4) What happened instead Occasional split second pop up of window and tool tips. Can also click buttons if you are lucky. Please let me know if there are logs I can pull. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/1312780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1715054] Re: Developer name not shown for snaps
SRU verification for Zesty: I have reproduced the problem with gnome-software 3.22.7-0ubuntu3.17.04.7 in zesty-updates and have verified that the version of gnome-software 3.22.7-0ubuntu3.17.04.8 in -proposed fixes the issue. Marking as verification-done ** Tags removed: verification-needed verification-needed-zesty ** Tags added: verification-done verification-done-zesty -- 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/1715054 Title: Developer name not shown for snaps Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] The snap developer is not shown in GNOME Software. [Test Case] 1. Open GNOME Software 2. Search for "Moon Buggy" and click on it Expected result: The developer name is shown as "dholbach" Observed result: The developer name is not shown anywhere. [Regression Potential] Low, as we just populate the "project group" (shows as developer) with the snap "developer" field. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1715054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706500] Re: Update snap store name "Snap Store"
SRU verification for Zesty: I have reproduced the problem with gnome-software 3.22.7-0ubuntu3.17.04.7 in zesty-updates and have verified that the version of gnome-software 3.22.7-0ubuntu3.17.04.8 in -proposed fixes the issue. Marking as verification-done ** Tags removed: verification-needed verification-needed-zesty ** Tags added: verification-done verification-done-zesty -- 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/1706500 Title: Update snap store name "Snap Store" Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] Currently various things are shown for the snap "Source" field: 3.20: "Ubuntu Snappy Store" - hard-coded 3.22 / 3.24: "dashboard.snapcraft.io" - is inferred from the snap metadata The officially decided store name is "Ubuntu Store" and this should show in this field. [Test Case] 1. Open GNOME Software. 2. Install a snap (e.g. moon-buggy). 3. Select installed tab. 4. Look at the "Source" field when looking at the app details. Expected result: The source is "Snap Store" Observed result: The source is something else. [Regression Potential] Small risk of breaking existing code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1706500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736232] Re: GNOME Software shows U1 login for snaps
SRU verification for Zesty: I have reproduced the problem with gnome-software 3.22.7-0ubuntu3.17.04.7 in zesty-updates and have verified that the version of gnome-software 3.22.7-0ubuntu3.17.04.8 in -proposed fixes the issue. @popey, the "classic snap" defect is reported in bug 1690280 Marking as verification-done -- 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/1736232 Title: GNOME Software shows U1 login for snaps Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: As I understood it, GNOME Software is no longer supposed to be asking for U1 logins when installing snaps. I just did a clean up to date install of 16.04.3 and tried launching G-S and it asked me for a U1 login. Steps to reproduce: Install 16.04.3 Update to latest software in the repo Open Ubuntu Software Click the "hiri" banner Click install button Expected behaviour:- Policykit login box appears Actual behaviour:- Ubuntu One login/sign up box appears ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.5-0ubuntu0.16.04.6 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 4 19:56:34 2017 InstallationDate: Installed on 2017-12-04 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1736232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737741] [NEW] rhythembox-client --seek fails at more than 2148 seconds
Public bug reported: System Information: Description:Ubuntu 17.04 Release:17.04 rhythmbox: Installiert: 3.4.1-2ubuntu1 Installationskandidat: 3.4.1-2ubuntu1 Versionstabelle: *** 3.4.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status Behavior: via the commandline the rythembox client can skip to a specific second via the command rhythmbox-client --seek This works for seeking up to second 2147. Any number beyond that skips to the next track, even if the track is longer instead of going to the correct position in the file itself (the track has over 4000 seconds) my guess is that that the internal format is a signed 32-Bit Int that overflows. 2148 seconds = 214800 milliseconds -> cast to Int32 is -2146967296 which would certainly produce an error (seeking to a negative number) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1737741 Title: rhythembox-client --seek fails at more than 2148 seconds Status in rhythmbox package in Ubuntu: New Bug description: System Information: Description: Ubuntu 17.04 Release: 17.04 rhythmbox: Installiert: 3.4.1-2ubuntu1 Installationskandidat: 3.4.1-2ubuntu1 Versionstabelle: *** 3.4.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status Behavior: via the commandline the rythembox client can skip to a specific second via the command rhythmbox-client --seek This works for seeking up to second 2147. Any number beyond that skips to the next track, even if the track is longer instead of going to the correct position in the file itself (the track has over 4000 seconds) my guess is that that the internal format is a signed 32-Bit Int that overflows. 2148 seconds = 214800 milliseconds -> cast to Int32 is -2146967296 which would certainly produce an error (seeking to a negative number) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1737741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1537057] Re: rhytembox-client --print-playing-format %te partially broken
I am currently on xubuntu 17.04 and cannot reproduce this anymore. Seems to be running fine now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1537057 Title: rhytembox-client --print-playing-format %te partially broken Status in rhythmbox package in Ubuntu: New Bug description: Hello Launchpad, I was setting up keyboard shortcuts for controlling rhytembox entirely via keyboard in the background. While most of the commands can be bound quite easily using the rhytembox-client, i found a weird behavior when using the current time to skip ahead (using seek) In order to get the current position in the track, in use the command rhytembox-client --print-playing-format %te As this gives me the format in hour:minute:seconds. This works up to a track length of 1:11:34, then there seems to be an error, and counting starts from 0 again; here is an example of the output while listening to a long track: while true; do rhythmbox-client --print-playing-format %te; sleep 1; done 1:11:30 1:11:31 1:11:32 1:11:33 1:11:34 Unbekannt 0:01 0:02 0:03 0:04 0:05 0:06 0:07 ^C I've tested this with several tracks - they all split behave the same. So my guess is that this is some kind of overflow in the timing ? Of course, not many tracks are that long, but i'd still like to point this out. Makes the while skipping forward via the client very hard, as the time playing is not really reliable. Not sure if this should be mentioned here or go into the wishlist, but it would be great if the output format could also print seconds. It would be very useful with seek to easily fast forward/backward. Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1537057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
** Package changed: gnome-shell (Ubuntu) => unity (Ubuntu) -- 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/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) Status in systemd package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on my computer. I'm using Unity DE, with default settings. The problem is not about taking screnshots. xev recognizes when I press down the alt key, but nothing happens when I press Print Screen with alt being pressed (it does when PrintScreen is pressed by itself) Here is evtest output when I press Alt+Printscreen: # Alt pressed down: Event: time 1510817663.883489, -- SYN_REPORT Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.923476, -- SYN_REPORT Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.963479, -- SYN_REPORT Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046 # Print screen pressed Event: time 1510817663.993036, -- SYN_REPORT Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 # Alt released Event: time 1510817664.945032, -- SYN_REPORT Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1 Event: time 1510817664.945086, -- SYN_REPORT Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0 Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1510817664.945097, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12.1 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: Unity:Unity7:ubuntu CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules Date: Thu Nov 16 08:29:46 2017 InstallationDate: Installed on 2017-03-26 (234 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1667227 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Bug description: 1) $ lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 2) $ apt-cache policy mate-terminal mate-terminal: Installed: 1.17.0-0ubuntu1 Candidate: 1.17.0-0ubuntu1 3) Open mate-terminal Select "Edit" -> "Keyboard Shortcuts" Select "Help"->"Contents", click on default shortcut key "F1" to change Try to set it to various key sequences. Sometimes bug is triggered by pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting Ctrl-Shift-W / Crtl-Shift-Alt-W Expected: changed keyboard shortcut for "Help"->"Contents" 4) Abort and closed mate-terminal ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-terminal 1.17.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Feb 23 09:33:19 2017 ExecutablePath: /usr/bin/mate-terminal ExecutableTimestamp: 1484233434 InstallationDate: Installed on 2017-02-22 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: mate-terminal ProcCwd: /home/user SegvAnalysis: Segfault happened at: 0x7f883e41c321 : testb $0x4,0x16(%rax) PC (0x7f883e41c321) ok source "$0x4" ok destination "0x16(%rax)" (0x7001e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1667227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
On my Unity session on 17.10 printscreen doesn't work, neither does ALT+Printscreen (it triggers HUD), nor CTRL+ALT+T to open terminal. Seems a bunch of them don't work. -- 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/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on my computer. I'm using Unity DE, with default settings. The problem is not about taking screnshots. xev recognizes when I press down the alt key, but nothing happens when I press Print Screen with alt being pressed (it does when PrintScreen is pressed by itself) Here is evtest output when I press Alt+Printscreen: # Alt pressed down: Event: time 1510817663.883489, -- SYN_REPORT Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.923476, -- SYN_REPORT Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.963479, -- SYN_REPORT Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046 # Print screen pressed Event: time 1510817663.993036, -- SYN_REPORT Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 # Alt released Event: time 1510817664.945032, -- SYN_REPORT Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1 Event: time 1510817664.945086, -- SYN_REPORT Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0 Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1510817664.945097, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12.1 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: Unity:Unity7:ubuntu CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules Date: Thu Nov 16 08:29:46 2017 InstallationDate: Installed on 2017-03-26 (234 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1732612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (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/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on my computer. I'm using Unity DE, with default settings. The problem is not about taking screnshots. xev recognizes when I press down the alt key, but nothing happens when I press Print Screen with alt being pressed (it does when PrintScreen is pressed by itself) Here is evtest output when I press Alt+Printscreen: # Alt pressed down: Event: time 1510817663.883489, -- SYN_REPORT Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.923476, -- SYN_REPORT Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.963479, -- SYN_REPORT Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046 # Print screen pressed Event: time 1510817663.993036, -- SYN_REPORT Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 # Alt released Event: time 1510817664.945032, -- SYN_REPORT Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1 Event: time 1510817664.945086, -- SYN_REPORT Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0 Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1510817664.945097, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12.1 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: Unity:Unity7:ubuntu CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules Date: Thu Nov 16 08:29:46 2017 InstallationDate: Installed on 2017-03-26 (234 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1732612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
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/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on my computer. I'm using Unity DE, with default settings. The problem is not about taking screnshots. xev recognizes when I press down the alt key, but nothing happens when I press Print Screen with alt being pressed (it does when PrintScreen is pressed by itself) Here is evtest output when I press Alt+Printscreen: # Alt pressed down: Event: time 1510817663.883489, -- SYN_REPORT Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.923476, -- SYN_REPORT Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.963479, -- SYN_REPORT Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046 # Print screen pressed Event: time 1510817663.993036, -- SYN_REPORT Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 # Alt released Event: time 1510817664.945032, -- SYN_REPORT Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1 Event: time 1510817664.945086, -- SYN_REPORT Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0 Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1510817664.945097, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12.1 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: Unity:Unity7:ubuntu CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules Date: Thu Nov 16 08:29:46 2017 InstallationDate: Installed on 2017-03-26 (234 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1732612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
Not sure how any of this helps, I would require somebody with graphics/keyboard stack to understand what/where has regressed. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on my computer. I'm using Unity DE, with default settings. The problem is not about taking screnshots. xev recognizes when I press down the alt key, but nothing happens when I press Print Screen with alt being pressed (it does when PrintScreen is pressed by itself) Here is evtest output when I press Alt+Printscreen: # Alt pressed down: Event: time 1510817663.883489, -- SYN_REPORT Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.923476, -- SYN_REPORT Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.963479, -- SYN_REPORT Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046 # Print screen pressed Event: time 1510817663.993036, -- SYN_REPORT Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 # Alt released Event: time 1510817664.945032, -- SYN_REPORT Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1 Event: time 1510817664.945086, -- SYN_REPORT Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0 Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1510817664.945097, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12.1 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: Unity:Unity7:ubuntu CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules Date: Thu Nov 16 08:29:46 2017 InstallationDate: Installed on 2017-03-26 (234 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1732612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736232] Re: GNOME Software shows U1 login for snaps
Seems some snaps install okay, some don't. Looks like classic snaps return a 400 bad request in gnome-software, but non-classic ones install okay. -- 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/1736232 Title: GNOME Software shows U1 login for snaps Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: As I understood it, GNOME Software is no longer supposed to be asking for U1 logins when installing snaps. I just did a clean up to date install of 16.04.3 and tried launching G-S and it asked me for a U1 login. Steps to reproduce: Install 16.04.3 Update to latest software in the repo Open Ubuntu Software Click the "hiri" banner Click install button Expected behaviour:- Policykit login box appears Actual behaviour:- Ubuntu One login/sign up box appears ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.5-0ubuntu0.16.04.6 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 4 19:56:34 2017 InstallationDate: Installed on 2017-12-04 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1736232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather
For the record I'd like to mention that the key information to spot the root cause of this bug was provided in Christophe's comment #10, even if the solutions differ. Thanks, Christophe, for your helpful contribution! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Artful: In Progress Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736232] Re: GNOME Software shows U1 login for snaps
Seems my system wasn't completely up to date, re-tested after doing all updates on Zesty and it works. Yay! Sorry for the false lead. -- 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/1736232 Title: GNOME Software shows U1 login for snaps Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: As I understood it, GNOME Software is no longer supposed to be asking for U1 logins when installing snaps. I just did a clean up to date install of 16.04.3 and tried launching G-S and it asked me for a U1 login. Steps to reproduce: Install 16.04.3 Update to latest software in the repo Open Ubuntu Software Click the "hiri" banner Click install button Expected behaviour:- Policykit login box appears Actual behaviour:- Ubuntu One login/sign up box appears ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.5-0ubuntu0.16.04.6 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 4 19:56:34 2017 InstallationDate: Installed on 2017-12-04 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1736232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714282] Re: Sorry something went wrong GDBus:
Same issue here, Ubuntu 17.10 -- 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/1714282 Title: Sorry something went wrong GDBus: Status in xorg package in Ubuntu: Confirmed Bug description: After applying the latest update the Software-center now opens but still has a problem. For the Launch pad, software center, in Ubuntu 17.10 it reports this error when trying to open it. "Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown Method: No such interface` org.gnome.Shell.Extensions on object at path /org/gnome/shell". Some of the links to the software doesn't work. Some of the buttons of categories doesn't work. Updates never show "software to be updated" anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729999] Re: Please remove prosper source, superseded
** Changed in: prosper (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to prosper in Ubuntu. https://bugs.launchpad.net/bugs/172 Title: Please remove prosper source, superseded Status in prosper package in Ubuntu: New Status in prosper package in Debian: Fix Released Bug description: Please remove the *SOURCE* package prosper as prosper is now incorporated into TeX Live, and src:texlive-base builds a transitional package prosper. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prosper/+bug/172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734943] Re: no internet access, from any wi-fi network or wired network
** Also affects: network-manager (Ubuntu) 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/1734943 Title: no internet access, from any wi-fi network or wired network Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Today, when i started Ubuntu. In bar, on the network icon appear a "?" symbol. I tried to connect Ubuntu to internet with a wired cable and another wi-fi network. He's connect to wi-fi and wired cable network but appears a "?" symbol in the network icon and i don't have access on the internet. Sorry for my bad english :))) Thank you! P.S. i use Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737458] Re: package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando
There appears to be a trigger loop: Configurando odbcinst (2.3.4-1.1) ... dpkg: se encontró un bucle al procesar los disparadores: la cadena de paquetes cuyos disparadores son o pueden ser responsables: libgdk-pixbuf2.0-0:amd64 -> libgdk-pixbuf2.0-0:i386 disparadores pendientes de paquetes que no son o pueden no ser resolubles: systemd: /etc/init.d libvlc-bin:amd64: /usr/lib/x86_64-linux-gnu/vlc/plugins libc-bin: ldconfig bamfdaemon: /usr/share/applications gnome-icon-theme: /usr/share/icons/gnome sgml-base: update-sgmlcatalog initramfs-tools: update-initramfs menu: /usr/share/menu libgdk-pixbuf2.0-0:i386: /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders libgdk-pixbuf2.0-0:amd64: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders dictionaries-common: update-default-wordlist ureadahead: /etc/init.d gconf2: /usr/share/GConf/gsettings: /usr/share/gconf/schemas: /usr/share/gconf/defaults dpkg: error al procesar el paquete systemd (--configure): los disparadores han entrado en bucle, abandonando ** Package changed: systemd (Ubuntu) => gdk-pixbuf (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1737458 Title: package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando Status in gdk-pixbuf package in Ubuntu: New Bug description: upgrade from Artful to Bionic ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-18.21-lowlatency 4.13.13 Uname: Linux 4.13.0-18-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 Date: Mon Dec 11 02:56:44 2017 ErrorMessage: los disparadores han entrado en bucle, abandonando InstallationDate: Installed on 2012-02-27 (2113 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.4rc1, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando UpgradeStatus: Upgraded to bionic on 2017-12-11 (0 days ago) dmi.bios.date: 01/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.20F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.20F:bd01/13/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1737458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737458] [NEW] package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando
You have been subscribed to a public bug: upgrade from Artful to Bionic ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-18.21-lowlatency 4.13.13 Uname: Linux 4.13.0-18-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 Date: Mon Dec 11 02:56:44 2017 ErrorMessage: los disparadores han entrado en bucle, abandonando InstallationDate: Installed on 2012-02-27 (2113 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.4rc1, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando UpgradeStatus: Upgraded to bionic on 2017-12-11 (0 days ago) dmi.bios.date: 01/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.20F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.20F:bd01/13/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando https://bugs.launchpad.net/bugs/1737458 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721419] Re: Average rating for apps incorrect
SRU verification for Xenial: I have reproduced the problem with gnome-software 3.20.5-0ubuntu0.16.04.6 in xenial-updates and have verified that the version of gnome-software 3.20.5-0ubuntu0.16.04.7 in -proposed fixes the issue. Marking as verification-done ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1721419 Title: Average rating for apps incorrect Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Bug description: The average rating for apps in ubuntu-software seems to be calculated incorrectly. For example "Genius Math Tool" had an average rating of 2 stars and 9 reviews each with 4-5 star rating. So i added another 4 star review. The expected average rating is 4 stars currently a 2 star rating is displayed. Another package with obviously weird average rating is "Log File Viewer" currently at average 3 star rating. Considering the reviews it should be closer to 4.6. Further Info: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $apt-cache policy ubuntu-software ubuntu-software: Installed: 3.20.5-0ubuntu0.16.04.6 Candidate: 3.20.5-0ubuntu0.16.04.6 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-software 3.20.5-0ubuntu0.16.04.6 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 5 01:51:14 2017 InstallationDate: Installed on 2017-05-22 (135 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1721419/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1715054] Re: Developer name not shown for snaps
SRU verification for Xenial: I have reproduced the problem with gnome-software 3.20.5-0ubuntu0.16.04.6 in xenial-updates and have verified that the version of gnome-software 3.20.5-0ubuntu0.16.04.7 in -proposed fixes the issue. Marking as verification-done ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1715054 Title: Developer name not shown for snaps Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] The snap developer is not shown in GNOME Software. [Test Case] 1. Open GNOME Software 2. Search for "Moon Buggy" and click on it Expected result: The developer name is shown as "dholbach" Observed result: The developer name is not shown anywhere. [Regression Potential] Low, as we just populate the "project group" (shows as developer) with the snap "developer" field. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1715054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713586] Re: gnome-software displays wildly inaccurate estimate of package size when a certain deb file is double-clicked in nautilus
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1713586 Title: gnome-software displays wildly inaccurate estimate of package size when a certain deb file is double-clicked in nautilus Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Bug description: [Impact] For .debs with a large Installed-Size GNOME Software shows the incorrect value. This is due to an integer overflow. [Test Case] 1. Launch the attached test-deb_1_all.deb file in GNOME Software 2. Check the Size field. Expected result: Size is set to 3.9GB Observed result: Size is set to 18.4EB [Regression Potential] Took upstream commit that fixed this by using a 64 bit number to calculate size. Unlikely to cause further issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1713586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
