[Desktop-packages] [Bug 1581560] Re: system crash when attaching external display
Have resolved the issue by installing yakkety kernel: sudo add-apt-repository ppa:canonical-kernel-team/ppa sudo apt update sudo apt install linux-image-generic-lts-yakkety -- 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/1581560 Title: system crash when attaching external display Status in xorg package in Ubuntu: Expired Bug description: After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes and reboots when I attach an external display. Process: - put laptop to sleep. - come into work the next day - open up laptop - plug in external display - observe bug Expected behavior: I can attach the external display Observed behavior: system shows black screen on both laptop and display and after a minute or two reboots. Laptop drives external display fine after reboot. I ssh to the laptop from another machine and monitored /var/log/syslog, /var/log/Xorg.0.log, and ~/.xsession-errors. All I see in those files before the lockup is this, from Xorg.0.log: [ 34289.447] (II) intel(0): Enabled output DP1-8 [ 34289.448] (II) intel(0): Enabled output DP1-1 [ 34289.460] (II) intel(0): resizing framebuffer to 2560x1440 [ 34289.482] (II) intel(0): switch to mode 2560x1440@60.0 on DP1-8 using pipe 0, (0, 0), rotation normal, reflection none ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 13 09:24:07 2016 DistUpgraded: 2016-04-21 20:51:13,846 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-30-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227] InstallationDate: Installed on 2015-09-10 (245 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20BS0031US ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-22 (21 days ago) dmi.bios.date: 05/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET29W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BS0031US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BS0031US:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0031US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BS0031US dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO drirc: version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 13 09:04:56 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4669 vendor AUO xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1616413] Re: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all
Hi, Any luck with a fix? I am still having a problem despite upgrading to 16.10. Suvam. -- 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/1616413 Title: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: I am not getting any sound at all from my Dell Optiplex 7040 (running Ubuntu 16.04). The volume control icon is showing up next to the clock, and I am able to change the volume levels: but this has no effect. There is absolutely NO sound at all. In Settings -> Output, no devices are listed. Strangely enough, aplay -l results in: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3234 Analog [ALC3234 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 which indicates that the sound card is getting detected. I tried sudo alsa force-reload following which I rebooted. That doesn't fix the problem. I opened alsamixer: it is detecting the sound card perfectly and nothing is muted. Still, there is no audio. I then tried the following: sudo apt-get remove --purge alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio sudo alsa force-reload And still there is no audio. I'd be really grateful if you could look into this. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: suvam 4522 F pulseaudio suvam 5594 F alsamixer CurrentDesktop: Unity Date: Wed Aug 24 15:59:21 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-02-12 (193 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: suvam 4522 F pulseaudio suvam 5594 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2016-08-11 (13 days ago) dmi.bios.date: 12/04/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0HD5W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd12/04/2015:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 7040 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1616413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup
It also happens on Gentoo Linux using gnome-session-3.20.2: https://bugs.gentoo.org/show_bug.cgi?id=601160 ** Bug watch added: Gentoo Bugzilla #601160 https://bugs.gentoo.org/show_bug.cgi?id=601160 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1582496 Title: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup Status in gnome-session package in Ubuntu: Confirmed Bug description: I submitted this question a week but did not receive an answer or advice to solving them. https://answers.launchpad.net/ubuntu/+source /gnome-session/+question/293479 These failures are still plaguing my syslog every time I activate Nautilus. Appreciate help to resolve these failures. Earlier question After a recent updating, I notice these failures in the systemlogs. May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:35:01 Eliot org.gnome.zeitgeist.Engine[1400]: (zeitgeist-daemon:2197): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed May 9 16:42:54 Eliot gnome-session[1576]: (nautilus:2606): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed May 9 16:59:53 Eliot gnome-session[1576]: (nautilus:2842): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed May 9 17:00:19 Eliot gnome-session[1576]: (nautilus:2857): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed The last three failures appears whenever I activate nautilus. Nautilus will appear and work as usual. How can I resolve these failure notices? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1582496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers
https://blueprints.launchpad.net/ubuntu/+spec/foundations-y-local- resolver has the two outstanding issues to switch NM over to resolved too. These are unblocked now: the new resolved DNS plugin is in upstream master since around September, and NM 1.4 landed in zesty-proposed yesterday. Let's land that first, then backport the DNS plugin and switch it over, then we'll consistently use resolved everywhere and that comment will be much easier to write. This is also the reason why I didn't do this comment change yet, I think it's better to wait for the above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638836 Title: resolv.conf for resolved stub server should have a comment how to see the actual servers Status in network-manager package in Ubuntu: Triaged Status in resolvconf package in Ubuntu: In Progress Bug description: resolv.conf currently just has nameserver 127.0.0.53 with resolved (its local stub resolver). We should have an extra comment on top of that that says # systemd-resolved stub resolver; run "systemd-resolve --status" to see the actual name servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1610293] Re: mic cartoon voice
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1610293 Title: mic cartoon voice Status in pulseaudio package in Ubuntu: Expired Bug description: I have one sort of typical problem, and one very strange problem, both related to the audio. First the typical one, because, clearly, the strange one is the headlining act here. Typical kind of problem: My system keeps changing from audio line out, to hdmi out as the default choice, and I have to keep moving it back by hand from systemsettings. It seems to be related to squeezelite, but am not sure. Strange problem: After updating to 16.04, my microphone transmits only a strange, helium inflected cartoon voice when I speak. This strange transmission works with arecord or ffmpeg from command line, and with skype testing service. The latter convinces me that it is not a recording issue, but really a sound capture issue. Pulseaudio will not allow me to select my external microphone jack, though there is a microphone plugged in. It appears to use my webcam (logitech C310) mic. There was no such problem last week under 14.04. I cannot think of any other tests to perform. If it were allowed, I would upload a short recording of my voice, primarily for your amusement. A few details: $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1610293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1621246] Re: Bluetooth A2DP audio stops after reconnecting headset
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1621246 Title: Bluetooth A2DP audio stops after reconnecting headset Status in pulseaudio package in Ubuntu: Expired Bug description: Ubuntu 16.04.1 64-bit. DELL E7450 laptop, connected to an LG HBS900 headset. 1. Pair the headset 2. All Settings -> Sound, set the mode to High Fidelity Playback (A2DP Sink) (otherwise the sound is horrible) 3. Test, ensure "Front Left" and "Front Right" sound as they should. 4. Disconnect the headset via the Bluetooth indicator in the system tray. 5. Connect the headset to another device and play audio through it (I took a call). 6. Connect back the headset to the laptop. 7. Attempt to play audio, say in SMPlayer. No audio comes through. SMPlayer doesn't advance the seek button. 8. Run `pulseaudio --kill`. 9. Reconnect the headset a bunch of times. 10. In Settings -> Sound, try to set the mode to High Fidelity. Only the Headset mode worked, with mono sound. When I'd change the value to High Fidelity, the active sound device moved to the internal sound card. After a couple more reconnections, I could finally get A2DP sound again. However, the sound SKIPS randomly a couple times a minute (bug 405294). Playing the exact same MP3 with the exact same player (SMPlayer) on Kubuntu 16.04.1 doesn't reproduce this problem, despite presumably using the same Bluetooth stack. Super frustrating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1621246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1627239] Re: Web pages not rendering with e10s enabled and AppArmor profile in enforce mode
If you are running in complain mode you could look at the audit log and see what AppArmor complains about when you are browsing the web with e10s enabled. If you see AppArmor complaining about Firefox accessing some specific paths, those might be causing he issues you are seeing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1627239 Title: Web pages not rendering with e10s enabled and AppArmor profile in enforce mode Status in firefox package in Ubuntu: Confirmed Bug description: STR: 0. Enable enforce mode for the Firefox app-armor profile: sudo aa-enforce usr.bin.firefox 1. Open Firefox 49 with clean profile (or force-enable e10s as per https://wiki.mozilla.org/Electrolysis#Force_Enable and restart Firefox) 2. Go to any site What happens: The site loads but the content is rendered blank. The page is loaded properly since I can hover over (invisible) links and see the cursor change & the address to be shown in the bottom of the window. What should happen: The site is rendered properly. This is related to e10s and the default AppArmor profile shipped with firefox. See the attached screenshot for how the first-run page looks like with a clean profile, e10s and AppArmor enabled. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 49.0+build4-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BuildID: 20160920074044 Channel: Unavailable CurrentDesktop: Unity Date: Sat Sep 24 07:38:09 2016 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePlugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False RunningIncompatibleAddons: False SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1627239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1004256] Re: No Sound
this is also effecting me on 14.04 on a MythtV client. -- 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/1004256 Title: No Sound Status in alsa-driver package in Ubuntu: Invalid Bug description: sudo lshw -c sound *-multimedia:0 UNCLAIMED description: Audio device product: Wrestler HDMI Audio [Radeon HD 6250/6310] vendor: ATI Technologies Inc physical id: 1.1 bus info: pci@:00:01.1 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi bus_master cap_list configuration: latency=0 resources: memory:90444000-90447fff *-multimedia:1 UNCLAIMED description: Audio device product: SBx00 Azalia (Intel HDA) vendor: ATI Technologies Inc physical id: 14.2 bus info: pci@:00:14.2 version: 40 width: 64 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: latency=0 resources: memory:9044-90443fff ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx AlsaDevices: total 0 crw-rw 1 root audio 116, 1 2012-05-25 05:46 seq crw-rw 1 root audio 116, 33 2012-05-25 05:46 timer AplayDevices: aplay: device_list:240: no soundcards found... ApportVersion: 1.23-0ubuntu3 Architecture: amd64 ArecordDevices: arecord: device_list:240: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri May 25 07:37:53 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE10-BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.modalias: dmi:bvnAcer:bvrV1.12:bd06/08/2011:svnAcer:pnAspireOne522:pvrV1.12:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.12: dmi.product.name: Aspire One 522 dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1004256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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'
Not sure if I'm commenting on the right bug, since I'm using Unity not XFCE, but I get this problem on two computers with Intel cards (both Intel Corporation Centrino Ultimate-N 6300). It happens maybe 1/10 times after resuming from suspend. This is on Ubuntu 16.04; there were no problems back with 14.04. -- 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 1575447] Re: package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: triggers looping, abandoned
** Changed in: gnome-menus (Ubuntu) Assignee: (unassigned) => Paulo (paulo-dias) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1575447 Title: package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: Confirmed Bug description: Upgrading from Ubuntu 15.10 to 16.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gnome-menus 3.13.3-6ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Mon Apr 25 22:15:29 2016 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-12-27 (486 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1575447/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645357] Re: configuration file falied md5sum by DPKG verify
** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1645357 Title: configuration file falied md5sum by DPKG verify Status in chromium-browser package in Ubuntu: Invalid Bug description: ??5?? c /etc/default/chromium-browser I'm downloading the source packages and will purge the package. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1257 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-LVDS-1: edid-base64: AP///wAw5GoEAAAYAQSQIhN4CgX1lFhWkigeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAb4BNW9FAAFjAwIDUAWMIQAAAbAgAMR+oKPGQSFhxuAIk= dpms: Off modes: 1366x768 1366x768 enabled: disabled status: connected DRM.card0-VGA-1: edid-base64: AP///wAF43AjvwUYAQNoMx14Kt1Fo1VPoCcSUFS/7wDRwLMAlQCBgIFAgcABAQEBAjqAGHE4LUBYLEUA/R4RAAAe/QAyTB5TEQAKICAgICAg/AAyMzcwCiAgICAgICAg/wBCTEtFMTlBMDAwMTkxAFQ= dpms: On modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected Date: Mon Nov 28 10:18:11 2016 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2016-11-27 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Load-Avg-1min: 1.43 Load-Processes-Running-Percent: 0.1% MachineType: Acer Aspire 5820T ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=55cfdd2f-fa32-4bee-a9b7-374612827a15 ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM51_CP dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.25:bd03/16/2011:svnAcer:pnAspire5820T:pvrV1.25:rvnAcer:rnJM51_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 5820T dmi.product.version: V1.25 dmi.sys.vendor: Acer gconf-keys: /desktop/gnome/applications/browser/exec = b'\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1645357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645522] Re: [SRU] libopencc2: missing files cause librime fail to work
** Changed in: opencc (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to opencc in Ubuntu. https://bugs.launchpad.net/bugs/1645522 Title: [SRU] libopencc2: missing files cause librime fail to work Status in opencc package in Ubuntu: Fix Released Status in opencc source package in Yakkety: In Progress Status in opencc source package in Zesty: Fix Released Status in opencc package in Debian: Fix Released Bug description: [Impact] A list of missing files from opencc package makes opencc and libopencc2 does not work correctly for its consumers (fcitx-rime, ibus-rime). For example, when using fcitx-rime, fcitx would print the following error message onto stderr once the user tries to switch to input Simplified Chinese in Rime (Selecting *月拼音:简化字): [Test Case] After installing the updated package, fcitx-rime would not print error messages when user tries to switch to input Simplified Chinese in Rime. [Regression Potential] This updated package would introduce an additional binary call librime-data, which is actually a backport of version 1.0.4-2 in Debian and Ubuntu Zesty, potential of regression is low. == Description from Debian bug == In Debian unstable, when using fcitx-rime, fcitx would print the following error message onto stderr once the user tries to switch to input Simplified Chinese in rime (Selecting *月拼音:简化字): E0902 23:45:44.494884 6107 simplifier.cc:126] Error initializing opencc: t2s.json not found or not accessible. The t2s.json is supposed to be in /usr/share/opencc. To be concrete, the following missing files may be needed for opencc to work correctly: usr/share/ usr/share/opencc/ usr/share/opencc/HKVariants.ocd usr/share/opencc/HKVariantsPhrases.ocd usr/share/opencc/HKVariantsRev.ocd usr/share/opencc/HKVariantsRevPhrases.ocd usr/share/opencc/JPVariants.ocd usr/share/opencc/STCharacters.ocd usr/share/opencc/STPhrases.ocd usr/share/opencc/TSCharacters.ocd usr/share/opencc/TSPhrases.ocd usr/share/opencc/TWPhrases.ocd usr/share/opencc/TWPhrasesRev.ocd usr/share/opencc/TWVariants.ocd usr/share/opencc/TWVariantsRev.ocd usr/share/opencc/TWVariantsRevPhrases.ocd usr/share/opencc/hk2s.json usr/share/opencc/s2hk.json usr/share/opencc/s2t.json usr/share/opencc/s2tw.json usr/share/opencc/s2twp.json usr/share/opencc/t2hk.json usr/share/opencc/t2s.json usr/share/opencc/t2tw.json usr/share/opencc/tw2s.json usr/share/opencc/tw2sp.json However, they do not exist in any opencc-related packages (libopencc-dev, libopencc-dbg (Oh, BTW, please migrate to -dbgsym package), libopencc2 and opencc). The solution may be either include those files in a library package, or pack those files into another separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencc/+bug/1645522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645352] Re: No HDMI output after upgrade to 16.04!
Thanks Brian for the suggestion. Sorry, the only "package" that I can guess that it could be xorg. I have attempted to get help in the IRC chat at FreeNode, but instead I got just questions. I asked for assistance to identify a package name three times during a 30 minute session and got no help. So, I'm stuck. If Ubuntu 16.04 includes the Intel driver and, I've insured that the driver is correct and, loaded using the Intel Graphics Tool and, checked the status above ... I don't know what else to do. -- 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/1645352 Title: No HDMI output after upgrade to 16.04! Status in xorg package in Ubuntu: New Bug description: Running Ubuntu 16.04 64bit, 4.4.8 Kernel on an ASUS Trio with Intel® Haswell graphics card and using i915 driver. After upgrade there is no HDMI output to the external screen that I use daily. I did the following: - Upgraded to 4.4.8 Kernel hoping that the issue would be resolved. - Checked for other reports of this issue and followed advise to use NVIDIA 364 drivers. - Checked Intel for the most recent driver which is already packaged with 16.04; it is the i915 driver which is in use. - Used Intel driver update tool to ensure that update is correct. - Purchased a HDMI adapter to use mini-display port; works and reports HDMI1 is in use, but HDMI2 is not recognized (when monitor is plugged in to HDMI2) - Someone has assisted and has confirmed that there seems to be no hardware issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645522] Re: [SRU] libopencc2: missing files cause librime fail to work
** Description changed: + [Impact] + + A list of missing files from opencc package makes opencc and libopencc2 does not work correctly for its consumers (fcitx-rime, ibus-rime). For example, when using fcitx-rime, fcitx would print the + following error message onto stderr once the user tries to switch to + input Simplified Chinese in Rime (Selecting *月拼音:简化字): + + [Test Case] + + After installing the updated package, fcitx-rime would not print error + messages when user tries to switch to input Simplified Chinese in Rime. + + [Regression Potential] + + This updated package would introduce an additional binary call librime- + data, which is actually backported from version 1.0.4-2 in Debian and + Ubuntu Zesty, potential of regression is low. + + == Description from Debian bug == In Debian unstable, when using fcitx-rime, fcitx would print the following error message onto stderr once the user tries to switch to input Simplified Chinese in rime (Selecting *月拼音:简化字): E0902 23:45:44.494884 6107 simplifier.cc:126] Error initializing opencc: t2s.json not found or not accessible. The t2s.json is supposed to be in /usr/share/opencc. To be concrete, the following missing files may be needed for opencc to work correctly: usr/share/ usr/share/opencc/ usr/share/opencc/HKVariants.ocd usr/share/opencc/HKVariantsPhrases.ocd usr/share/opencc/HKVariantsRev.ocd usr/share/opencc/HKVariantsRevPhrases.ocd usr/share/opencc/JPVariants.ocd usr/share/opencc/STCharacters.ocd usr/share/opencc/STPhrases.ocd usr/share/opencc/TSCharacters.ocd usr/share/opencc/TSPhrases.ocd usr/share/opencc/TWPhrases.ocd usr/share/opencc/TWPhrasesRev.ocd usr/share/opencc/TWVariants.ocd usr/share/opencc/TWVariantsRev.ocd usr/share/opencc/TWVariantsRevPhrases.ocd usr/share/opencc/hk2s.json usr/share/opencc/s2hk.json usr/share/opencc/s2t.json usr/share/opencc/s2tw.json usr/share/opencc/s2twp.json usr/share/opencc/t2hk.json usr/share/opencc/t2s.json usr/share/opencc/t2tw.json usr/share/opencc/tw2s.json usr/share/opencc/tw2sp.json However, they do not exist in any opencc-related packages (libopencc-dev, libopencc-dbg (Oh, BTW, please migrate to -dbgsym package), libopencc2 and opencc). The solution may be either include those files in a library package, or pack those files into another separate package. ** Description changed: [Impact] A list of missing files from opencc package makes opencc and libopencc2 does not work correctly for its consumers (fcitx-rime, ibus-rime). For example, when using fcitx-rime, fcitx would print the following error message onto stderr once the user tries to switch to input Simplified Chinese in Rime (Selecting *月拼音:简化字): [Test Case] After installing the updated package, fcitx-rime would not print error messages when user tries to switch to input Simplified Chinese in Rime. [Regression Potential] This updated package would introduce an additional binary call librime- - data, which is actually backported from version 1.0.4-2 in Debian and + data, which is actually a backport of version 1.0.4-2 in Debian and Ubuntu Zesty, potential of regression is low. - == Description from Debian bug == In Debian unstable, when using fcitx-rime, fcitx would print the following error message onto stderr once the user tries to switch to input Simplified Chinese in rime (Selecting *月拼音:简化字): E0902 23:45:44.494884 6107 simplifier.cc:126] Error initializing opencc: t2s.json not found or not accessible. The t2s.json is supposed to be in /usr/share/opencc. To be concrete, the following missing files may be needed for opencc to work correctly: usr/share/ usr/share/opencc/ usr/share/opencc/HKVariants.ocd usr/share/opencc/HKVariantsPhrases.ocd usr/share/opencc/HKVariantsRev.ocd usr/share/opencc/HKVariantsRevPhrases.ocd usr/share/opencc/JPVariants.ocd usr/share/opencc/STCharacters.ocd usr/share/opencc/STPhrases.ocd usr/share/opencc/TSCharacters.ocd usr/share/opencc/TSPhrases.ocd usr/share/opencc/TWPhrases.ocd usr/share/opencc/TWPhrasesRev.ocd usr/share/opencc/TWVariants.ocd usr/share/opencc/TWVariantsRev.ocd usr/share/opencc/TWVariantsRevPhrases.ocd usr/share/opencc/hk2s.json usr/share/opencc/s2hk.json usr/share/opencc/s2t.json usr/share/opencc/s2tw.json usr/share/opencc/s2twp.json usr/share/opencc/t2hk.json usr/share/opencc/t2s.json usr/share/opencc/t2tw.json usr/share/opencc/tw2s.json usr/share/opencc/tw2sp.json However, they do not exist in any opencc-related packages (libopencc-dev, libopencc-dbg (Oh, BTW, please migrate to -dbgsym package), libopencc2 and opencc). The solution may be either include those files in a library package, or pack those files into another separate package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to opencc in Ubuntu.
[Desktop-packages] [Bug 1645522] Re: [SRU] libopencc2: missing files cause librime fail to work
** Changed in: opencc (Ubuntu Yakkety) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to opencc in Ubuntu. https://bugs.launchpad.net/bugs/1645522 Title: [SRU] libopencc2: missing files cause librime fail to work Status in opencc package in Ubuntu: Fix Released Status in opencc source package in Yakkety: In Progress Status in opencc source package in Zesty: Fix Released Status in opencc package in Debian: Fix Released Bug description: [Impact] A list of missing files from opencc package makes opencc and libopencc2 does not work correctly for its consumers (fcitx-rime, ibus-rime). For example, when using fcitx-rime, fcitx would print the following error message onto stderr once the user tries to switch to input Simplified Chinese in Rime (Selecting *月拼音:简化字): [Test Case] After installing the updated package, fcitx-rime would not print error messages when user tries to switch to input Simplified Chinese in Rime. [Regression Potential] This updated package would introduce an additional binary call librime-data, which is actually a backport of version 1.0.4-2 in Debian and Ubuntu Zesty, potential of regression is low. == Description from Debian bug == In Debian unstable, when using fcitx-rime, fcitx would print the following error message onto stderr once the user tries to switch to input Simplified Chinese in rime (Selecting *月拼音:简化字): E0902 23:45:44.494884 6107 simplifier.cc:126] Error initializing opencc: t2s.json not found or not accessible. The t2s.json is supposed to be in /usr/share/opencc. To be concrete, the following missing files may be needed for opencc to work correctly: usr/share/ usr/share/opencc/ usr/share/opencc/HKVariants.ocd usr/share/opencc/HKVariantsPhrases.ocd usr/share/opencc/HKVariantsRev.ocd usr/share/opencc/HKVariantsRevPhrases.ocd usr/share/opencc/JPVariants.ocd usr/share/opencc/STCharacters.ocd usr/share/opencc/STPhrases.ocd usr/share/opencc/TSCharacters.ocd usr/share/opencc/TSPhrases.ocd usr/share/opencc/TWPhrases.ocd usr/share/opencc/TWPhrasesRev.ocd usr/share/opencc/TWVariants.ocd usr/share/opencc/TWVariantsRev.ocd usr/share/opencc/TWVariantsRevPhrases.ocd usr/share/opencc/hk2s.json usr/share/opencc/s2hk.json usr/share/opencc/s2t.json usr/share/opencc/s2tw.json usr/share/opencc/s2twp.json usr/share/opencc/t2hk.json usr/share/opencc/t2s.json usr/share/opencc/t2tw.json usr/share/opencc/tw2s.json usr/share/opencc/tw2sp.json However, they do not exist in any opencc-related packages (libopencc-dev, libopencc-dbg (Oh, BTW, please migrate to -dbgsym package), libopencc2 and opencc). The solution may be either include those files in a library package, or pack those files into another separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencc/+bug/1645522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635460] Re: Magic spacebar only changes to next message
FWIW I patched the existing 3.22.1 release with the upstream patch 06dc3464c835e35fd8412a6aeb35d88056940351 and it fixes the problem. -- 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/1635460 Title: Magic spacebar only changes to next message Status in Evolution: Fix Released Status in evolution package in Ubuntu: New Bug description: According to here https://help.gnome.org/users/evolution/stable/mail- reading-keyboard-shortcuts.html.en When viewing messages, "If the message is more than one screen long, the Spacebar works as Page Down.". This no longer occurs in 16.10. It always goes to the next unread message. 16.04 worked as documented. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1635460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645522] [NEW] [SRU] libopencc2: missing files cause librime fail to work
Public bug reported: == Description from Debian bug == In Debian unstable, when using fcitx-rime, fcitx would print the following error message onto stderr once the user tries to switch to input Simplified Chinese in rime (Selecting *月拼音:简化字): E0902 23:45:44.494884 6107 simplifier.cc:126] Error initializing opencc: t2s.json not found or not accessible. The t2s.json is supposed to be in /usr/share/opencc. To be concrete, the following missing files may be needed for opencc to work correctly: usr/share/ usr/share/opencc/ usr/share/opencc/HKVariants.ocd usr/share/opencc/HKVariantsPhrases.ocd usr/share/opencc/HKVariantsRev.ocd usr/share/opencc/HKVariantsRevPhrases.ocd usr/share/opencc/JPVariants.ocd usr/share/opencc/STCharacters.ocd usr/share/opencc/STPhrases.ocd usr/share/opencc/TSCharacters.ocd usr/share/opencc/TSPhrases.ocd usr/share/opencc/TWPhrases.ocd usr/share/opencc/TWPhrasesRev.ocd usr/share/opencc/TWVariants.ocd usr/share/opencc/TWVariantsRev.ocd usr/share/opencc/TWVariantsRevPhrases.ocd usr/share/opencc/hk2s.json usr/share/opencc/s2hk.json usr/share/opencc/s2t.json usr/share/opencc/s2tw.json usr/share/opencc/s2twp.json usr/share/opencc/t2hk.json usr/share/opencc/t2s.json usr/share/opencc/t2tw.json usr/share/opencc/tw2s.json usr/share/opencc/tw2sp.json However, they do not exist in any opencc-related packages (libopencc-dev, libopencc-dbg (Oh, BTW, please migrate to -dbgsym package), libopencc2 and opencc). The solution may be either include those files in a library package, or pack those files into another separate package. ** Affects: opencc (Ubuntu) Importance: High Assignee: Aron Xu (happyaron) Status: Fix Released ** Affects: opencc (Ubuntu Yakkety) Importance: High Assignee: Aron Xu (happyaron) Status: Triaged ** Affects: opencc (Ubuntu Zesty) Importance: High Assignee: Aron Xu (happyaron) Status: Fix Released ** Affects: opencc (Debian) Importance: Unknown Status: Unknown ** Also affects: opencc (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: opencc (Ubuntu Zesty) Importance: High Assignee: Aron Xu (happyaron) Status: Triaged ** Changed in: opencc (Ubuntu Yakkety) Status: New => Triaged ** Changed in: opencc (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: opencc (Ubuntu Zesty) Status: Triaged => Fix Released ** Changed in: opencc (Ubuntu Yakkety) Assignee: (unassigned) => Aron Xu (happyaron) ** Summary changed: - libopencc2: missing files cause librime fail to work + [SRU] libopencc2: missing files cause librime fail to work ** Bug watch added: Debian Bug tracker #836395 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836395 ** Also affects: opencc (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836395 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to opencc in Ubuntu. https://bugs.launchpad.net/bugs/1645522 Title: [SRU] libopencc2: missing files cause librime fail to work Status in opencc package in Ubuntu: Fix Released Status in opencc source package in Yakkety: Triaged Status in opencc source package in Zesty: Fix Released Status in opencc package in Debian: Unknown Bug description: == Description from Debian bug == In Debian unstable, when using fcitx-rime, fcitx would print the following error message onto stderr once the user tries to switch to input Simplified Chinese in rime (Selecting *月拼音:简化字): E0902 23:45:44.494884 6107 simplifier.cc:126] Error initializing opencc: t2s.json not found or not accessible. The t2s.json is supposed to be in /usr/share/opencc. To be concrete, the following missing files may be needed for opencc to work correctly: usr/share/ usr/share/opencc/ usr/share/opencc/HKVariants.ocd usr/share/opencc/HKVariantsPhrases.ocd usr/share/opencc/HKVariantsRev.ocd usr/share/opencc/HKVariantsRevPhrases.ocd usr/share/opencc/JPVariants.ocd usr/share/opencc/STCharacters.ocd usr/share/opencc/STPhrases.ocd usr/share/opencc/TSCharacters.ocd usr/share/opencc/TSPhrases.ocd usr/share/opencc/TWPhrases.ocd usr/share/opencc/TWPhrasesRev.ocd usr/share/opencc/TWVariants.ocd usr/share/opencc/TWVariantsRev.ocd usr/share/opencc/TWVariantsRevPhrases.ocd usr/share/opencc/hk2s.json usr/share/opencc/s2hk.json usr/share/opencc/s2t.json usr/share/opencc/s2tw.json usr/share/opencc/s2twp.json usr/share/opencc/t2hk.json usr/share/opencc/t2s.json usr/share/opencc/t2tw.json usr/share/opencc/tw2s.json usr/share/opencc/tw2sp.json However, they do not exist in any opencc-related packages (libopencc-dev, libopencc-dbg (Oh, BTW, please migrate to -dbgsym package), libopencc2 and opencc). The solution may be either include those files in a library package, or pack those files into another separate package. To manage
[Desktop-packages] [Bug 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor
Alright, sounds like there's still work to do. Alberts, please log a new bug describing the remaining issue so it's more clearly still open :) Just run: ubuntu-bug nautilus Or if that fails then: https://bugs.launchpad.net/ubuntu/+source/nautilus/+filebug -- 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/1626935 Title: [yakkety] desktop is black and/or flickering after plugging in a second monitor Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Yakkety: Fix Released Bug description: [ Description ] Nautilus's wallpaper drawing doesn't respond to changes in monitor configuration. Instead of your wallpaper you see black. [ Fix ] Inside nautilus, the wallpaper widget connects to GTK's "monitors- changed" signal when it is constructed. It does this only once the widget is realized - a "realized" signal handler connects to "monitors-changed". In Yakkety, the "realized" signal handler is connected after the widget is already realized, meaning that the signal handler isn't called and we don't connect to the "monitors- changed" signal. The proposed fix remedies this by checking if we are realized and explicitly calling the signal handler if so. [ QA ] Have multiple monitors. Have only one of them connected. Log in. Plug in one monitor. If it's autoactivated, check you see your background on both monitors. If not, activate it ("Displays") and do the same. [ Regression potential ] I'm not sure why or where the order changed to make the widget be realized earlier, if it matters or if this was always buggy and we got lucky. I would guess a refactoring in Nautilus itself, and so the proposed fix is safe, but watch out for other weirdness. [ Original description ] Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Graphic chips: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] [10de:139b] (rev ff) Desktop wallpaper on extended display shows black background only, and the hdmi detection is very unstable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 23 05:30:30 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-09-20 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
Hui, could you please add relevant information about the regression potential of this bug fix, and anything else you feel is important for the SRU? I'm ok with it and will upload, but think a little more information is needed. ** Also affects: pulseaudio (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in pulseaudio package in Ubuntu: New Status in pulseaudio source package in Trusty: New Bug description: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645514] [NEW] multiple mouse pointer crashes
Public bug reported: Trying to setup multiple mouse pointers following the guide: https://wiki.archlinux.org/index.php/Multi-pointer_X Causes unity to crash and takes the user back to the login screen. The commands seem to work but when the user moves the second mouse, it instantly crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xinput 1.6.2-1 Uname: Linux 4.8.8-040808-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 29 11:37:21 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Hawaii PRO [Radeon R9 290] [1043:0466] InstallationDate: Installed on 2016-11-09 (19 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.8-040808-generic root=UUID=bdfb401a-08af-401a-a841-488821cf0261 ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd07/08/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Nov 29 11:36:27 2016 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: xinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1645514 Title: multiple mouse pointer crashes Status in xinput package in Ubuntu: New Bug description: Trying to setup multiple mouse pointers following the guide: https://wiki.archlinux.org/index.php/Multi-pointer_X Causes unity to crash and takes the user back to the login screen. The commands seem to work but when the user moves the second mouse, it instantly crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xinput 1.6.2-1 Uname: Linux 4.8.8-040808-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 29 11:37:21 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Hawaii PRO [Radeon R9 290] [1043:0466] InstallationDate: Installed on 2016-11-09 (19 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.8-040808-generic root=UUID=bdfb401a-08af-401a-a841-488821cf0261 ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2014 dmi.bios.vendor: American
[Desktop-packages] [Bug 1497806] Re: Mirrored display broken in Xubuntu
I use Ubuntu Studio 16.04 with XFCE4 4.12 and I had that problem too, but exploring the "Extend to the right" option and then returning to "Displays", "Mirror Displays" option is already accessible. Unfortunately, unplugging the another monitor and plugging it again, may recquire select first "Extend to the right" to make "Mirror Displays" accesible again. -- 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/1497806 Title: Mirrored display broken in Xubuntu Status in xorg package in Ubuntu: Invalid Bug description: Mirrored displays is not accessible (grayed out) when trying to activate this feature for multi-monitor support. I am not sure which specific package to nominate for this bug, but it seems to only be happening on systems with XFCE4 installed and running (Including Xubuntu, Mint, and Debian). It maybe an error with the package xfce4-display-settings, but I am not sure. This bug is being reported from: Description: Linux Mint 17.2 Rafaela Release: 17.2 Here is a copy of this Bug Report on Bugzilla: https://bugzilla.xfce.org/show_bug.cgi?id=11712 This bug report also has a picture attachment which is exactly what I am seeing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1497806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers
** Changed in: network-manager (Ubuntu) Assignee: Canonical Foundations Team (canonical-foundations) => Steve Langasek (vorlon) -- 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/1638836 Title: resolv.conf for resolved stub server should have a comment how to see the actual servers Status in network-manager package in Ubuntu: Triaged Status in resolvconf package in Ubuntu: In Progress Bug description: resolv.conf currently just has nameserver 127.0.0.53 with resolved (its local stub resolver). We should have an extra comment on top of that that says # systemd-resolved stub resolver; run "systemd-resolve --status" to see the actual name servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635460] Re: Magic spacebar only changes to next message
** Changed in: evolution Status: Unknown => Fix Released ** Changed in: evolution Importance: Unknown => Medium -- 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/1635460 Title: Magic spacebar only changes to next message Status in Evolution: Fix Released Status in evolution package in Ubuntu: New Bug description: According to here https://help.gnome.org/users/evolution/stable/mail- reading-keyboard-shortcuts.html.en When viewing messages, "If the message is more than one screen long, the Spacebar works as Page Down.". This no longer occurs in 16.10. It always goes to the next unread message. 16.04 worked as documented. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1635460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635460] Re: Magic spacebar only changes to next message
** Also affects: evolution via https://bugzilla.gnome.org/show_bug.cgi?id=771821 Importance: Unknown Status: Unknown -- 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/1635460 Title: Magic spacebar only changes to next message Status in Evolution: Fix Released Status in evolution package in Ubuntu: New Bug description: According to here https://help.gnome.org/users/evolution/stable/mail- reading-keyboard-shortcuts.html.en When viewing messages, "If the message is more than one screen long, the Spacebar works as Page Down.". This no longer occurs in 16.10. It always goes to the next unread message. 16.04 worked as documented. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1635460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1380480] Re: network disabled after suspend - resume
Michalje, Kristijian, note that this bug was opened before systemd was used as a system init. If you're still having trouble please file a new bug. Thanks. -- 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/1380480 Title: network disabled after suspend - resume Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Background: this started to happen after the upgrade to Utopic Beta 1 3) When I close the laptop's lid and open, the wifi should reconnect 4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I left-click on NM icon in notif area. However the context menu (right-click) has items "Enable networking" and "Enable Wi-Fi" both with checkmarks. Workarounds: switch off - on the physical switch on laptop OR two times go and select "Enable networking" in the NM context menu (after first time it removes checkmark and the "Enable Wi-Fi" item - visual feedback of being disabled). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu27 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 11 22:33:06 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-07-21 (447 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.10.1 dev wlan0 proto static 10.9.9.0/24 dev vboxnet0 proto kernel scope link src 10.9.9.1 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.239 metric 9 SourcePackage: network-manager UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-07-19T15:03:44.847279 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635460] Re: Magic spacebar only changes to next message
This is now fixed upstream in 3.22.2. https://bugzilla.gnome.org/show_bug.cgi?id=771821 Can we please update? ** Bug watch added: GNOME Bug Tracker #771821 https://bugzilla.gnome.org/show_bug.cgi?id=771821 -- 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/1635460 Title: Magic spacebar only changes to next message Status in Evolution: Unknown Status in evolution package in Ubuntu: New Bug description: According to here https://help.gnome.org/users/evolution/stable/mail- reading-keyboard-shortcuts.html.en When viewing messages, "If the message is more than one screen long, the Spacebar works as Page Down.". This no longer occurs in 16.10. It always goes to the next unread message. 16.04 worked as documented. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1635460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers
I have a fix for resolvconf here, but it's inaccurate for the desktop because Network Manager is still doing dnsmasq by default. Opening a task for NM. ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Status: New => Triaged ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- 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/1638836 Title: resolv.conf for resolved stub server should have a comment how to see the actual servers Status in network-manager package in Ubuntu: Triaged Status in resolvconf package in Ubuntu: In Progress Bug description: resolv.conf currently just has nameserver 127.0.0.53 with resolved (its local stub resolver). We should have an extra comment on top of that that says # systemd-resolved stub resolver; run "systemd-resolve --status" to see the actual name servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1380480] Re: network disabled after suspend - resume
Confirming the presence of this bug in 16.10 -- 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/1380480 Title: network disabled after suspend - resume Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Background: this started to happen after the upgrade to Utopic Beta 1 3) When I close the laptop's lid and open, the wifi should reconnect 4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I left-click on NM icon in notif area. However the context menu (right-click) has items "Enable networking" and "Enable Wi-Fi" both with checkmarks. Workarounds: switch off - on the physical switch on laptop OR two times go and select "Enable networking" in the NM context menu (after first time it removes checkmark and the "Enable Wi-Fi" item - visual feedback of being disabled). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu27 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 11 22:33:06 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-07-21 (447 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.10.1 dev wlan0 proto static 10.9.9.0/24 dev vboxnet0 proto kernel scope link src 10.9.9.1 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.239 metric 9 SourcePackage: network-manager UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-07-19T15:03:44.847279 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor
I disabled compositing and the flicker went away, but I now get some funky mouse trails that don't get cleaned up when crossing the edge between monitor 1 and monitor 2. -- 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/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in xorg package in Ubuntu: Incomplete Status in xorg package in Fedora: Unknown Bug description: My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I "Restore previous settings", after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573296] Re: obsolete conffiles not cleaned up on upgrade
** Changed in: pulseaudio (Ubuntu Xenial) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1573296 Title: obsolete conffiles not cleaned up on upgrade Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Bug description: Impact: When upgrading to xenial from earlier releases, some files are left on the user's system. They are not used, but may otherwise be mistaken for being used by the user if they are attempting to fix a problem. Regression potential: Low to none, as the relevant files are not used, and are being removed when the updated version of Pulseaudio is installed. These files are already removed in yakkety and later. Test case: When updating from trusty to xenial, one will note the presence of the below listed files on the system. Updating from pulseaudio in xenial or pulseaudio in trusty to what is in xenial-proposed shoudl delete the listed files. The /etc/init.d/pulseaudio script should also be unregistered. Original bug report: The following files are marked obsolete after the upgrade to 16.04: /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete Those files should be cleaned up and the sysv init script properly deregistered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1573296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths
We've added a patch to maliit to support this via the MALIIT_PLUGIN_PATH environment variable. ** Changed in: maliit-framework (Ubuntu) Status: New => Fix Released ** Changed in: maliit-framework (Ubuntu) Assignee: (unassigned) => Michael Sheldon (michael-sheldon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: In Progress Status in address-book-service package in Ubuntu: In Progress Status in dialer-app package in Ubuntu: In Progress Status in history-service package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: In Progress Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: In Progress Status in indicator-location package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: In Progress Status in indicator-network package in Ubuntu: In Progress Status in indicator-power package in Ubuntu: In Progress Status in indicator-session package in Ubuntu: In Progress Status in indicator-sound package in Ubuntu: In Progress Status in indicator-transfer package in Ubuntu: In Progress Status in maliit-framework package in Ubuntu: Fix Released Status in mediascanner2 package in Ubuntu: In Progress Status in messaging-app package in Ubuntu: In Progress Status in pay-service package in Ubuntu: New Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: In Progress Status in ubuntu-keyboard package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: In Progress Status in unity-scope-scopes package in Ubuntu: Won't Fix Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 681617] Re: pptp stops receiving packets when bandwidth spike
@asavah, you wrote "It's a SHAME that such a good fix is not yet in the "official" package." I'm laughing like anything. I'm the upstream and I make the official package, yet this fix has NEVER come to me. I just happen to notice it now, here. Next time, make sure you talk to upstream before complaining about upstream. ;-) Merged as df45680 after fixing indentation. Thanks for the patch. https://sourceforge.net/p/pptpclient/git/ci/df4568002b67de068bbcf16bbdbca800986f325b/ Ruslan, mail me at qu...@laptop.org if you want your e-mail address added to AUTHORS; I'd normally do it, but it wasn't in the diff. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pptp-linux in Ubuntu. https://bugs.launchpad.net/bugs/681617 Title: pptp stops receiving packets when bandwidth spike Status in pptp-linux package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: Binary package hint: pptp-linux I've had this problem since long ago, when downloading at high speed (ubuntu images from my uni's network and similar) my network connection would become unresponsive, and I had to reconnect. This hit me real hard today, as it kept happening while I was browsing a single youtube clip. My dorm uses PPTP to connect to the net, and we have a fairly juicy line (~100mbps). I've researched a bit, and tried to adjust the MISSING_WINDOW in pqueue.h to 6000 from 300 (per [1] and [2]), and I think this fixed my problem. I guess this could've been fixed upstream already, but still would be nice to have this backported if possible. If nothing else, this bug- report might help someone else with the same problem. [1]http://blog.gmane.org/gmane.comp.misc.pptpclient.devel/month=20100801 [2]https://bugzilla.novell.com/show_bug.cgi?id=628537 someone else with the same problem: http://ubuntuforums.org/showthread.php?p=10163284#post10163284 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: pptp-linux 1.7.2-4 ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Thu Nov 25 23:42:53 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: pptp-linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pptp-linux/+bug/681617/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637583] Re: PWG Raster printing on IPP Everywhere printers not working correctly
This bug was fixed in the package cups-filters - 1.11.4-0ubuntu2.1 --- cups-filters (1.11.4-0ubuntu2.1) yakkety-proposed; urgency=medium * cups-browsed, gstoraster, pdftoraster: Assorted fixes to make IPP Everywhere printers correctly working (LP: #1637583): - MIME conversion rules for PWG Raster output using gstoraster and pdftoraster. - Let gstoraster and pdftoraster output PWG Raster instead of CUPS Raster for IPP Everywhere printers. - Let pdftoraster generate correct PWG Raster (full page bitmaps without removal of unprintable borders). - Let pdftopdf log the pages of PWG Raster jobs in page_log. - Let cups-browsed also auto-create queues only for IPP Everywhere printers and not for legacy IPP printers. -- Till KamppeterMon, 14 Nov 2016 19:00:00 -0200 ** Changed in: cups-filters (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1637583 Title: PWG Raster printing on IPP Everywhere printers not working correctly Status in cups-filters package in Ubuntu: Fix Released Status in ghostscript package in Ubuntu: Fix Released Status in cups-filters source package in Yakkety: Fix Released Status in ghostscript source package in Yakkety: Fix Released Bug description: Printers conforming to the new IPP Everywhere standard (of the Printing Working Group, PWG, http://www.pwg.org/) are starting to come onto the market. These printers are capable to inform the clients computers about all their capabilities (paper sizes, resolutions, finishers, ...) via IPP and understand known standard page description languages (always PWG Raster, but can also understand PostScript, PDF, JPEG, and/or PCL). So no drivers for these printers are needed. With CUPS, cups-filters, and one of Ghostscript, Poppler, or MuPDF they are fully supported. Yakkety is intended to support them, but getting my hands on an IPP Everywhere printer (which takes PWG Raster as inpout format) I have found some issues: - CUPS selects a filter chain using MuPDF but MuPDF is not installed by default. - In contrary to CUPS Raster, PWG Raster contains a full page bitmap of the page, including the unprintable margins. Margins in the header are set to zero. - Filter chains could send CUPS Raster instead of PWG Raster. - Printed pages are not logged in /var/log/cups/page_log. All these issued are fixed in cups-filters 1.11.5 and in a patch to Ghostscript (already upstream). This bug report is for an SRU for Yakkety to fix the issues also there. [Impact] With "CreateIPPPrinterQueues Yes" set in /etc/cups/cups-browsed.conf IPP Everywhere printers are discovered in the network and automatically set up but they only print if mutool (package mupdf- tools) is installed. This leaves users with non-working print queues. [Testcase] Set "CreateIPPPrinterQueues Yes" in /etc/cups/cups-browsed.conf and restart cups-browsed. If an IPP Everywhere printer is in the network, it will be detected but you cannot print on the auto-generated queue. After installing the mupdf-tools package printing works. With the fixed cups-filters and Ghostscript installed mupdf-tools is not needed. Jobs get filtered via Ghostscript and printing on the IPP Everywhere printer works. [Regression Potential] Small, as changes in the filter chain only happen if PWG Raster is involved and this happens only with IPP Everywhere printers. Only the output of PWG Raster and not of any other format is modified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1637583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637583] Re: PWG Raster printing on IPP Everywhere printers not working correctly
This bug was fixed in the package ghostscript - 9.19~dfsg+1-0ubuntu6.1 --- ghostscript (9.19~dfsg+1-0ubuntu6.1) yakkety-proposed; urgency=medium * debian/patches/020161028~0726780_gdevcups-pwgraster-bitmap-always-without-margins.patch: "cups" output device: When creating PWG Raster output, always output the bitmap of the full page, ignoring any unprintable margins suggested by the PPD file (LP: #1637583). -- Till KamppeterMon, 14 Nov 2016 17:37:00 -0200 ** Changed in: ghostscript (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1637583 Title: PWG Raster printing on IPP Everywhere printers not working correctly Status in cups-filters package in Ubuntu: Fix Released Status in ghostscript package in Ubuntu: Fix Released Status in cups-filters source package in Yakkety: Fix Released Status in ghostscript source package in Yakkety: Fix Released Bug description: Printers conforming to the new IPP Everywhere standard (of the Printing Working Group, PWG, http://www.pwg.org/) are starting to come onto the market. These printers are capable to inform the clients computers about all their capabilities (paper sizes, resolutions, finishers, ...) via IPP and understand known standard page description languages (always PWG Raster, but can also understand PostScript, PDF, JPEG, and/or PCL). So no drivers for these printers are needed. With CUPS, cups-filters, and one of Ghostscript, Poppler, or MuPDF they are fully supported. Yakkety is intended to support them, but getting my hands on an IPP Everywhere printer (which takes PWG Raster as inpout format) I have found some issues: - CUPS selects a filter chain using MuPDF but MuPDF is not installed by default. - In contrary to CUPS Raster, PWG Raster contains a full page bitmap of the page, including the unprintable margins. Margins in the header are set to zero. - Filter chains could send CUPS Raster instead of PWG Raster. - Printed pages are not logged in /var/log/cups/page_log. All these issued are fixed in cups-filters 1.11.5 and in a patch to Ghostscript (already upstream). This bug report is for an SRU for Yakkety to fix the issues also there. [Impact] With "CreateIPPPrinterQueues Yes" set in /etc/cups/cups-browsed.conf IPP Everywhere printers are discovered in the network and automatically set up but they only print if mutool (package mupdf- tools) is installed. This leaves users with non-working print queues. [Testcase] Set "CreateIPPPrinterQueues Yes" in /etc/cups/cups-browsed.conf and restart cups-browsed. If an IPP Everywhere printer is in the network, it will be detected but you cannot print on the auto-generated queue. After installing the mupdf-tools package printing works. With the fixed cups-filters and Ghostscript installed mupdf-tools is not needed. Jobs get filtered via Ghostscript and printing on the IPP Everywhere printer works. [Regression Potential] Small, as changes in the filter chain only happen if PWG Raster is involved and this happens only with IPP Everywhere printers. Only the output of PWG Raster and not of any other format is modified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1637583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637583] Update Released
The verification of the Stable Release Update for cups-filters has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1637583 Title: PWG Raster printing on IPP Everywhere printers not working correctly Status in cups-filters package in Ubuntu: Fix Released Status in ghostscript package in Ubuntu: Fix Released Status in cups-filters source package in Yakkety: Fix Committed Status in ghostscript source package in Yakkety: Fix Released Bug description: Printers conforming to the new IPP Everywhere standard (of the Printing Working Group, PWG, http://www.pwg.org/) are starting to come onto the market. These printers are capable to inform the clients computers about all their capabilities (paper sizes, resolutions, finishers, ...) via IPP and understand known standard page description languages (always PWG Raster, but can also understand PostScript, PDF, JPEG, and/or PCL). So no drivers for these printers are needed. With CUPS, cups-filters, and one of Ghostscript, Poppler, or MuPDF they are fully supported. Yakkety is intended to support them, but getting my hands on an IPP Everywhere printer (which takes PWG Raster as inpout format) I have found some issues: - CUPS selects a filter chain using MuPDF but MuPDF is not installed by default. - In contrary to CUPS Raster, PWG Raster contains a full page bitmap of the page, including the unprintable margins. Margins in the header are set to zero. - Filter chains could send CUPS Raster instead of PWG Raster. - Printed pages are not logged in /var/log/cups/page_log. All these issued are fixed in cups-filters 1.11.5 and in a patch to Ghostscript (already upstream). This bug report is for an SRU for Yakkety to fix the issues also there. [Impact] With "CreateIPPPrinterQueues Yes" set in /etc/cups/cups-browsed.conf IPP Everywhere printers are discovered in the network and automatically set up but they only print if mutool (package mupdf- tools) is installed. This leaves users with non-working print queues. [Testcase] Set "CreateIPPPrinterQueues Yes" in /etc/cups/cups-browsed.conf and restart cups-browsed. If an IPP Everywhere printer is in the network, it will be detected but you cannot print on the auto-generated queue. After installing the mupdf-tools package printing works. With the fixed cups-filters and Ghostscript installed mupdf-tools is not needed. Jobs get filtered via Ghostscript and printing on the IPP Everywhere printer works. [Regression Potential] Small, as changes in the filter chain only happen if PWG Raster is involved and this happens only with IPP Everywhere printers. Only the output of PWG Raster and not of any other format is modified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1637583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616943] Update Released
The verification of the Stable Release Update for gnome-software has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1616943 Title: Can't auth against U1 in g-s Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in snapd-glib source package in Xenial: Fix Committed Status in gnome-software source package in Yakkety: Fix Released Bug description: [Impact] Authentication using Ubuntu One credentials to install/remove snaps always fails. This is due to a behaviour change in snapd (no longer accepts login requests from non-root users). Existing credentials continue to work. [Test Case] 1. Delete any existing credentials by deleting passwords marked "com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse. 2. Start GNOME Software 3. Search for a snap (e.g. "moon-buggy") 4. Install Snap 5. Enter Ubuntu One credentials when prompted Observed result: Dialog says "Incorrect email or password". Expected result: Authentication completes and the snap is installed. [Regression Potential] The solution is to use a new D-Bus service (snapd-login-service) and new library (snapd-glib) to get the Macaroon from snapd. This has some risk of introducing new bugs. The change is minimised (other snapd code paths unchanged) and the alternative is login to be impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock
** Tags removed: verification-done ** Tags added: verification-done-yakkety verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576424 Title: Gimp crashes with text tool & caps lock Status in GTK+: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in gtk+2.0 source package in Xenial: Fix Committed Status in gtk+2.0 source package in Yakkety: Fix Released Bug description: [Impact] Gimp crashes with a segfault when I use caps lock while renaming a layer. It is possible Caps lock causes crashes in other events also. [Test Case] Steps to reproduce: 1. Open a new blank gimp document 2. select the text tool 3. type a couple of words of text (gimp will create a text layer above the background layer) 4. with the text tool still selected, click on the background layer (just to move away from the text layer) 5. now double click on the text layer to rename the layer (layer name gets highlighted) 6. press the caps lock key 7. click on the background layer again (without renaming or doing anything to the text layer) Now repeat steps 5 and 6. Gimp crashes. [Regression Potential] None expected. The patch used has been taken from upstream development. https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad Packages for Xenial and Yakkety have been built in a PPA and regression tested. [ Other Info ] I can force this to happen every time I launch Gimp. Rebooting makes no difference. It seems to be the second time I press caps lock that forces the crash. I tried launching Gimp with caps lock on vs caps lock off, but I don't believe it made any difference. I can force a crash every time following the above sequence. I deleted my gimp preferences folder then rebooted for good measure. Gimp created a fresh preferences folder, but it hasn't solved the problem. I was originally in single window mode, but the new preferences folder put me back to multi window, but it crashes either way. I ran dmesg | tail after the crash and got the following line: gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0 error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000] I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver (available from the Additional Drivers tab). In that same tab, I also have enabled Processor microcode firmware for Intel CPUs. Terminal tells me Gimp version is 2.8.16-1ubuntu1 I'm not very experienced with bug reporting and not sure what other information I need to supply. Gimp was absolutely rock solid on this machine with 15.10, so it may be a Xubuntu issue. Hope someone can take a look at this. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1576424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock
This bug was fixed in the package gtk+2.0 - 2.24.30-4ubuntu3 --- gtk+2.0 (2.24.30-4ubuntu3) yakkety; urgency=medium * debian/patches/lp1576424-explicitly-disconnect-keymap-signals.patch - GtkEntry: Explicitly disconnect keymap signals. (LP: #1576424) -- Martin WimpressTue, 04 Oct 2016 17:07:26 +0100 ** Changed in: gtk+2.0 (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576424 Title: Gimp crashes with text tool & caps lock Status in GTK+: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in gtk+2.0 source package in Xenial: Fix Committed Status in gtk+2.0 source package in Yakkety: Fix Released Bug description: [Impact] Gimp crashes with a segfault when I use caps lock while renaming a layer. It is possible Caps lock causes crashes in other events also. [Test Case] Steps to reproduce: 1. Open a new blank gimp document 2. select the text tool 3. type a couple of words of text (gimp will create a text layer above the background layer) 4. with the text tool still selected, click on the background layer (just to move away from the text layer) 5. now double click on the text layer to rename the layer (layer name gets highlighted) 6. press the caps lock key 7. click on the background layer again (without renaming or doing anything to the text layer) Now repeat steps 5 and 6. Gimp crashes. [Regression Potential] None expected. The patch used has been taken from upstream development. https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad Packages for Xenial and Yakkety have been built in a PPA and regression tested. [ Other Info ] I can force this to happen every time I launch Gimp. Rebooting makes no difference. It seems to be the second time I press caps lock that forces the crash. I tried launching Gimp with caps lock on vs caps lock off, but I don't believe it made any difference. I can force a crash every time following the above sequence. I deleted my gimp preferences folder then rebooted for good measure. Gimp created a fresh preferences folder, but it hasn't solved the problem. I was originally in single window mode, but the new preferences folder put me back to multi window, but it crashes either way. I ran dmesg | tail after the crash and got the following line: gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0 error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000] I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver (available from the Additional Drivers tab). In that same tab, I also have enabled Processor microcode firmware for Intel CPUs. Terminal tells me Gimp version is 2.8.16-1ubuntu1 I'm not very experienced with bug reporting and not sure what other information I need to supply. Gimp was absolutely rock solid on this machine with 15.10, so it may be a Xubuntu issue. Hope someone can take a look at this. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1576424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616943] Re: Can't auth against U1 in g-s
This bug was fixed in the package gnome-software - 3.20.1+git20161013.0 .d77d6cf-0ubuntu2 --- gnome-software (3.20.1+git20161013.0.d77d6cf-0ubuntu2) yakkety; urgency=medium * debian/control{,.in}: Build-Depend on libsnapd-glib-dev, to successfully build the Snap plugin. * debian/rules: Pass --enable-snap, so that configure bails out if the Snap plugin won't be built. gnome-software (3.20.1+git20161013.0.d77d6cf-0ubuntu1) yakkety; urgency=medium * New upstream snapshot from the wip/ubuntu branch at git://git.gnome.org/gnome-software. - Use snapd-glib to perform snapd login. This fixes non-root access being removed in snapd. (LP: #1616943) -- Iain LaneThu, 13 Oct 2016 16:52:55 +0100 ** Changed in: gnome-software (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- 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/1616943 Title: Can't auth against U1 in g-s Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in snapd-glib source package in Xenial: Fix Committed Status in gnome-software source package in Yakkety: Fix Released Bug description: [Impact] Authentication using Ubuntu One credentials to install/remove snaps always fails. This is due to a behaviour change in snapd (no longer accepts login requests from non-root users). Existing credentials continue to work. [Test Case] 1. Delete any existing credentials by deleting passwords marked "com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse. 2. Start GNOME Software 3. Search for a snap (e.g. "moon-buggy") 4. Install Snap 5. Enter Ubuntu One credentials when prompted Observed result: Dialog says "Incorrect email or password". Expected result: Authentication completes and the snap is installed. [Regression Potential] The solution is to use a new D-Bus service (snapd-login-service) and new library (snapd-glib) to get the Macaroon from snapd. This has some risk of introducing new bugs. The change is minimised (other snapd code paths unchanged) and the alternative is login to be impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645491] [NEW] Error in Swedish name translation in thunderbird.desktop
Public bug reported: Hi, I'm involved in translating a lot of GNOME, Ubuntu and other FOSS- packages to Swedish and as a coordinator for the Swedish Ubuntu translations. I noticed that the Swedish translation for name ( see file thunderbird.desktop in the thunderbird source) has an error - instead of "Name[sv]=E-postklienten Thunderbird" it should be "Name[sv]=Thunderbird e-postklient" to be in line with most other FOSS-translations to Swedish, and to be sorted in the correct order in menus etc. If someone could correct this error I'd be grateful (and please take it upstreams). ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, I'm involved in translating a lot of GNOME, Ubuntu and other FOSS- packages to Swedish and as a coordinator for the Swedish Ubuntu translations. I noticed that the Swedish translation for name ( see file thunderbird.desktop in the thunderbird source) has an error - instead of "Name[sv]=E-postklienten Thunderbird" it should be "Name[sv]=Thunderbird e-postklient" - to be in line with most other FOSS-translations to Swedish, and to be sorted in - the correct order in menues etc. + to be in line with most other FOSS-translations to Swedish, and to be + sorted in the correct order in menus etc. If someone could correct this error I'd be grateful, and please take it upstreams. ** Description changed: Hi, I'm involved in translating a lot of GNOME, Ubuntu and other FOSS- packages to Swedish and as a coordinator for the Swedish Ubuntu translations. I noticed that the Swedish translation for name ( see file thunderbird.desktop in the thunderbird source) has an error - instead of "Name[sv]=E-postklienten Thunderbird" it should be "Name[sv]=Thunderbird e-postklient" to be in line with most other FOSS-translations to Swedish, and to be sorted in the correct order in menus etc. - If someone could correct this error I'd be grateful, and please take it - upstreams. + If someone could correct this error I'd be grateful (and please take it + upstreams). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1645491 Title: Error in Swedish name translation in thunderbird.desktop Status in thunderbird package in Ubuntu: New Bug description: Hi, I'm involved in translating a lot of GNOME, Ubuntu and other FOSS- packages to Swedish and as a coordinator for the Swedish Ubuntu translations. I noticed that the Swedish translation for name ( see file thunderbird.desktop in the thunderbird source) has an error - instead of "Name[sv]=E-postklienten Thunderbird" it should be "Name[sv]=Thunderbird e-postklient" to be in line with most other FOSS-translations to Swedish, and to be sorted in the correct order in menus etc. If someone could correct this error I'd be grateful (and please take it upstreams). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1645491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645485] [NEW] very old display driver bug?
Public bug reported: the most bothersome, most notable, and most curious symptom of this bug is the absolute degree to which the display locks up. xclock's seconds are no longer changing, the mouse cursor won't move, and even ctl-alt-F1 does nothing. meanwhile mplayer, playing in a hidden tmux window, is still playing merrily along. i logged in via sshd and copied this from htop: 0 [|100.0%] Tasks: 68; 3 running 1 [|| 1.3%] Load average: 1.00 0.91 0.53 Mem[|973M/1.91G] Time: 14:26:17 Swp[ 0K/1.86G] PID START USER VIRT RES NI CPU% TIME+ S Command 1714 12:50 g 1713M 789M 0 0.0 6:37.92 S /usr/lib/firefox/firefox 2368 14:07 g 661M 57252 0 0.0 0:03.33 S /usr/bin/python3 /usr/bin/blueman-manager 794 12:49 root 269M 54988 0 99.3 10:12.88 R /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/ 2385 14:07 g 583M 53524 0 0.0 0:00.39 S /usr/bin/python3 /usr/bin/blueman-applet 2397 14:07 g 555M 42968 0 0.0 0:10.68 S pavucontrol 1926 12:57 g 282M 37752 0 0.7 0:02.46 S /usr/lib/firefox/plugin-container /opt/google/talkp 1933 12:57 g 512M 36404 0 0.0 0:02.96 S /opt/google/talkplugin/GoogleTalkPlugin 2403 14:07 g 823M 30352 0 0.0 0:03.52 S mplayer -ao pulse -af channels=2 -framedrop -msgcol F1Help F2Setup F3SearchF4FilterF5Tree F6SortByF7Nice -F8Nice +F9Kill F10Quit ps also attached, taken before killing xorg. i've filed this under xorg merely because xorg is the one stuck eating all the CPU. i really suspect the display driver, and don't know how to find or identify that. i much more commonly saw these very same symptoms when i used to run xscreensaver. i stopped running xscreensaver just to stop beating my head against that wall. but many years and many releases later, it looks like this display driver bug is still lurking around. there was hardly anything running when this froze. i already mentioned mplayer (sound only) and tmux, twm's the window manager, firefox was running but iconized and idle tho running gmail and the googletalk plugin, not that i suspect any of them in any way. xterm was occupying most of the screen, showing tmux, and idle. the ones i'd more suspect would be xclock & pavucontrol. pavucontrol was hidden but busily showing it's audio level bar, xclock was visible and displaying the time of day including seconds, so the most likely one to have tripped a display driver bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 28 14:36:38 2016 InstallationDate: Installed on 2016-10-15 (43 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "ps taken before xorg killed" https://bugs.launchpad.net/bugs/1645485/+attachment/4784403/+files/ps -- 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/1645485 Title: very old display driver bug? Status in xorg package in Ubuntu: New Bug description: the most bothersome, most notable, and most curious symptom of this bug is the absolute degree to which the display locks up. xclock's seconds are no longer changing, the mouse cursor won't move, and even ctl-alt-F1 does nothing. meanwhile mplayer, playing in a hidden tmux window, is still playing merrily along. i logged in via sshd and copied this from htop: 0 [|100.0%] Tasks: 68; 3 running 1 [|| 1.3%] Load average: 1.00 0.91 0.53 Mem[|973M/1.91G] Time: 14:26:17 Swp[ 0K/1.86G] PID START USER VIRT RES NI CPU% TIME+ S Command 1714 12:50 g 1713M 789M 0 0.0 6:37.92 S /usr/lib/firefox/firefox 2368 14:07 g 661M 57252 0 0.0 0:03.33 S /usr/bin/python3 /usr/bin/blueman-manager 794 12:49 root 269M 54988 0 99.3 10:12.88 R /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/ 2385 14:07 g 583M 53524 0 0.0 0:00.39 S /usr/bin/python3 /usr/bin/blueman-applet 2397 14:07 g 555M 42968 0 0.0 0:10.68 S pavucontrol 1926 12:57 g 282M 37752 0 0.7 0:02.46 S /usr/lib/firefox/plugin-container /opt/google/talkp 1933 12:57 g 512M 36404 0 0.0 0:02.96 S /opt/google/talkplugin/GoogleTalkPlugin 2403 14:07 g
[Desktop-packages] [Bug 1505025] Re: Missing functional
** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete ** Changed in: gnome-terminal (Ubuntu) Status: Incomplete => Fix Released ** Changed in: gnome-terminal (Ubuntu) Status: Fix Released => 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/1505025 Title: Missing functional Status in gnome-terminal package in Ubuntu: Invalid Bug description: 1. Open terminal 2. In top menu choose "Edit" > "Profile Preferences" 3. Choose "Colors" tab. 4. Uncheck "Use colors from system theme", in "Palette" section change "build-in schemes" or color palette. Expected result some color or scheme changing (there is no info about this feature in terminal help) Actual result nothing happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1505025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths
** Also affects: maliit-framework (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: In Progress Status in address-book-service package in Ubuntu: In Progress Status in dialer-app package in Ubuntu: In Progress Status in history-service package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: In Progress Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: In Progress Status in indicator-location package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: In Progress Status in indicator-network package in Ubuntu: In Progress Status in indicator-power package in Ubuntu: In Progress Status in indicator-session package in Ubuntu: In Progress Status in indicator-sound package in Ubuntu: In Progress Status in indicator-transfer package in Ubuntu: In Progress Status in maliit-framework package in Ubuntu: New Status in mediascanner2 package in Ubuntu: In Progress Status in messaging-app package in Ubuntu: In Progress Status in pay-service package in Ubuntu: New Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: In Progress Status in ubuntu-keyboard package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: In Progress Status in unity-scope-scopes package in Ubuntu: Won't Fix Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1610517] Re: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping
A number of errors of this type occurred during upgrade to 16.4.1 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1610517 Title: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping Status in hicolor-icon-theme package in Ubuntu: Confirmed Bug description: While running a `do-release-upgrade` from Xubuntu 15.10 to 16.04 something like a post-install hook apparently triggered looping. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10 Uname: Linux 4.2.0-38-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sat Aug 6 11:48:42 2016 Dependencies: DuplicateSignature: package:hicolor-icon-theme:0.15-0ubuntu1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-02-24 (893 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-08-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1610517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1610517] Re: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hicolor-icon-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1610517 Title: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping Status in hicolor-icon-theme package in Ubuntu: Confirmed Bug description: While running a `do-release-upgrade` from Xubuntu 15.10 to 16.04 something like a post-install hook apparently triggered looping. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10 Uname: Linux 4.2.0-38-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sat Aug 6 11:48:42 2016 Dependencies: DuplicateSignature: package:hicolor-icon-theme:0.15-0ubuntu1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-02-24 (893 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-08-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1610517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1643901] Re: flxdec security update tracking bug
** No longer affects: gst-plugins-good0.10 (Ubuntu Yakkety) ** No longer affects: gst-plugins-good0.10 (Ubuntu Zesty) ** Changed in: gst-plugins-good0.10 (Ubuntu) Importance: Undecided => Medium ** Changed in: gst-plugins-good0.10 (Ubuntu) Status: Invalid => Fix Released ** No longer affects: gst-plugins-good1.0 (Ubuntu Precise) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1643901 Title: flxdec security update tracking bug Status in gst-plugins-good0.10 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Confirmed Status in gst-plugins-good0.10 source package in Precise: Fix Released Status in gst-plugins-good0.10 source package in Trusty: Fix Released Status in gst-plugins-good1.0 source package in Trusty: Fix Released Status in gst-plugins-good0.10 source package in Xenial: Fix Released Status in gst-plugins-good1.0 source package in Xenial: Fix Released Status in gst-plugins-good1.0 source package in Yakkety: Fix Released Status in gst-plugins-good1.0 source package in Zesty: Confirmed Bug description: This bug is to track the security update to fix the flxdec out-of- bounds write. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1643901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
The Debian bug is about the warning message not being actionable when it appears, it does *not* appear at Debian under normal circumstances, hence it is a completely different issue (and one that isn't easily solvable). ** Changed in: appstream (Debian) Importance: Unknown => Undecided ** Changed in: appstream (Debian) Status: Unknown => New ** Changed in: appstream (Debian) Remote watch: Debian Bug tracker #820774 => None ** Package changed: appstream (Debian) => debian ** Changed in: debian Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in Debian: Invalid Bug description: [Impact] * The recent update of the Ubuntu asgen instance yielded it to generate modern metadata. While we could tell asgen to generate old- style metadata, fixing appstream is the better idea, since we already applied similar patches to appstream-glib (and having this package hold back updates is a bad idea). Currently, the unknown metadata is considered to be broken by appstream and it displays a warning about that issue during an `apt update` * The attached patch includes a second change to make AppStream more robust against broken YAML data, ensuring LP #1579712 can not be triggered on purpose or due to broken disks creating damaged YAML structure. [Test Case 1] * apt update * Check for errors about metadata being ignored [Test Case 2] * appstreamcli refresh --force * Check for errors about metadata being ignored * Check if we ignored data that should be present (search for it via `appstreamcli search `) * Run `appstreamcli status` and see if we still have information on the same amount of components as prior to the update. [Regression Potential] * Medium; The works case would be KDE Discover and GNOME Software loosing information on available software, but this risk is very low and the patch to fix this bug is very simple and has almost no regression potential. The YAML parser fix patch is a bit more complex, but should have no sideeffects. [Original report] Periodically I get emails from a machine with the subject: Cronif [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi And a body of: AppStream cache update completed, but some metadata was ignored due to errors. I have a machine monitored by Munin. One of the plugins used on that machine is /etc/munin/plugins/apt which periodically counts the number of packets that can be upgraded. This is achieved by a crontab entry installed from the package which looks like this: # # cron-jobs for munin-node # MAILTO=root # If the APT plugin is enabled, update packages databases approx. once # an hour (12 invokations an hour, 1 in 12 chance that the update will # happen), but ensure that there will never be more than two hour (7200 # seconds) interval between updates.. */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi For many months everything has been running smoothly. On the 23rd November 2016 I started getting the "AppStream cache update completed, but some metadata was ignored due to errors." messages at a rate of about ten a day. I did a quick Google search which turned up a handful of bugs from earlier this year, such as Bug1575248. That is marked as Fixed Released though, so I am raising this new bug. If there are any further diagnostic details I can provide, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 09:57:18 2016 InstallationDate: Installed on 2013-05-08 (1295 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508) JournalErrors: -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 GMT. -- Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SourcePackage: appstream UpgradeStatus: Upgraded to xenial on
[Desktop-packages] [Bug 1627239] Re: Web pages not rendering with e10s enabled and AppArmor profile in enforce mode
Hi Sami! The proposed workaround does not work for me. Only setting apparmor to complain mode allows shm access and renders websites... Any hints? Thanks Martin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1627239 Title: Web pages not rendering with e10s enabled and AppArmor profile in enforce mode Status in firefox package in Ubuntu: Confirmed Bug description: STR: 0. Enable enforce mode for the Firefox app-armor profile: sudo aa-enforce usr.bin.firefox 1. Open Firefox 49 with clean profile (or force-enable e10s as per https://wiki.mozilla.org/Electrolysis#Force_Enable and restart Firefox) 2. Go to any site What happens: The site loads but the content is rendered blank. The page is loaded properly since I can hover over (invisible) links and see the cursor change & the address to be shown in the bottom of the window. What should happen: The site is rendered properly. This is related to e10s and the default AppArmor profile shipped with firefox. See the attached screenshot for how the first-run page looks like with a clean profile, e10s and AppArmor enabled. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 49.0+build4-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BuildID: 20160920074044 Channel: Unavailable CurrentDesktop: Unity Date: Sat Sep 24 07:38:09 2016 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePlugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False RunningIncompatibleAddons: False SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1627239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639663] Re: vdpau permissions incorrect in 304.132-0ubuntu0.16.04.2
** Bug watch added: code.mythtv.org/trac/ #12944 http://code.mythtv.org/trac/ticket/12944 ** Also affects: mythtv via http://code.mythtv.org/trac/ticket/12944 Importance: Unknown Status: Unknown -- 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/1639663 Title: vdpau permissions incorrect in 304.132-0ubuntu0.16.04.2 Status in MythTV: Unknown Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Bug description: Running version 16.04.2 vdpau only works as root in version 304.132-0ubuntu0.16.04.2. I can run vdpauinfo as normal user and get an error, unable to create device. Run as root (sudo vdpauinfo) and it works. Similarly, running mythfrontend with vdpau requires sudo mythfrontend to be able to work. The previous version 304.131 worked fine. I have temporarily fixed the problem by rolling back to that version. To manage notifications about this bug go to: https://bugs.launchpad.net/mythtv/+bug/1639663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"
** Bug watch removed: Debian Bug tracker #820774 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820774 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1575248 Title: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update" Status in AppStream: Invalid Status in Ubuntu GNOME: Invalid Status in appstream package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Fix Released Status in fwupd package in Debian: Fix Released Bug description: [Impact] * Checks for apt updates using apt or apt-get also update the appstream cache. Some of the appstream metadata installed locally isn't strictly valid as it's missing two fields. [Test Case] * fwupdmgr refresh * apt update * check for errors about metadata being ignored [Regression Potential] * This is just changing the XML metadata locally, I don't see any regression potential. [Other Info] * This fix has been applied upstream: https://github.com/hughsie/fwupd/commit/f4e0e88f7cba833a4badc1a3d62f1a08dd1bfd96 [Original report] I have found that when there are new packages available which my machine doesn't know about yet, if I run "sudo apt-get update" this is the output: Get:1 http://gb.archive.ubuntu.com/ubuntu xenial InRelease [247 kB] Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Get:3 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease [82.2 kB] Get:4 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages [28 B] Get:5 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease [82.2 kB] Get:6 http://security.ubuntu.com/ubuntu xenial-security/restricted i386 Packages [28 B] Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages [28 B] Get:8 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [28 B] Get:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 Packages [28 B] Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse Translation-en [28 B] Get:11 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1,201 kB] Get:12 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages [1,196 kB] Get:13 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en_GB [426 kB] Get:14 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en [568 kB] Get:15 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 Metadata [733 kB] Get:16 http://gb.archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons [409 kB] Get:17 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages [8,344 B] Get:18 http://gb.archive.ubuntu.com/ubuntu xenial/restricted i386 Packages [8,684 B] Get:19 http://gb.archive.ubuntu.com/ubuntu xenial/restricted Translation-en_GB [2,556 B] Get:20 http://gb.archive.ubuntu.com/ubuntu xenial/restricted Translation-en [2,908 B] Get:21 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 DEP-11 Metadata [186 B] Get:22 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7,532 kB] Get:23 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages [7,512 kB] Get:24 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en_GB [3,040 kB] Get:25 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en [4,354 kB] Get:26 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 DEP-11 Metadata [3,410 kB] Get:27 http://gb.archive.ubuntu.com/ubuntu xenial/universe DEP-11 64x64 Icons [7,448 kB] Get:28 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [144 kB] Get:29 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse i386 Packages [140 kB] Get:30 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse Translation-en_GB [88.1 kB] Get:31 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse Translation-en [106 kB] Get:32 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 DEP-11 Metadata [63.8 kB] Get:33 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse DEP-11 64x64 Icons [230 kB] Get:34 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [28 B] Get:35 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [28 B] Get:36 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main Translation-en [28 B] Get:37 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages [28 B] Get:38 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted i386 Packages [28 B] Get:39 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted
[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
** Changed in: appstream (Ubuntu Xenial) Importance: Undecided => Medium ** Bug watch added: Debian Bug tracker #820774 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820774 ** Also affects: appstream (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820774 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in appstream package in Debian: Unknown Bug description: [Impact] * The recent update of the Ubuntu asgen instance yielded it to generate modern metadata. While we could tell asgen to generate old- style metadata, fixing appstream is the better idea, since we already applied similar patches to appstream-glib (and having this package hold back updates is a bad idea). Currently, the unknown metadata is considered to be broken by appstream and it displays a warning about that issue during an `apt update` * The attached patch includes a second change to make AppStream more robust against broken YAML data, ensuring LP #1579712 can not be triggered on purpose or due to broken disks creating damaged YAML structure. [Test Case 1] * apt update * Check for errors about metadata being ignored [Test Case 2] * appstreamcli refresh --force * Check for errors about metadata being ignored * Check if we ignored data that should be present (search for it via `appstreamcli search `) * Run `appstreamcli status` and see if we still have information on the same amount of components as prior to the update. [Regression Potential] * Medium; The works case would be KDE Discover and GNOME Software loosing information on available software, but this risk is very low and the patch to fix this bug is very simple and has almost no regression potential. The YAML parser fix patch is a bit more complex, but should have no sideeffects. [Original report] Periodically I get emails from a machine with the subject: Cronif [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi And a body of: AppStream cache update completed, but some metadata was ignored due to errors. I have a machine monitored by Munin. One of the plugins used on that machine is /etc/munin/plugins/apt which periodically counts the number of packets that can be upgraded. This is achieved by a crontab entry installed from the package which looks like this: # # cron-jobs for munin-node # MAILTO=root # If the APT plugin is enabled, update packages databases approx. once # an hour (12 invokations an hour, 1 in 12 chance that the update will # happen), but ensure that there will never be more than two hour (7200 # seconds) interval between updates.. */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi For many months everything has been running smoothly. On the 23rd November 2016 I started getting the "AppStream cache update completed, but some metadata was ignored due to errors." messages at a rate of about ten a day. I did a quick Google search which turned up a handful of bugs from earlier this year, such as Bug1575248. That is marked as Fixed Released though, so I am raising this new bug. If there are any further diagnostic details I can provide, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 09:57:18 2016 InstallationDate: Installed on 2013-05-08 (1295 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508) JournalErrors: -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 GMT. -- Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SourcePackage: appstream UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1573206] Re: GNOME Software does not install third-party .deb packages
*** This bug is a duplicate of bug 1573408 *** https://bugs.launchpad.net/bugs/1573408 Also having the problem. -- 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/1573206 Title: GNOME Software does not install third-party .deb packages Status in gdebi: New Status in GNOME Software: New Status in GRadio: New Status in Ubuntu GNOME: Triaged Status in Ubuntu Studio: Triaged Status in gnome-software package in Ubuntu: Triaged Bug description: Ubuntu 16.04 LTS (clean install). 64-bit. Final release. Gnome-software version: 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 Version table: *** 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500 500 http://no.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status I intended to install MEGA Sync Client, Google Chrome and Dropbox by downloading the needed packages from their websites (respectively https://mega.nz/#sync and https://www.google.com/chrome/ and https://www.dropbox.com/install?os=lnx ). I opened the packages one by one with gnome-software and pressed Install - nothing, except for a super-quick progress bar animation, happened. No matter how many times I tried, same result. Also, an icon pops up on the panel saying "Waiting to install", but nothing seems to happen. This only seems to happen with third-party packages; installing a random deb from packages.ubuntu.com/xenial worked. I even tried to reinstall the system to make this work, but same problem. Gdebi, however, installs the packages as expected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 21 21:01:52 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2016-04-21 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nn_NO.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdebi/+bug/1573206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645437] [NEW] Problem appear like Xorg
Public bug reported: In first, i working ubuntu16.04 on VirtualBox machine.Host is linux Mint Cinnamon 17.3. I trying custom Ubuntu for Yosemite style whith help of Noob's Lab. Lot of commands line don't work ! Maybe problem with Gtk3 ? For examples: Gnome-Screenshot'captures are all black or back of screen not the windows... During splash you can see a destroy picture like lot of rays! and little others... Sorry for my english (i'm french!!!) et thank you very much for you work. Cyril ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Nov 28 19:28:04 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-11-19 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=17e79935-2f42-4abb-8d15-2246144b6d53 ro drm.debug=0xe quiet vesafb.invalid=1 nopat splash plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Nov 28 19:26:22 2016 xserver.configfile: default xserver.errors: AIGLX error: vboxvideo does not export required DRI extension AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1645437 Title: Problem appear like Xorg Status in xorg package in Ubuntu: New Bug description: In first, i working ubuntu16.04 on VirtualBox machine.Host is linux Mint Cinnamon 17.3. I trying custom Ubuntu for Yosemite style whith help of Noob's Lab. Lot of commands line don't work ! Maybe problem with Gtk3 ? For examples: Gnome-Screenshot'captures are all black or back of screen not the windows... During splash you can see a destroy picture like lot of rays! and little others... Sorry for my english (i'm french!!!) et thank you very much for you work. Cyril ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Nov 28 19:28:04 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if
[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
Right, wait for a call for testing on this bug - before then you won't get it unless you build the package yourself. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Bug description: [Impact] * The recent update of the Ubuntu asgen instance yielded it to generate modern metadata. While we could tell asgen to generate old- style metadata, fixing appstream is the better idea, since we already applied similar patches to appstream-glib (and having this package hold back updates is a bad idea). Currently, the unknown metadata is considered to be broken by appstream and it displays a warning about that issue during an `apt update` * The attached patch includes a second change to make AppStream more robust against broken YAML data, ensuring LP #1579712 can not be triggered on purpose or due to broken disks creating damaged YAML structure. [Test Case 1] * apt update * Check for errors about metadata being ignored [Test Case 2] * appstreamcli refresh --force * Check for errors about metadata being ignored * Check if we ignored data that should be present (search for it via `appstreamcli search `) * Run `appstreamcli status` and see if we still have information on the same amount of components as prior to the update. [Regression Potential] * Medium; The works case would be KDE Discover and GNOME Software loosing information on available software, but this risk is very low and the patch to fix this bug is very simple and has almost no regression potential. The YAML parser fix patch is a bit more complex, but should have no sideeffects. [Original report] Periodically I get emails from a machine with the subject: Cronif [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi And a body of: AppStream cache update completed, but some metadata was ignored due to errors. I have a machine monitored by Munin. One of the plugins used on that machine is /etc/munin/plugins/apt which periodically counts the number of packets that can be upgraded. This is achieved by a crontab entry installed from the package which looks like this: # # cron-jobs for munin-node # MAILTO=root # If the APT plugin is enabled, update packages databases approx. once # an hour (12 invokations an hour, 1 in 12 chance that the update will # happen), but ensure that there will never be more than two hour (7200 # seconds) interval between updates.. */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi For many months everything has been running smoothly. On the 23rd November 2016 I started getting the "AppStream cache update completed, but some metadata was ignored due to errors." messages at a rate of about ten a day. I did a quick Google search which turned up a handful of bugs from earlier this year, such as Bug1575248. That is marked as Fixed Released though, so I am raising this new bug. If there are any further diagnostic details I can provide, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 09:57:18 2016 InstallationDate: Installed on 2013-05-08 (1295 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508) JournalErrors: -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 GMT. -- Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SourcePackage: appstream UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"
Ok. Does that joepardize the instalaltion or not? -Message d'origine- De : boun...@canonical.com [mailto:boun...@canonical.com] De la part de Krino Hoogestraat Envoyé : lundi 28 novembre 2016 19:27 À : c_cromph...@hotmail.com Objet : [Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update" Bug still persists after update: 20161128 18:00 GMT. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1575248 Title: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update" To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1575248/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1575248 Title: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update" Status in AppStream: Invalid Status in Ubuntu GNOME: Invalid Status in appstream package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Fix Released Status in fwupd package in Debian: Fix Released Bug description: [Impact] * Checks for apt updates using apt or apt-get also update the appstream cache. Some of the appstream metadata installed locally isn't strictly valid as it's missing two fields. [Test Case] * fwupdmgr refresh * apt update * check for errors about metadata being ignored [Regression Potential] * This is just changing the XML metadata locally, I don't see any regression potential. [Other Info] * This fix has been applied upstream: https://github.com/hughsie/fwupd/commit/f4e0e88f7cba833a4badc1a3d62f1a08dd1bfd96 [Original report] I have found that when there are new packages available which my machine doesn't know about yet, if I run "sudo apt-get update" this is the output: Get:1 http://gb.archive.ubuntu.com/ubuntu xenial InRelease [247 kB] Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Get:3 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease [82.2 kB] Get:4 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages [28 B] Get:5 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease [82.2 kB] Get:6 http://security.ubuntu.com/ubuntu xenial-security/restricted i386 Packages [28 B] Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages [28 B] Get:8 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [28 B] Get:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 Packages [28 B] Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse Translation-en [28 B] Get:11 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1,201 kB] Get:12 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages [1,196 kB] Get:13 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en_GB [426 kB] Get:14 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en [568 kB] Get:15 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 Metadata [733 kB] Get:16 http://gb.archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons [409 kB] Get:17 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages [8,344 B] Get:18 http://gb.archive.ubuntu.com/ubuntu xenial/restricted i386 Packages [8,684 B] Get:19 http://gb.archive.ubuntu.com/ubuntu xenial/restricted Translation-en_GB [2,556 B] Get:20 http://gb.archive.ubuntu.com/ubuntu xenial/restricted Translation-en [2,908 B] Get:21 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 DEP-11 Metadata [186 B] Get:22 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7,532 kB] Get:23 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages [7,512 kB] Get:24 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en_GB [3,040 kB] Get:25 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en [4,354 kB] Get:26 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 DEP-11 Metadata [3,410 kB] Get:27 http://gb.archive.ubuntu.com/ubuntu xenial/universe DEP-11 64x64 Icons [7,448 kB] Get:28 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [144 kB] Get:29 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse i386 Packages [140 kB] Get:30 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse Translation-en_GB [88.1 kB] Get:31 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse Translation-en [106 kB]
[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
@krino: Are you sure that you updated the AppStream package? Because it looks like Laney's upload didn't reach x-u-proposed yet (and therefore also isn't in x-updates yet). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Bug description: [Impact] * The recent update of the Ubuntu asgen instance yielded it to generate modern metadata. While we could tell asgen to generate old- style metadata, fixing appstream is the better idea, since we already applied similar patches to appstream-glib (and having this package hold back updates is a bad idea). Currently, the unknown metadata is considered to be broken by appstream and it displays a warning about that issue during an `apt update` * The attached patch includes a second change to make AppStream more robust against broken YAML data, ensuring LP #1579712 can not be triggered on purpose or due to broken disks creating damaged YAML structure. [Test Case 1] * apt update * Check for errors about metadata being ignored [Test Case 2] * appstreamcli refresh --force * Check for errors about metadata being ignored * Check if we ignored data that should be present (search for it via `appstreamcli search `) * Run `appstreamcli status` and see if we still have information on the same amount of components as prior to the update. [Regression Potential] * Medium; The works case would be KDE Discover and GNOME Software loosing information on available software, but this risk is very low and the patch to fix this bug is very simple and has almost no regression potential. The YAML parser fix patch is a bit more complex, but should have no sideeffects. [Original report] Periodically I get emails from a machine with the subject: Cronif [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi And a body of: AppStream cache update completed, but some metadata was ignored due to errors. I have a machine monitored by Munin. One of the plugins used on that machine is /etc/munin/plugins/apt which periodically counts the number of packets that can be upgraded. This is achieved by a crontab entry installed from the package which looks like this: # # cron-jobs for munin-node # MAILTO=root # If the APT plugin is enabled, update packages databases approx. once # an hour (12 invokations an hour, 1 in 12 chance that the update will # happen), but ensure that there will never be more than two hour (7200 # seconds) interval between updates.. */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi For many months everything has been running smoothly. On the 23rd November 2016 I started getting the "AppStream cache update completed, but some metadata was ignored due to errors." messages at a rate of about ten a day. I did a quick Google search which turned up a handful of bugs from earlier this year, such as Bug1575248. That is marked as Fixed Released though, so I am raising this new bug. If there are any further diagnostic details I can provide, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 09:57:18 2016 InstallationDate: Installed on 2013-05-08 (1295 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508) JournalErrors: -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 GMT. -- Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SourcePackage: appstream UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645432] [NEW] Ubuntu Modifcations slows Firefox if Adblock or UBlock present
Public bug reported: See for example: http://askubuntu.com/questions/333720/firefox-very-slow/352954#352954 A lot of people use Adblock or UBlock, don't you think this incompatibility should be solved? Especially since "Ubuntu Modifications" may well be the most useless thing ever. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1645432 Title: Ubuntu Modifcations slows Firefox if Adblock or UBlock present Status in firefox package in Ubuntu: New Bug description: See for example: http://askubuntu.com/questions/333720/firefox-very-slow/352954#352954 A lot of people use Adblock or UBlock, don't you think this incompatibility should be solved? Especially since "Ubuntu Modifications" may well be the most useless thing ever. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1645432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"
Bug still persists after update: 20161128 18:00 GMT. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1575248 Title: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update" Status in AppStream: Invalid Status in Ubuntu GNOME: Invalid Status in appstream package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Fix Released Status in fwupd package in Debian: Fix Released Bug description: [Impact] * Checks for apt updates using apt or apt-get also update the appstream cache. Some of the appstream metadata installed locally isn't strictly valid as it's missing two fields. [Test Case] * fwupdmgr refresh * apt update * check for errors about metadata being ignored [Regression Potential] * This is just changing the XML metadata locally, I don't see any regression potential. [Other Info] * This fix has been applied upstream: https://github.com/hughsie/fwupd/commit/f4e0e88f7cba833a4badc1a3d62f1a08dd1bfd96 [Original report] I have found that when there are new packages available which my machine doesn't know about yet, if I run "sudo apt-get update" this is the output: Get:1 http://gb.archive.ubuntu.com/ubuntu xenial InRelease [247 kB] Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Get:3 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease [82.2 kB] Get:4 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages [28 B] Get:5 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease [82.2 kB] Get:6 http://security.ubuntu.com/ubuntu xenial-security/restricted i386 Packages [28 B] Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages [28 B] Get:8 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [28 B] Get:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 Packages [28 B] Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse Translation-en [28 B] Get:11 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1,201 kB] Get:12 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages [1,196 kB] Get:13 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en_GB [426 kB] Get:14 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en [568 kB] Get:15 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 Metadata [733 kB] Get:16 http://gb.archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons [409 kB] Get:17 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages [8,344 B] Get:18 http://gb.archive.ubuntu.com/ubuntu xenial/restricted i386 Packages [8,684 B] Get:19 http://gb.archive.ubuntu.com/ubuntu xenial/restricted Translation-en_GB [2,556 B] Get:20 http://gb.archive.ubuntu.com/ubuntu xenial/restricted Translation-en [2,908 B] Get:21 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 DEP-11 Metadata [186 B] Get:22 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7,532 kB] Get:23 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages [7,512 kB] Get:24 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en_GB [3,040 kB] Get:25 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en [4,354 kB] Get:26 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 DEP-11 Metadata [3,410 kB] Get:27 http://gb.archive.ubuntu.com/ubuntu xenial/universe DEP-11 64x64 Icons [7,448 kB] Get:28 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [144 kB] Get:29 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse i386 Packages [140 kB] Get:30 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse Translation-en_GB [88.1 kB] Get:31 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse Translation-en [106 kB] Get:32 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 DEP-11 Metadata [63.8 kB] Get:33 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse DEP-11 64x64 Icons [230 kB] Get:34 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [28 B] Get:35 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [28 B] Get:36 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main Translation-en [28 B] Get:37 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages [28 B] Get:38 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted i386 Packages [28 B] Get:39 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted Translati
[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
Bug still persists after update: 20161128 18:00 GMT. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Bug description: [Impact] * The recent update of the Ubuntu asgen instance yielded it to generate modern metadata. While we could tell asgen to generate old- style metadata, fixing appstream is the better idea, since we already applied similar patches to appstream-glib (and having this package hold back updates is a bad idea). Currently, the unknown metadata is considered to be broken by appstream and it displays a warning about that issue during an `apt update` * The attached patch includes a second change to make AppStream more robust against broken YAML data, ensuring LP #1579712 can not be triggered on purpose or due to broken disks creating damaged YAML structure. [Test Case 1] * apt update * Check for errors about metadata being ignored [Test Case 2] * appstreamcli refresh --force * Check for errors about metadata being ignored * Check if we ignored data that should be present (search for it via `appstreamcli search `) * Run `appstreamcli status` and see if we still have information on the same amount of components as prior to the update. [Regression Potential] * Medium; The works case would be KDE Discover and GNOME Software loosing information on available software, but this risk is very low and the patch to fix this bug is very simple and has almost no regression potential. The YAML parser fix patch is a bit more complex, but should have no sideeffects. [Original report] Periodically I get emails from a machine with the subject: Cron <root@Jenkins> if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi And a body of: AppStream cache update completed, but some metadata was ignored due to errors. I have a machine monitored by Munin. One of the plugins used on that machine is /etc/munin/plugins/apt which periodically counts the number of packets that can be upgraded. This is achieved by a crontab entry installed from the package which looks like this: # # cron-jobs for munin-node # MAILTO=root # If the APT plugin is enabled, update packages databases approx. once # an hour (12 invokations an hour, 1 in 12 chance that the update will # happen), but ensure that there will never be more than two hour (7200 # seconds) interval between updates.. */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi For many months everything has been running smoothly. On the 23rd November 2016 I started getting the "AppStream cache update completed, but some metadata was ignored due to errors." messages at a rate of about ten a day. I did a quick Google search which turned up a handful of bugs from earlier this year, such as Bug1575248. That is marked as Fixed Released though, so I am raising this new bug. If there are any further diagnostic details I can provide, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 09:57:18 2016 InstallationDate: Installed on 2013-05-08 (1295 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508) JournalErrors: -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 GMT. -- Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SourcePackage: appstream UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645415] [NEW] Earphones not working on Ubuntu 16.04.1 after resume from suspend
Public bug reported: I am a new Ubuntu user and installed 16.04.1 LTS dual boot with Windows 10. Recently I discovered that my earphones have a pulsating white noise after the machine is resumed from suspend. The laptop speakers are fine though. On reboot everything works fine. I have tried restarting pulseaudio using following commands: pulseaudio -k pulseaudio --start Also tried this: /usr/bin/pasuspender /bin/true But the pulsating sound persists. My laptop model is ASUS ROG G501VW F1034T. I have updated my system using commands: sudo apt update sudo apt upgrade Please let me know if I need to provide outputs of commands or any system logs. Here is the "lsb_release -rd" command output: Description:Ubuntu 16.04.1 LTS Release:16.04 ** Affects: ubuntu Importance: Undecided Status: New ** Package changed: alsa-driver (Ubuntu) => ubuntu -- 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/1645415 Title: Earphones not working on Ubuntu 16.04.1 after resume from suspend Status in Ubuntu: New Bug description: I am a new Ubuntu user and installed 16.04.1 LTS dual boot with Windows 10. Recently I discovered that my earphones have a pulsating white noise after the machine is resumed from suspend. The laptop speakers are fine though. On reboot everything works fine. I have tried restarting pulseaudio using following commands: pulseaudio -k pulseaudio --start Also tried this: /usr/bin/pasuspender /bin/true But the pulsating sound persists. My laptop model is ASUS ROG G501VW F1034T. I have updated my system using commands: sudo apt update sudo apt upgrade Please let me know if I need to provide outputs of commands or any system logs. Here is the "lsb_release -rd" command output: Description: Ubuntu 16.04.1 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1645415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645352] Re: No HDMI output after upgrade to 16.04!
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1645352 Title: No HDMI output after upgrade to 16.04! Status in xorg package in Ubuntu: New Bug description: Running Ubuntu 16.04 64bit, 4.4.8 Kernel on an ASUS Trio with Intel® Haswell graphics card and using i915 driver. After upgrade there is no HDMI output to the external screen that I use daily. I did the following: - Upgraded to 4.4.8 Kernel hoping that the issue would be resolved. - Checked for other reports of this issue and followed advise to use NVIDIA 364 drivers. - Checked Intel for the most recent driver which is already packaged with 16.04; it is the i915 driver which is in use. - Used Intel driver update tool to ensure that update is correct. - Purchased a HDMI adapter to use mini-display port; works and reports HDMI1 is in use, but HDMI2 is not recognized (when monitor is plugged in to HDMI2) - Someone has assisted and has confirmed that there seems to be no hardware issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639215] Re: After upgrade of Nvidia 304 drivers, mythfrontend.real crashed with SIGSEGV in QGLFormat::openGLVersionFlags()
** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided => High -- 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/1639215 Title: After upgrade of Nvidia 304 drivers, mythfrontend.real crashed with SIGSEGV in QGLFormat::openGLVersionFlags() Status in Mythbuntu: Won't Fix Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Bug description: The Nvidia 304 drivers were updated by an "apt update && apt upgrade" to 304.132-0ubuntu0.16.04.2. On the next reboot, mythfrontend crashed each time it was started. The mythfrontend.log file always shows the same messages - see the attached mythfrontend.log file. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mythtv-frontend 2:0.28.0+fixes.20161023.7f8f168-0ubuntu0mythbuntu3 [origin: LP-PPA-mythbuntu-0.28] ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: tbs5922fe nvidia .var.log.mythtv.mythavtest.log: .var.log.mythtv.mythccextractor.log: .var.log.mythtv.mythfilldatabase.log: .var.log.mythtv.mythjobqueue.log: .var.log.mythtv.mythlcdserver.log: .var.log.mythtv.mythmediaserver.log: .var.log.mythtv.mythshutdown.log: .var.log.mythtv.mythutil.log: .var.log.mythtv.mythwelcome.log: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: mythbuntu CurrentDesktop: XFCE Date: Sat Nov 5 00:30:56 2016 ExecutablePath: /usr/bin/mythfrontend.real InstallationDate: Installed on 2012-08-25 (1531 days ago) InstallationMedia: Mythbuntu 12.04 "Precise Pangolin" - Release amd64 (20120425) Installed_mythtv_dbg: 2:0.28.0+fixes.20161023.7f8f168-0ubuntu0mythbuntu3 ProcCmdline: /usr/bin/mythfrontend.real --syslog local7 ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f33652b2f29 <_ZN9QGLFormat18openGLVersionFlagsEv+313>: mov(%rax),%rax PC (0x7f33652b2f29) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: mythtv StacktraceTop: QGLFormat::openGLVersionFlags() () from /usr/lib/x86_64-linux-gnu/libQt5OpenGL.so.5 MythRenderOpenGL::Create (painter=..., device=0x0) at mythrender_opengl.cpp:114 MythMainWindow::Init (this=0x19e8210, forcedpainter=...) at mythmainwindow.cpp:1160 main (argc=3, argv=0x7ffd29d3e418) at main.cpp:1886 Title: mythfrontend.real crashed with SIGSEGV in QGLFormat::openGLVersionFlags() UpgradeStatus: Upgraded to xenial on 2016-10-08 (26 days ago) UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo syslog video To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1639215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645352] [NEW] No HDMI output after upgrade to 16.04!
You have been subscribed to a public bug: Running Ubuntu 16.04 64bit, 4.4.8 Kernel on an ASUS Trio with Intel® Haswell graphics card and using i915 driver. After upgrade there is no HDMI output to the external screen that I use daily. I did the following: - Upgraded to 4.4.8 Kernel hoping that the issue would be resolved. - Checked for other reports of this issue and followed advise to use NVIDIA 364 drivers. - Checked Intel for the most recent driver which is already packaged with 16.04; it is the i915 driver which is in use. - Used Intel driver update tool to ensure that update is correct. - Purchased a HDMI adapter to use mini-display port; works and reports HDMI1 is in use, but HDMI2 is not recognized (when monitor is plugged in to HDMI2) - Someone has assisted and has confirmed that there seems to be no hardware issues. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- No HDMI output after upgrade to 16.04! https://bugs.launchpad.net/bugs/1645352 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
Slows down and hangs seem to be two different problems. My mashines never hang but "slow down" when copying thousands of different files. I found an interesting answer here: http://askubuntu.com/questions/122113/copy-to-usb-memory-stick-really-slow 1'st answer from izx > reason 2, that You can see in my photo. After 3 hours of copying files I copied 29,4GB from 38,7GB but ONLY 20460 from 69502 files. If there is a problem that deserves a bug report then there is one with estimating the real time. At first system showed me 4 hours, then decreased to 2, the last hour lasted 110 minutes. Copying itself (this screenshot was taken on 2016 but from Ubuntu 12.04) is very reliable I'd say if only USB drive is reliable. ** Attachment added: "Copying.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1208993/+attachment/4784306/+files/Copying.png -- 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/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in nautilus package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1208993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645398] [NEW] /usr/bin/users-admin:11:g_queue_foreach:passwd_authenticate:on_user_passwd_current_focus_out:_gtk_marshal_BOOLEAN__BOXED:g_closure_invoke
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-system-tools. This problem was most recently seen with package version 3.0.0-4ubuntu2, the problem page at https://errors.ubuntu.com/problem/bf188cdcb003af8e34598e6b4ccf1ceed39b41e5 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 you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New ** Tags: precise raring trusty utopic vivid xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/1645398 Title: /usr/bin/users- admin:11:g_queue_foreach:passwd_authenticate:on_user_passwd_current_focus_out:_gtk_marshal_BOOLEAN__BOXED:g_closure_invoke Status in gnome-system-tools package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-system-tools. This problem was most recently seen with package version 3.0.0-4ubuntu2, the problem page at https://errors.ubuntu.com/problem/bf188cdcb003af8e34598e6b4ccf1ceed39b41e5 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 you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1645398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645393] [NEW] /usr/bin/unity-control-center:11:append_sections_from_gsettings:reload_sections:wm_window_event_filter:gdk_event_apply_filters:gdk_event_source_translate_event
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+16.10.20161003.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/615e72d6b8a79a9e1ccc82dafe724422ed9b6343 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 you can request it at http://forms.canonical.com/reports/. ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: kylin-14.10 kylin-15.04 trusty utopic vivid wily xenial yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1645393 Title: /usr/bin/unity-control- center:11:append_sections_from_gsettings:reload_sections:wm_window_event_filter:gdk_event_apply_filters:gdk_event_source_translate_event Status in unity-control-center package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+16.10.20161003.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/615e72d6b8a79a9e1ccc82dafe724422ed9b6343 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 you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1645393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645384] [NEW] package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida
Public bug reported: el problema se genero cuando intentaba descargar unos programas, no se completo la descarga y la tuve que reiniciar y posterior al reinicio aparecio el mensaje de error. ProblemType: Package DistroRelease: elementary 0.4 Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 28 09:10:05 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 128 InstallationDate: Installed on 2016-11-26 (1 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package loki third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1645384 Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 128 Status in gconf package in Ubuntu: New Bug description: el problema se genero cuando intentaba descargar unos programas, no se completo la descarga y la tuve que reiniciar y posterior al reinicio aparecio el mensaje de error. ProblemType: Package DistroRelease: elementary 0.4 Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 28 09:10:05 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 128 InstallationDate: Installed on 2016-11-26 (1 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1645384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645378] [NEW] firefox 50.0's address bar does not accept long entries
Public bug reported: When I type in: - bugs.launchpad.net or - plop plop plop plop then enter in my address bar, nothing occurs... If I type in "plop plop plop", then I'm redirected correctly to my default search engine result page. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1645378 Title: firefox 50.0's address bar does not accept long entries Status in firefox package in Ubuntu: New Bug description: When I type in: - bugs.launchpad.net or - plop plop plop plop then enter in my address bar, nothing occurs... If I type in "plop plop plop", then I'm redirected correctly to my default search engine result page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1645378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645378] Re: firefox 50.0's address bar does not accept long entries
This is apparently due to the DDG addon... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1645378 Title: firefox 50.0's address bar does not accept long entries Status in firefox package in Ubuntu: New Bug description: When I type in: - bugs.launchpad.net or - plop plop plop plop then enter in my address bar, nothing occurs... If I type in "plop plop plop", then I'm redirected correctly to my default search engine result page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1645378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132
** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1639180 Title: no login possible after update to nvidia 304.132 Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-legacy-304xx package in Debian: Confirmed Bug description: Ubuntu 16.04 LTS NVIDIA driver: - nvidia-graphics-drivers-304 - update to version 304.132 dpkg.log: upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2 - reboot - lightdm login screen - login - a few seconds some flickering - and the lightdm login screen appears again It is not possible to login. Unity is not loading. .xsession-errors: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 34 Current serial number in output stream: 35 See also bug 1634802 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631191] Re: Display backlight won't turn on after screen timeout
I am also seeing this with my Oryx Pro 2 - please fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1631191 Title: Display backlight won't turn on after screen timeout Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Bug description: Using nVidia driver 367.44 on Skylake Intel Processors, with 1000 series graphics, the backlight won't turn on after turned off by gnome session idle delay (org.gnome.desktop.session idle-delay). or by `xset dpms force off` Resume from suspend is unaffected. This is on a clean install of 16.10 with the 367.44 nVidia driver. This is a regression from the 367.35 driver. 367.48 and 370.28 also exhibit this behavior. This is confirmed on the following hardware: Oryx Pro 2 (oryp2) i7-6700HQ with 1070 Serval 10 (serw10) i7-6700 with 1060 Bonobo 11 (bonw11) i7-6700K with dual 1070 Steps to reproduce: 1. Install a fresh image of Yakkety and 367.44 from the graphics driver team's PPA. 2. Log in to Unity shell 3. Lock screen and wait for dimming. 4. Move the mouse to 'resume' 5. The screen will turn on, but the backlight is still off The current workaround: 1. Hit tty1 (Ctrl+Alt+F1) 2. Hit tty7 (Ctrl+Alt+F7) This will bring Unity back to life. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nvidia-367 367.44-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 6 16:17:11 2016 SourcePackage: nvidia-graphics-drivers-367 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1631191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645375] [NEW] Xorg freeze when starting chromium-browser
Public bug reported: I get messages like the following in the journal: kernel: nouveau :0a:00.0: fifo: CACHE_ERROR - ch 7 [chromium- browse[6657]] subc 3 mthd 15ec data I can still SSH in. Chromium Version 53.0.2785.143 Built on Ubuntu , running on Ubuntu 16.10 (64-bit) lsb_release -rd: Description: Ubuntu 16.10 Release: 16.10 apt-cache policy xserver-xorg-video-nouveau: xserver-xorg-video-nouveau: Installed: 1:1.0.12-2 Candidate: 1:1.0.12-2 Version table: *** 1:1.0.12-2 500 500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status What you expected to happen: Chrome Browser window to open. What happened instead: Outline of Chrome Browser window appeared and then Xorg froze. Mouse point could be moved on one display but between displays. Nothing was responsive on the UI. Running Chromium with: chromium-browser -gpu works and does not freeze. Regards ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Nov 28 15:49:47 2016 DistUpgraded: 2016-10-19 16:07:29,098 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.6, 4.8.0-26-generic, x86_64: installed virtualbox, 5.1.6, 4.8.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862] InstallationDate: Installed on 2016-01-05 (327 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. PowerEdge T320 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-27-generic root=UUID=0f94436a-b93a-4750-b0f1-08be2c4b2188 ro rootflags=subvol=@ SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to yakkety on 2016-10-19 (40 days ago) dmi.bios.date: 01/29/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.2 dmi.board.name: 0FDT3J dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.2:bd01/29/2015:svnDellInc.:pnPowerEdgeT320:pvr:rvnDellInc.:rn0FDT3J:rvrA02:cvnDellInc.:ct17:cvr: dmi.product.name: PowerEdge T320 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Mon Nov 28 15:43:48 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu yakkety -- 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/1645375 Title: Xorg freeze when starting chromium-browser Status in xorg package in Ubuntu: New Bug description: I get messages like the following in the journal: kernel: nouveau :0a:00.0: fifo: CACHE_ERROR - ch 7 [chromium- browse[6657]] subc 3 mthd 15ec data I can still SSH in. Chromium Version 53.0.2785.143 Built on Ubuntu , running on Ubuntu 16.10 (64-bit) lsb_release -rd: Description:Ubuntu 16.10 Release:16.10 apt-cache policy xserver-xorg-video-nouveau: xserver-xorg-video-nouveau: Installed: 1:1.0.12-2 Candidate: 1:1.0.12-2 Version table: *** 1:1.0.12-2 500 500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status What you expected to happen:
[Desktop-packages] [Bug 1645370] Re: nautilus crashed with SIGSEGV in gdk_pixbuf_loader_write()
*** This bug is a duplicate of bug 1645286 *** https://bugs.launchpad.net/bugs/1645286 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1645286, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1645370/+attachment/4784240/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1645370/+attachment/4784242/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1645370/+attachment/4784246/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1645370/+attachment/4784247/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1645370/+attachment/4784248/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1645370/+attachment/4784250/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1645370/+attachment/4784251/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1645286 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1645370 Title: nautilus crashed with SIGSEGV in gdk_pixbuf_loader_write() Status in nautilus package in Ubuntu: New Bug description: possible one of those buffer overflows https://bugzilla.gnome.org/show_bug.cgi?id=775244 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 Uname: Linux 4.7.0-040700-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Nov 28 11:19:14 2016 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1470333588 InstallationDate: Installed on 2015-12-02 (361 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027) ProcCmdline: nautilus -n ProcCwd: /home/muelli Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so ?? () from /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jpeg.so gdk_pixbuf_loader_write () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12 gnome_desktop_thumbnail_factory_generate_thumbnail () from /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12 Title: nautilus crashed with SIGSEGV in gdk_pixbuf_loader_write() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1645370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1196239] Re: Add support for fake modes on laptop screens which only have one
Bug filed to track scaling support: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1645372 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1196239 Title: Add support for fake modes on laptop screens which only have one Status in Canonical System Image: Triaged Status in Mir: Triaged Status in xorg-server package in Ubuntu: Won't Fix Bug description: Reproduce: run mirout What happens: I only see one resolution supported. What should happen: I should see more resolutions, like I do on unity7. I guess, if in doubt, “support” the same ones as xrandr. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1196239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645366] [NEW] upgrading pulseaudio 8.3.0 to 8.3.1 on 16.04 broke bluetooth audio for me
Public bug reported: Description:Ubuntu 16.04.1 LTS Release:16.04 Package name: 1:8.0-0ubuntu3.1 After using the software updater to upgrade libpulseaudio I am unable to connect/pair my Bose QC 35 to my computer. When using blueman to connect, I receive the following error: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/dbus/connection.py", line 607, in msg_reply_handler *message.get_args_list())) File "/usr/lib/python3/dist-packages/blueman/bluez/Device.py", line 33, in err raise exception dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. This used to work before the update. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1645366 Title: upgrading pulseaudio 8.3.0 to 8.3.1 on 16.04 broke bluetooth audio for me Status in pulseaudio package in Ubuntu: New Bug description: Description:Ubuntu 16.04.1 LTS Release:16.04 Package name: 1:8.0-0ubuntu3.1 After using the software updater to upgrade libpulseaudio I am unable to connect/pair my Bose QC 35 to my computer. When using blueman to connect, I receive the following error: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/dbus/connection.py", line 607, in msg_reply_handler *message.get_args_list())) File "/usr/lib/python3/dist-packages/blueman/bluez/Device.py", line 33, in err raise exception dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. This used to work before the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1645366/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645357] [NEW] configuration file falied md5sum by DPKG verify
Public bug reported: ??5?? c /etc/default/chromium-browser I'm downloading the source packages and will purge the package. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1257 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-LVDS-1: edid-base64: AP///wAw5GoEAAAYAQSQIhN4CgX1lFhWkigeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAb4BNW9FAAFjAwIDUAWMIQAAAbAgAMR+oKPGQSFhxuAIk= dpms: Off modes: 1366x768 1366x768 enabled: disabled status: connected DRM.card0-VGA-1: edid-base64: AP///wAF43AjvwUYAQNoMx14Kt1Fo1VPoCcSUFS/7wDRwLMAlQCBgIFAgcABAQEBAjqAGHE4LUBYLEUA/R4RAAAe/QAyTB5TEQAKICAgICAg/AAyMzcwCiAgICAgICAg/wBCTEtFMTlBMDAwMTkxAFQ= dpms: On modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected Date: Mon Nov 28 10:18:11 2016 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2016-11-27 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Load-Avg-1min: 1.43 Load-Processes-Running-Percent: 0.1% MachineType: Acer Aspire 5820T ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=55cfdd2f-fa32-4bee-a9b7-374612827a15 ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM51_CP dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.25:bd03/16/2011:svnAcer:pnAspire5820T:pvrV1.25:rvnAcer:rnJM51_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 5820T dmi.product.version: V1.25 dmi.sys.vendor: Acer gconf-keys: /desktop/gnome/applications/browser/exec = b'\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1645357 Title: configuration file falied md5sum by DPKG verify Status in chromium-browser package in Ubuntu: New Bug description: ??5?? c /etc/default/chromium-browser I'm downloading the source packages and will purge the package. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1257 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-LVDS-1: edid-base64: AP///wAw5GoEAAAYAQSQIhN4CgX1lFhWkigeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAb4BNW9FAAFjAwIDUAWMIQAAAbAgAMR+oKPGQSFhxuAIk= dpms: Off modes: 1366x768 1366x768 enabled: disabled status: connected DRM.card0-VGA-1: edid-base64: AP///wAF43AjvwUYAQNoMx14Kt1Fo1VPoCcSUFS/7wDRwLMAlQCBgIFAgcABAQEBAjqAGHE4LUBYLEUA/R4RAAAe/QAyTB5TEQAKICAgICAg/AAyMzcwCiAgICAgICAg/wBCTEtFMTlBMDAwMTkxAFQ= dpms: On modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected Date: Mon Nov 28 10:18:11 2016 Desktop-Session: 'ubuntu'
[Desktop-packages] [Bug 1453655] Re: desktop icons disappear on Ubuntu 15.04 when clicking Open Dropbox folder
Hello, I'm here to report that this bug still appears for me on a recent clean install of Ubuntu 16.10. It was also present, for me, in a previous installation of Ubuntu 16.04. Whenever I open the dropbox folder from the dropbox indicator, all the icons on the desktop disappear. I have nautilus version 1:3.20.3-1ubuntu3.1. -- 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/1453655 Title: desktop icons disappear on Ubuntu 15.04 when clicking Open Dropbox folder Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus-dropbox package in Ubuntu: Invalid Status in nautilus source package in Vivid: Fix Released Status in nautilus source package in Wily: Fix Released Bug description: I've been using both Ubuntu and dropbox for several years. With Ubuntu 15.04 there is a new problem that my desktop icons disappear when I click on the dropbox icon in the status bar and choose Open Dropbox Folder. Then the desktop icons will disappear - but will remain visible in Files -> Desktop. The only way I know to get the desktop icons back is to log out and then log back in again. The bug is 100% reproducible, and it never appeared before 15.04. I also have Copy on my status bar. Clicking on Copy -> Open Copy Folder has no problems. Likewise I can use File with a right click and use Open a New Window and that too is OK. Only dropbox has a problem and only since 15.04 If I can help in any way, please contact me ilan.tal - at - gmail.com [Impact] DE-agnostic programs that invoke nautilus using "nautilus --no-desktop" will make the nautilus-rendered desktop vanish. Dropbox is one such case. [Test Case] 1. Launch nautilus, and make sure it is currently rendering the desktop. 2. Run "nautilus --no-desktop /" 3. See if the desktop vanishes. [Regression Potential] The patch is relatively trivial, only affecting the --no-desktop codepath. As a worst case, --no-desktop would not function correctly in cases where nautilus is not already running (--no-desktop when nautilus is not already running means nautilus should not render the desktop at all). Just to make sure, this additional test case should be used: 1. Kill nautilus, and make sure it doesn't get relaunched. 2. Check to see what the desktop looks like (shouldn't be rendered by nautilus, at least) 3. Launch "nautilus --no-desktop /" 4. Make sure that nautilus really doesn't render a desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1453655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645341] [NEW] Wacom serial: Screen rotation triggers pen/eraser rotation but not for finger touch
Public bug reported: After updating to xenial the finger touch was broken. With an update to yakkety the finger touch device came back, but it doesn't rotate with the screen, how it used to in former releases. Pen and eraser are rotated as expected. I discovered, that the bug occurs only with linux kernels after 4.4, so it depends on recent changes in the kernel. The 'xsetwacom list devices' command generates the output: Wacom Serial Penabled 2FG Touchscreen Pen stylusid: 15 type: STYLUS Wacom Serial Penabled 2FG Touchscreen Finger touch id: 16 type: TOUCH Wacom Serial Penabled 2FG Touchscreen Pen eraserid: 18 type: ERASER ... but with the old linux kernel from utopic (4.2.0) the ids are different: 15 for the stylus (unchanged), 17 for the eraser, 18 for finger touch This bug affects: * an updated system how described above * a fresh installation of yakkety (used to file this bug) * the zesty daily build ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg-input-wacom 1:0.33.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 28 15:10:21 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu InstallationDate: Installed on 2016-11-28 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP EliteBook 2760p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=71701156-1f2c-4138-a7eb-0c16ea6b53d3 ro quiet splash SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SOU Ver. F.62 dmi.board.name: 162A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 05.41 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SOUVer.F.62:bd05/27/2016:svnHewlett-Packard:pnHPEliteBook2760p:pvrA0005F02:rvnHewlett-Packard:rn162A:rvrKBCVersion05.41:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2760p dmi.product.version: A0005F02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Mon Nov 28 14:32:58 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset ** Affects: xf86-input-wacom (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu yakkety zesty ** Summary changed: - Wacom serial: Screen rotation triggers pen/eraser rotation but not for finger tocuh + Wacom serial: Screen rotation triggers pen/eraser rotation but not for finger touch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1645341 Title: Wacom serial: Screen rotation triggers pen/eraser rotation but not for finger touch Status in xf86-input-wacom package in Ubuntu: New Bug description: After updating to xenial the finger touch was broken. With an update to yakkety the finger touch device came back, but it doesn't rotate with the screen, how it used to in former releases. Pen and eraser are rotated as expected. I discovered, that the bug occurs only with linux kernels after 4.4, so it depends on recent changes in the kernel. The 'xsetwacom list devices' command generates the output: Wacom Serial Penabled 2FG Touchscreen Pen stylus id: 15 type: STYLUS Wacom Serial Penabled 2FG Touchscreen Finger touchid: 16 type: TOUCH Wacom Serial Penabled 2FG Touchscreen Pen eraser id: 18 type: ERASER ... but with the old linux kernel from utopic (4.2.0) the ids are different: 15 for the stylus (unchanged), 17 for the eraser, 18 for finger touch This bug affects: * an updated system how described above * a fresh installation of yakkety (used to file this bug) * the zesty daily build ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg-input-wacom 1:0.33.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8
[Desktop-packages] [Bug 1623450] Re: Cursor jumps to top-right corner when releasing your finger from the touchpad while the left mouse button on the touchpad is pressed, Lenovo E460, ALPS Touchpad
;( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1623450 Title: Cursor jumps to top-right corner when releasing your finger from the touchpad while the left mouse button on the touchpad is pressed, Lenovo E460, ALPS Touchpad Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: 1) Ubuntu 16.04.01 LTS 2) 1.8.2-1ubuntu3 3) When releasing the finger from the touchpad (e.g. while marking larger portions of text, or scrolling using the sidebar) I expect the cursor to remain in the position it was before the finger was upped from the keyboard. 4) Instead, the cursor jumps to the top right of the screen, marking the entire text of a page and scrolling all the way up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu3 Uname: Linux 4.7.3-040703-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 14 13:07:17 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu InstallationDate: Installed on 2016-09-13 (0 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b541 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20ETCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.3-040703-generic root=UUID=6eb6b9f5-2dbe-49be-bfa3-54cfde10c957 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R00ET45W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ETCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR00ET45W(1.20):bd06/12/2016:svnLENOVO:pn20ETCTO1WW:pvrThinkPadE460:rvnLENOVO:rn20ETCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20ETCTO1WW dmi.product.version: ThinkPad E460 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Sep 14 12:41:57 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5297 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1623450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636255] Re: The "restore-missing" functionality is not working as expected
*** This bug is a duplicate of bug 1610667 *** https://bugs.launchpad.net/bugs/1610667 Hello Nicola, thank you for that information. It seems to me that you suffer from the same problem that I reported in bug #1610667 against a test version (at that time). I will therefore mark this as a duplicate and confirm both bugs. Best Regards Vej ** Changed in: deja-dup Status: Incomplete => Triaged ** Changed in: deja-dup (Ubuntu) Status: Incomplete => Confirmed ** This bug has been marked a duplicate of bug 1610667 Incremental backup prevents "restore-missing" from restoring files, that were deleted before -- 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/1636255 Title: The "restore-missing" functionality is not working as expected Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Confirmed Bug description: I have found out that the "--restore-missing" functionality is not working as expected. I have set up déja-dup to backup some folders every day. If I delete some files today, and then I use the "restore-missing" functionality the same day (today in my example), déja-dup shows me the list of missing files as expected. The problem is that if I use the "restore-missing" functionality from tomorrow on, no files are listed anymore. It seems that "restore-missing" seeks the missing files only if the backup is made the same day that I deleted the files. The behavior I expected is that "restore-missing" should search the entire backup series, and create a list of all missing files since the first backup was made. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: deja-dup 34.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 18:09:40 2016 InstallationDate: Installed on 2014-04-23 (914 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: deja-dup UpgradeStatus: Upgraded to xenial on 2016-07-31 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1636255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1643467] Re: Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec
** Tags added: precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1643467 Title: Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec Status in firefox package in Ubuntu: Confirmed Status in libav package in Ubuntu: Confirmed Bug description: Whenever it tries to play a video, Firefox 50 displays this message at the top of every page: "libavcodec may be vulnerable or is not supported, and should be updated to play video" https://dxr.mozilla.org/mozilla-central/source/browser/locales/en- US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742 Firefox refuses any libavcodec version prior to 54.35.1 (unless media.libavcodec.allow-obsolete==true). https://dxr.mozilla.org/mozilla- central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60 Users should not be subjected to this warning, as it is vague (does not instruct them how to fix it). Ubuntu 14.04 LTS should ship with an updated version of libavcodec. DistroRelease: Ubuntu 14.04 Package: firefox 50.0+build2-0ubuntu0.14.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1643467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645332] Re: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1642966 *** https://bugs.launchpad.net/bugs/1642966 ** This bug has been marked a duplicate of bug 1642966 package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1645332 Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: not sure what I'm looking at. Please advise. Thanks. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CupsErrorLog: Date: Mon Nov 21 08:41:19 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-12-07 (357 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) KernLog: Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 2325BC7 Papersize: letter ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-04 (116 days ago) dmi.bios.date: 09/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET82WW (2.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 2325BC7 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: AG978241 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2325BC7:pvrThinkPadX230:rvnLENOVO:rn2325BC7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2325BC7 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2015-08-05T00:18:48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1645332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645332] [NEW] package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: not sure what I'm looking at. Please advise. Thanks. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CupsErrorLog: Date: Mon Nov 21 08:41:19 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-12-07 (357 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) KernLog: Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 2325BC7 Papersize: letter ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-04 (116 days ago) dmi.bios.date: 09/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET82WW (2.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 2325BC7 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: AG978241 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2325BC7:pvrThinkPadX230:rvnLENOVO:rn2325BC7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2325BC7 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2015-08-05T00:18:48 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check package-from-proposed xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1645332 Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: not sure what I'm looking at. Please advise. Thanks. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CupsErrorLog: Date: Mon Nov 21 08:41:19 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-12-07 (357 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) KernLog: Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 2325BC7 Papersize: letter ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-49-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-04 (116 days ago) dmi.bios.date: 09/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET82WW (2.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 2325BC7 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: AG978241 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2325BC7:pvrThinkPadX230:rvnLENOVO:rn2325BC7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2325BC7 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2015-08-05T00:18:48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1645332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1645325] [NEW] audacious tracklist staying focused
Public bug reported: When using audacious, tracklist window should stay focused / on top z-index when you drag and drop a track into it. This is, for example, default behavior on Winamp on Windows, but doesn't happen on Audacious on Ubuntu. I think it is extremely handy to happen. Current behavior is, when you drag the track from a Nautilus window, it gets focused and it overlaps and hides the tracklist window, making it necessary to manually put them in non-overlapping places. I reported this to audacious developers and they pointed out that although it is a good idea, there is nothing they can do, and I should report it as a file manager bug/feature request. Thank you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 CurrentDesktop: Unity Date: Mon Nov 28 13:43:58 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+276+150'" LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1645325 Title: audacious tracklist staying focused Status in nautilus package in Ubuntu: New Bug description: When using audacious, tracklist window should stay focused / on top z-index when you drag and drop a track into it. This is, for example, default behavior on Winamp on Windows, but doesn't happen on Audacious on Ubuntu. I think it is extremely handy to happen. Current behavior is, when you drag the track from a Nautilus window, it gets focused and it overlaps and hides the tracklist window, making it necessary to manually put them in non-overlapping places. I reported this to audacious developers and they pointed out that although it is a good idea, there is nothing they can do, and I should report it as a file manager bug/feature request. Thank you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 CurrentDesktop: Unity Date: Mon Nov 28 13:43:58 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+276+150'" LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1645325/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1645308] [NEW] [SRU] Backport zeromq3 4.2.0 to yakkety
Public bug reported: [Impact] As per product requirement, we have released a git-snapshot based pre- release version of zeromq3 4.2.0 to yakkety (4.1.5+git20160811+2fc86bc) as the upstream version was not yet available. The agreement was that we will release the snapshot-based version only if, once the official update is available we will update and switch. The rationale for this would be that the snapshot-based version is anyway more-or-less feature compatible with the official version. It's also not wise to keep shipping a snapshot for long as some bugfixes might be missing from the cherry-pick. The generated binaries are binary-compatible, with only a few new symbols exported in the main 4.2.0 version. [Test Case] No particular test-case - installing the new version and making sure that existing reverse-dependencies still work as intended. [Regression Potential] There is, of course, some regression potential, but as already mentioned: there weren't too many commits since the git snapshot that our previous version was based off. ** Affects: zeromq3 (Ubuntu) Importance: Medium Status: Fix Released ** Affects: zeromq3 (Ubuntu Yakkety) Importance: Medium Assignee: Łukasz Zemczak (sil2100) Status: In Progress ** Also affects: zeromq3 (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: zeromq3 (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: zeromq3 (Ubuntu Yakkety) Status: New => In Progress ** Changed in: zeromq3 (Ubuntu) Status: New => Fix Released ** Changed in: zeromq3 (Ubuntu Yakkety) Assignee: (unassigned) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1645308 Title: [SRU] Backport zeromq3 4.2.0 to yakkety Status in zeromq3 package in Ubuntu: Fix Released Status in zeromq3 source package in Yakkety: In Progress Bug description: [Impact] As per product requirement, we have released a git-snapshot based pre- release version of zeromq3 4.2.0 to yakkety (4.1.5+git20160811+2fc86bc) as the upstream version was not yet available. The agreement was that we will release the snapshot-based version only if, once the official update is available we will update and switch. The rationale for this would be that the snapshot-based version is anyway more-or-less feature compatible with the official version. It's also not wise to keep shipping a snapshot for long as some bugfixes might be missing from the cherry-pick. The generated binaries are binary-compatible, with only a few new symbols exported in the main 4.2.0 version. [Test Case] No particular test-case - installing the new version and making sure that existing reverse-dependencies still work as intended. [Regression Potential] There is, of course, some regression potential, but as already mentioned: there weren't too many commits since the git snapshot that our previous version was based off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1645308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor
Was this tested with HiDPI? On fully updated VM (zesty) with scaling- factor set to 2 initially window size is correct, but after resizing VM, nautilus desktop window is 1/4 from size it should have. I think that I have same problem also on my main pc (also zesty) - desktop window is only 1/4 after resolution changes. Restarting nautilus "fixes" problem until next resolution changes. -- 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/1626935 Title: [yakkety] desktop is black and/or flickering after plugging in a second monitor Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Yakkety: Fix Released Bug description: [ Description ] Nautilus's wallpaper drawing doesn't respond to changes in monitor configuration. Instead of your wallpaper you see black. [ Fix ] Inside nautilus, the wallpaper widget connects to GTK's "monitors- changed" signal when it is constructed. It does this only once the widget is realized - a "realized" signal handler connects to "monitors-changed". In Yakkety, the "realized" signal handler is connected after the widget is already realized, meaning that the signal handler isn't called and we don't connect to the "monitors- changed" signal. The proposed fix remedies this by checking if we are realized and explicitly calling the signal handler if so. [ QA ] Have multiple monitors. Have only one of them connected. Log in. Plug in one monitor. If it's autoactivated, check you see your background on both monitors. If not, activate it ("Displays") and do the same. [ Regression potential ] I'm not sure why or where the order changed to make the widget be realized earlier, if it matters or if this was always buggy and we got lucky. I would guess a refactoring in Nautilus itself, and so the proposed fix is safe, but watch out for other weirdness. [ Original description ] Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Graphic chips: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] [10de:139b] (rev ff) Desktop wallpaper on extended display shows black background only, and the hdmi detection is very unstable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 23 05:30:30 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-09-20 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
[Desktop-packages] [Bug 1274115] Re: snd_pcm_avail() returned a value that is exceptionally large
More info: I have the same bug. Lenovo X1 yoga. Laptop becomes completely unresponsive. ubuntu 16.04, kernel 4.4.0-47-generic, pulsaudo Anyone found a way out? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1274115 Title: snd_pcm_avail() returned a value that is exceptionally large Status in pulseaudio package in Ubuntu: Confirmed Bug description: Sometimese sound begins stutter while listen to music or watching youtube. In syslog I see: Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 866944 bytes (4914 ms). Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. I'm using Kubuntu 13.10 $ uname -a Linux bazilio-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ kde4-config --version Qt: 4.8.4 KDE Development Platform: 4.12.0 kde4-config: 1.0 $ pulseaudio --version pulseaudio 4.0 $ alsactl --version alsactl version 1.0.27.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1274115] Re: snd_pcm_avail() returned a value that is exceptionally large
I have the same bug. Lenovo X1 yoga. Laptop becomes completely unresponsive. Anyone found a way out? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1274115 Title: snd_pcm_avail() returned a value that is exceptionally large Status in pulseaudio package in Ubuntu: Confirmed Bug description: Sometimese sound begins stutter while listen to music or watching youtube. In syslog I see: Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 866944 bytes (4914 ms). Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. I'm using Kubuntu 13.10 $ uname -a Linux bazilio-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ kde4-config --version Qt: 4.8.4 KDE Development Platform: 4.12.0 kde4-config: 1.0 $ pulseaudio --version pulseaudio 4.0 $ alsactl --version alsactl version 1.0.27.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
Uploaded, thank you! ** Also affects: appstream (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: appstream (Ubuntu Xenial) Status: New => In Progress ** Changed in: appstream (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: appstream (Ubuntu Xenial) Assignee: (unassigned) => Matthias Klumpp (ximion) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Bug description: [Impact] * The recent update of the Ubuntu asgen instance yielded it to generate modern metadata. While we could tell asgen to generate old- style metadata, fixing appstream is the better idea, since we already applied similar patches to appstream-glib (and having this package hold back updates is a bad idea). Currently, the unknown metadata is considered to be broken by appstream and it displays a warning about that issue during an `apt update` * The attached patch includes a second change to make AppStream more robust against broken YAML data, ensuring LP #1579712 can not be triggered on purpose or due to broken disks creating damaged YAML structure. [Test Case 1] * apt update * Check for errors about metadata being ignored [Test Case 2] * appstreamcli refresh --force * Check for errors about metadata being ignored * Check if we ignored data that should be present (search for it via `appstreamcli search `) * Run `appstreamcli status` and see if we still have information on the same amount of components as prior to the update. [Regression Potential] * Medium; The works case would be KDE Discover and GNOME Software loosing information on available software, but this risk is very low and the patch to fix this bug is very simple and has almost no regression potential. The YAML parser fix patch is a bit more complex, but should have no sideeffects. [Original report] Periodically I get emails from a machine with the subject: Cronif [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi And a body of: AppStream cache update completed, but some metadata was ignored due to errors. I have a machine monitored by Munin. One of the plugins used on that machine is /etc/munin/plugins/apt which periodically counts the number of packets that can be upgraded. This is achieved by a crontab entry installed from the package which looks like this: # # cron-jobs for munin-node # MAILTO=root # If the APT plugin is enabled, update packages databases approx. once # an hour (12 invokations an hour, 1 in 12 chance that the update will # happen), but ensure that there will never be more than two hour (7200 # seconds) interval between updates.. */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi For many months everything has been running smoothly. On the 23rd November 2016 I started getting the "AppStream cache update completed, but some metadata was ignored due to errors." messages at a rate of about ten a day. I did a quick Google search which turned up a handful of bugs from earlier this year, such as Bug1575248. That is marked as Fixed Released though, so I am raising this new bug. If there are any further diagnostic details I can provide, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 09:57:18 2016 InstallationDate: Installed on 2013-05-08 (1295 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508) JournalErrors: -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 GMT. -- Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SourcePackage: appstream UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1615044] Re: "unmanaged-devices=" lists misbehaves with "except:"
** Changed in: network-manager (Ubuntu) Assignee: Martin Pitt (pitti) => (unassigned) -- 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/1615044 Title: "unmanaged-devices=" lists misbehaves with "except:" Status in network-manager package in Ubuntu: Triaged Bug description: In yakkety we now ship /usr/lib/NetworkManager/conf.d/10-globally- managed-devices.conf with unmanaged-devices=*,except:type:wifi,except:type:wwan but this now breaks conf.d snippets which want to blacklist an additional interface, such as /run/NetworkManager/conf.d/test- blacklist.conf that does unmanaged-devices+=wlan0 resulting in # NetworkManager --print-config [...] unmanaged-devices=*,except:type:wifi,except:type:wwan,wlan0 Intuitively this should ignore wlan0 and all other non-wifi/wwan devices, but with that it *does* manage wlan0. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: i3 Date: Fri Aug 19 18:23:02 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback source-directory interfaces.d NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1615044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1644813] Re: Simple Scan uses a headerbar in Cinnamon
This bug was fixed in the package simple-scan - 3.23.2-0ubuntu1 --- simple-scan (3.23.2-0ubuntu1) zesty; urgency=medium * New upstream release: - Add optional tags in PDF output to be more PDF/A compliant - Don't use GtkHeaderBar in Cinnamon (LP: #1644813) * debian/control: - Bump Standards-Version to 3.9.8 (no changes required). -- Robert AncellMon, 28 Nov 2016 23:15:53 +1300 ** Changed in: simple-scan (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1644813 Title: Simple Scan uses a headerbar in Cinnamon Status in Simple Scan: Fix Released Status in simple-scan package in Ubuntu: Fix Released Bug description: Hi, Please add Cinnamon to the list of DEs where a headerbar shouldn't be used. It doesn't fit that environment. In src/ui.vala's load() function: if (is_desktop ("Unity") || is_desktop ("XFCE") || is_desktop ("MATE") || is_desktop ("LXDE")) should be: if (is_desktop ("Unity") || is_desktop ("XFCE") || is_desktop ("MATE") || is_desktop ("LXDE") || is_desktop ("X-Cinnamon") || is_desktop ("Cinnamon")) To reproduce, run: XDG_CURRENT_DESKTOP="X-Cinnamon" simple-scan The expected result is a traditional titlebar+menubar, not a headerbar. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1644813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1312377] Re: libmtp chokes on photos altered by Twitter Android app
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libmtp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1312377 Title: libmtp chokes on photos altered by Twitter Android app Status in libmtp package in Ubuntu: Confirmed Bug description: Whenever I upload a photo to Twitter from my phone and then try to copy the same photo to my Ubuntu machine via MTP, the transfer freezes, along with my file manager (Thunar in my case). Unplugging and reconnecting the phone is the only way to get the file manager working again. Photos that have only been uploaded to other services (Tumblr and Facebook are the ones I have tested), but not to Twitter, do not cause this problem. On one occasion I got a libmtp error message which read "object type doesn't support RepresentativeSampleData..", but I'm not 100% sure that this is related to the same issue. I am attaching two copies of the same photo. One was copied via MTP before I uploaded it to twitter. The other, which was taken after uploading the photo to Twitter, would not transfer via MTP. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libmtp9 1.1.6-20-g1b9f164-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-lowlatency 3.13.9 Uname: Linux 3.13.0-24-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 24 21:06:25 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-22 (244 days ago) InstallationMedia: Ubuntu-Studio 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: libmtp UpgradeStatus: Upgraded to trusty on 2014-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1312377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573959] Re: On-screen text disappears after suspend
Hello I at least have a very similar problem; so close I think it is the (therefore this comment). I have the latest and greatest of Ubuntu (Gnome) 16.04.1 LTS. (It is an upgrade from 14.04 LTS, but I do not know if this has any effect here). The problem started, for me, this month or late October. > uname -s -r -v -m -p -i -o Linux 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux All letters have "disappeared" (ie were not visible anymore) from the affected programs, but not all are affected. In the gnome-terminal it is possible to select the text and where the mouse pointer hovers while selecting you will be able to read the text, but it disappears on next redraw. Some NOT AFFECTED programs (except menus etc): - Firefox (so I was able to do this) - Chromium - Ubuntu Help - xterm - dash (the ubuntu menu) - google calendar (web-app) - (The document part of Libre Office Writer) Some AFFECTED programs: - Nautilus - The desktop - Remmina - gnome-terminal - Thunderbird - ubuntu-software - (All menus and toolbars etc of Libre Office Writer) - All except the document part of the document viewer - eclipse (eclipse-cpp-luna-SR2-linux-gtk-x86_64) - skype (only the system-bar(?) (uppermost bar)) - dropbox (except the settings dialog box) - alarm-clock-applet - gedit (except the document area) (It seems document areas are generally not affected, that excepts the buffer, or "document area", of gnome-terminal) The ctrl+alt+F[1-6] ttys seems to have stopped or not started after printing the following text: --- start of text --- lvmetad is not active yet, using direct activation during sysinit /ev/mapper/ubuntu--vg-root: clean, aaa/ files, /d blocks _ --- end of text --- note: the '_' seems more to be like a cursor than an (overwrite) underscore, but it is not blinking. (the 'a's, 'b's, 'c's, and 'd's are numbers. The number of digits are shown by the number of letters.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1573959 Title: On-screen text disappears after suspend Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: After resuming from a suspend, almost all text on screen is not visible. This includes menu items, text in all three boxes (list of folders, list of e-mails, e-mail body) in Thunderbird (with the curious exception of "ffl" in the File menu), top menu in Chromium (but not the menu obtained by pressing the hamburger button), and the menus produced by clicking items in the system tray. Also, the apport dialog had no text except for a few capital letters. ADDITIONAL INFORMATION: * initctl restart unity-panel-service restarts the panel, but the text is still missing * suspend and resume does not fix the issue * Logging out fixes the issue * Other affected applications: ** Chromium file select dialog ** Terminal (entire window) ** ttys 1-6 (Ctrl+Alt+F1, etc.) ** Document viewer (menus) ** Software Updater ** Rhythmbox ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc ** ubuntu-bug ** Nautilus ** LibreOffice Calc (spreadsheet text contents) ** Firefox * Unity dash is not affected. * Skype is not affected. * Mousing over a button in a dialog correctly shows the text. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 23 12:04:57 2016 DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics Controller [14c0:0075] InstallationDate: Installed on 2015-01-21 (457 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Compal VAW70 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) dmi.bios.date: 07/31/2013 dmi.bios.vendor: Insyde
[Desktop-packages] [Bug 1644813] Re: Simple Scan uses a headerbar in Cinnamon
** Branch linked: lp:~ubuntu-desktop/simple-scan/ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1644813 Title: Simple Scan uses a headerbar in Cinnamon Status in Simple Scan: Fix Released Status in simple-scan package in Ubuntu: Fix Committed Bug description: Hi, Please add Cinnamon to the list of DEs where a headerbar shouldn't be used. It doesn't fit that environment. In src/ui.vala's load() function: if (is_desktop ("Unity") || is_desktop ("XFCE") || is_desktop ("MATE") || is_desktop ("LXDE")) should be: if (is_desktop ("Unity") || is_desktop ("XFCE") || is_desktop ("MATE") || is_desktop ("LXDE") || is_desktop ("X-Cinnamon") || is_desktop ("Cinnamon")) To reproduce, run: XDG_CURRENT_DESKTOP="X-Cinnamon" simple-scan The expected result is a traditional titlebar+menubar, not a headerbar. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1644813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1644813] Re: Simple Scan uses a headerbar in Cinnamon
I've committed that change to trunk, was there an older series this would be useful on? ** Changed in: simple-scan Milestone: None => 3.23.1 ** Changed in: simple-scan Milestone: 3.23.1 => 3.23.2 ** Also affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Changed in: simple-scan Status: Fix Committed => Fix Released ** Changed in: simple-scan (Ubuntu) Status: New => Fix Committed ** Changed in: simple-scan (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1644813 Title: Simple Scan uses a headerbar in Cinnamon Status in Simple Scan: Fix Released Status in simple-scan package in Ubuntu: Fix Committed Bug description: Hi, Please add Cinnamon to the list of DEs where a headerbar shouldn't be used. It doesn't fit that environment. In src/ui.vala's load() function: if (is_desktop ("Unity") || is_desktop ("XFCE") || is_desktop ("MATE") || is_desktop ("LXDE")) should be: if (is_desktop ("Unity") || is_desktop ("XFCE") || is_desktop ("MATE") || is_desktop ("LXDE") || is_desktop ("X-Cinnamon") || is_desktop ("Cinnamon")) To reproduce, run: XDG_CURRENT_DESKTOP="X-Cinnamon" simple-scan The expected result is a traditional titlebar+menubar, not a headerbar. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1644813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1640607] Re: Generate PDF/A compliant documents
Simple Scan 3.23.2 has some PDF/A improvements. The main issue remaining the the "device-specific color spaces" which I haven't worked out how to correctly mark yet.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1640607 Title: Generate PDF/A compliant documents Status in Simple Scan: Triaged Status in simple-scan package in Ubuntu: New Bug description: [Impact] PDF/A [1] is a standard for PDF documents to make them suitable for archiving. The PDF files that simple-scan produces are PDF compliant, but missing some optional fields that are required for PDF/A. [Test Case] 1. Scan a document 2. Save to a PDF file 3. Check document through a PDF validator (e.g. [2]) Expected result: The generated document is compliant with PDF/A Observed result: The document is not compliant. [Regression potential] Some risk of PDF changes making files saved from Simple Scan not viewable in a PDF reader. This seems very low as PDF/A is a very commonly used standard. [1] https://en.wikipedia.org/wiki/PDF/A [2] http://www.pdf-tools.com/pdf/validate-pdfa-online.aspx To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1640607/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
(The attached patch solves an introspection ABI mismatch that I overlooked initially) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically Status in appstream package in Ubuntu: Fix Committed Bug description: [Impact] * The recent update of the Ubuntu asgen instance yielded it to generate modern metadata. While we could tell asgen to generate old- style metadata, fixing appstream is the better idea, since we already applied similar patches to appstream-glib (and having this package hold back updates is a bad idea). Currently, the unknown metadata is considered to be broken by appstream and it displays a warning about that issue during an `apt update` * The attached patch includes a second change to make AppStream more robust against broken YAML data, ensuring LP #1579712 can not be triggered on purpose or due to broken disks creating damaged YAML structure. [Test Case 1] * apt update * Check for errors about metadata being ignored [Test Case 2] * appstreamcli refresh --force * Check for errors about metadata being ignored * Check if we ignored data that should be present (search for it via `appstreamcli search `) * Run `appstreamcli status` and see if we still have information on the same amount of components as prior to the update. [Regression Potential] * Medium; The works case would be KDE Discover and GNOME Software loosing information on available software, but this risk is very low and the patch to fix this bug is very simple and has almost no regression potential. The YAML parser fix patch is a bit more complex, but should have no sideeffects. [Original report] Periodically I get emails from a machine with the subject: Cronif [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi And a body of: AppStream cache update completed, but some metadata was ignored due to errors. I have a machine monitored by Munin. One of the plugins used on that machine is /etc/munin/plugins/apt which periodically counts the number of packets that can be upgraded. This is achieved by a crontab entry installed from the package which looks like this: # # cron-jobs for munin-node # MAILTO=root # If the APT plugin is enabled, update packages databases approx. once # an hour (12 invokations an hour, 1 in 12 chance that the update will # happen), but ensure that there will never be more than two hour (7200 # seconds) interval between updates.. */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi For many months everything has been running smoothly. On the 23rd November 2016 I started getting the "AppStream cache update completed, but some metadata was ignored due to errors." messages at a rate of about ten a day. I did a quick Google search which turned up a handful of bugs from earlier this year, such as Bug1575248. That is marked as Fixed Released though, so I am raising this new bug. If there are any further diagnostic details I can provide, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 09:57:18 2016 InstallationDate: Installed on 2013-05-08 (1295 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508) JournalErrors: -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 GMT. -- Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SourcePackage: appstream UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
Yes, Yakkety and Zesty are not affected. ** Patch added: "appstream_0.9.4-1ubuntu2_LP1644498_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+attachment/4784052/+files/appstream_0.9.4-1ubuntu2_LP1644498_v2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically Status in appstream package in Ubuntu: Fix Committed Bug description: [Impact] * The recent update of the Ubuntu asgen instance yielded it to generate modern metadata. While we could tell asgen to generate old- style metadata, fixing appstream is the better idea, since we already applied similar patches to appstream-glib (and having this package hold back updates is a bad idea). Currently, the unknown metadata is considered to be broken by appstream and it displays a warning about that issue during an `apt update` * The attached patch includes a second change to make AppStream more robust against broken YAML data, ensuring LP #1579712 can not be triggered on purpose or due to broken disks creating damaged YAML structure. [Test Case 1] * apt update * Check for errors about metadata being ignored [Test Case 2] * appstreamcli refresh --force * Check for errors about metadata being ignored * Check if we ignored data that should be present (search for it via `appstreamcli search `) * Run `appstreamcli status` and see if we still have information on the same amount of components as prior to the update. [Regression Potential] * Medium; The works case would be KDE Discover and GNOME Software loosing information on available software, but this risk is very low and the patch to fix this bug is very simple and has almost no regression potential. The YAML parser fix patch is a bit more complex, but should have no sideeffects. [Original report] Periodically I get emails from a machine with the subject: Cronif [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi And a body of: AppStream cache update completed, but some metadata was ignored due to errors. I have a machine monitored by Munin. One of the plugins used on that machine is /etc/munin/plugins/apt which periodically counts the number of packets that can be upgraded. This is achieved by a crontab entry installed from the package which looks like this: # # cron-jobs for munin-node # MAILTO=root # If the APT plugin is enabled, update packages databases approx. once # an hour (12 invokations an hour, 1 in 12 chance that the update will # happen), but ensure that there will never be more than two hour (7200 # seconds) interval between updates.. */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi For many months everything has been running smoothly. On the 23rd November 2016 I started getting the "AppStream cache update completed, but some metadata was ignored due to errors." messages at a rate of about ten a day. I did a quick Google search which turned up a handful of bugs from earlier this year, such as Bug1575248. That is marked as Fixed Released though, so I am raising this new bug. If there are any further diagnostic details I can provide, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 09:57:18 2016 InstallationDate: Installed on 2013-05-08 (1295 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508) JournalErrors: -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 GMT. -- Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SourcePackage: appstream UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639568] Re: dnsmasq not updated by NetworkManager on system resume
I have the same issue when e.g.: - switching from Ethernet (via a USB-to-Ethernet adapter) and WiFi - turning on or off a VPN managed by NetworkManager (openvpn configured manually does not have the issue) My current workaround is to killall dnsmasq as root. It will re-start automatically with the updated settings. -- 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/1639568 Title: dnsmasq not updated by NetworkManager on system resume Status in network-manager package in Ubuntu: Confirmed Bug description: When the system resumes after sleep dnsmasq is either not updated with new dns information of never resumes operation. Restarting the network-manager service will manually resolve the problem. Everything else seems correct, the DHCP information is correct and shows the correct nameservers, resolv.conf is updated correctly. I am unable to determine if the issue is with dnsmasq not resuming or if the dbus message with the name servers is getting lost. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 6 07:24:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-03 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.218 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 The_Magical_Mystery_Tour 4e4fe235-20a0-414a-8ec3-97f65060250e /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1639568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639568] Re: dnsmasq not updated by NetworkManager on system resume
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1639568 Title: dnsmasq not updated by NetworkManager on system resume Status in network-manager package in Ubuntu: Confirmed Bug description: When the system resumes after sleep dnsmasq is either not updated with new dns information of never resumes operation. Restarting the network-manager service will manually resolve the problem. Everything else seems correct, the DHCP information is correct and shows the correct nameservers, resolv.conf is updated correctly. I am unable to determine if the issue is with dnsmasq not resuming or if the dbus message with the name servers is getting lost. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 6 07:24:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-03 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.218 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 The_Magical_Mystery_Tour 4e4fe235-20a0-414a-8ec3-97f65060250e /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1639568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp