[Desktop-packages] [Bug 1614050] Re: Window depth order messed up
Cui Wei, can you please first confirm that it fixes your issue? ** Also affects: metacity (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1614050 Title: Window depth order messed up Status in metacity package in Ubuntu: Fix Released Status in metacity source package in Xenial: New Bug description: Using the gome-flashback session with metacity is totally messed up since I updated from Ubuntu 14.04.3 to 16.04.1. All the effects mentioned here do not appear when using compiz, so I guess Metacity is broken. -Windows that should open in front (like Kupfer) appear behind the windows already open. -Before nemo is run, the Ubuntu default desktop background image appear, it can't be changed by settings. I just guess this is due wrong ordering of the true background and some window used by Gnome for showing the selected background. -If nemo is run to take over the desktop, the destkop icons appear in front of all windows. I guess all those effects originate from a similiar reason. None of these problems where appearant at Ubuntu 14.04. This is a total show stopper for using metacity on 16.04 as everyday applications like nemo and Kupfer can't be used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1614050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 887821] Re: "Show copy dialog" right click launcher entry doesn't work (on nautilus copy)
** Attachment removed: "Monitor for windows with certain title and strip them of "skip_taskbar" property." https://bugs.launchpad.net/ubuntu/+source/unity/+bug/887821/+attachment/4754095/+files/fix_skip_taskbar.sh ** Attachment added: "Monitor for windows with certain title and strip them of "skip_taskbar" property." https://bugs.launchpad.net/ubuntu/+source/unity/+bug/887821/+attachment/4754702/+files/fix_skip_taskbar.sh -- 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/887821 Title: "Show copy dialog" right click launcher entry doesn't work (on nautilus copy) Status in Unity: Fix Released Status in Unity 5.0 series: Won't Fix Status in nautilus package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in nautilus source package in Precise: Fix Released Status in unity source package in Precise: Invalid Bug description: Impact: the nautilus copy dialog don't get properly focussed by unity Test Case: - log into an unity session - copy a not too small file (so you have time to interact with the copy dialog) - minimize the copy dialog - right click on the corresponding unity-launcher's icon, and pick "show copy dialog" -> the dialog should be displayed Regression testing: Check that there is no focus issue with that dialog and the launcher -- While copying a large (8 gig) file across an SMB network, I minimized it. The right click on the Nautilus Unity bar showed a "Show copy dialog" item. Clicking on that item did nothing. The only way to get the dialog back up was to open one of the two minimized Nautilus windows and then minimize the one on top. After that minimize, then the copy dialog was displayed on top of the other Nautilus window. I couldn't find any way to get the copy dialog back on screen without clicking around somewhat aimlessly displaying and minimizing Nautilus windows until it appeared. The "Show copy dialog" right-click menu appeared to have no affect. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Nov 8 18:12:10 2011 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: PATH=(custom, no user) 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/unity/+bug/887821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630447] [NEW] Whole day events are shown a day before
Public bug reported: If I create a full day event on the 3rd december of 2016 (for example), it appears a day before (the 2nd december). If I edit this event on 3rd december 2016 from 00:00 pm till 23:59 pm, it works! The bug arrive when I use the full day option ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1630447 Title: Whole day events are shown a day before Status in gnome-calendar package in Ubuntu: New Bug description: If I create a full day event on the 3rd december of 2016 (for example), it appears a day before (the 2nd december). If I edit this event on 3rd december 2016 from 00:00 pm till 23:59 pm, it works! The bug arrive when I use the full day option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1630447/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1614050] Re: Window depth order messed up
I am not sure whether it is indeed fixed without a long-term testing procedure, but I could say that didn't encounter this issue again after using it for 4-5 days. So at least, the ppa version with this patch is no-doubt more stable that the current one in ubuntu mainstream repository. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1614050 Title: Window depth order messed up Status in metacity package in Ubuntu: Fix Released Status in metacity source package in Xenial: New Bug description: Using the gome-flashback session with metacity is totally messed up since I updated from Ubuntu 14.04.3 to 16.04.1. All the effects mentioned here do not appear when using compiz, so I guess Metacity is broken. -Windows that should open in front (like Kupfer) appear behind the windows already open. -Before nemo is run, the Ubuntu default desktop background image appear, it can't be changed by settings. I just guess this is due wrong ordering of the true background and some window used by Gnome for showing the selected background. -If nemo is run to take over the desktop, the destkop icons appear in front of all windows. I guess all those effects originate from a similiar reason. None of these problems where appearant at Ubuntu 14.04. This is a total show stopper for using metacity on 16.04 as everyday applications like nemo and Kupfer can't be used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1614050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot
This issue affected me with a new Dell E5470 on 14.04 The issue would go away with a factory reset but after doing updates it would reappear. The way I eventually got it fixed was Step 1: as stated above Edit file /etc/dbus-1/system.d/org.freedesktop.UPower.conf change: to: Step 2: Bios In my bios file I had to find the settings for the keyboard timeout and change it to something else. So if it was set to 5 seconds then I had to change it to 10 seconds. If it was set to 10 seconds then I had to change it to 5 seconds. Once I rebooted my system the keyboard returned to the expected behavior. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1510344 Title: Keyboard Backlight Turns on at boot Status in Dell Sputnik: Confirmed Status in gnome-settings-daemon: Fix Released Status in One Hundred Papercuts: Confirmed Status in Linux: Invalid Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon source package in Xenial: Fix Released Bug description: System: Dell XPS 13 9343 Action: Boot computer Expected Behavior: Keyboard backlight would be off when computer is booted Actual Behavior: Keyboard backlight is on at boot This did not happen with Ubuntu 15.04 There are new files in Ubuntu 15.10 - /sys/class/leds/dell::kbd_backlight$ cat stop_timeout 60s cat start_triggers +keyboard +touchpad cat trigger [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 rfkill0 cat brightness 2 --- Unsure if these files are important, but included in the report ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-2-generic 4.1.0-2.2 ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3 Uname: Linux 4.1.0-2-generic x86_64 ApportVersion: 2.18-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2488 F pulseaudio /dev/snd/controlC0: ubuntu 2488 F pulseaudio CasperVersion: 1.362 CurrentDesktop: Unity Date: Tue Oct 27 01:29:47 2015 IwConfig: enx00249b0981e3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt RelatedPackageVersions: linux-restricted-modules-4.1.0-2-generic N/A linux-backports-modules-4.1.0-2-generic N/A linux-firmware 1.145 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
In contrast this is what is happening with Xenial, which works perfectly. evtest: Event: time 1475641421.193234, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 1 Event: time 1475641421.193234, -- SYN_REPORT Event: time 1475641421.193306, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 0 Event: time 1475641421.193306, -- SYN_REPORT udev monitoring in the attachment. ** Attachment added: "udev.xenial.txt" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4754687/+files/udev.xenial.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1626651 Title: brightness keys are handled slower in Yakkety than Xenial Status in policykit-1 package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Bug description: I've noticed on Lenovo X220 and X230 laptops that pressing brightness keys on Yakkety seems less responsive and slower than Xenial. I ran forkstat on Xenial and just observed udev being forked off: Xenial: $ sudo forkstat Time Event PID Info Duration Process 17:37:35 fork273 parent /lib/systemd/systemd-udevd 17:37:35 fork 1977 child /lib/systemd/systemd-udevd 17:37:35 exit 1977 00.008 /lib/systemd/systemd-udevd Whereas on Yakkety, there is far more activity: Time Event PID Info Duration Process 16:35:34 fork 2626 parent update-notifier 16:35:34 fork 2645 child update-notifier 16:35:34 exec 2645 /usr/bin/python3 /usr/share/apport/apport-checkreports 16:35:34 exit 26452560.221 /usr/bin/python3 /usr/share/apport/apport-checkreports 16:35:34 fork 2626 parent update-notifier 16:35:34 fork 2646 child update-notifier 16:35:34 exec 2646 /usr/bin/python3 /usr/share/apport/apport-checkreports --system 16:35:34 exit 26462560.188 /usr/bin/python3 /usr/share/apport/apport-checkreports --system 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2647 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2647 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 exit 2647 00.008 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2648 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2648 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 exit 2648 00.006 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2649 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2649 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 exit 2649 00.007 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2650 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2650 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 exit 2650 00.006 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2651 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2651 pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2651 parent pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2652 thread pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2651 parent pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2653 thread pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 fork 1 parent /sbin/init splash 16:35:36 fork 2654 child /sbin/init splash Time Event PID Info Duration Process 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2655 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2656 child
[Desktop-packages] [Bug 1620313] Re: stop using hardening-wrapper, obsoleted by recent dpkg-dev
** Also affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Also affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Also affects: proftpd-dfsg (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-push-qml (Ubuntu) Importance: Undecided Status: New -- 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/1620313 Title: stop using hardening-wrapper, obsoleted by recent dpkg-dev Status in firefox package in Ubuntu: In Progress Status in gtk2-engines-murrine package in Ubuntu: Fix Released Status in lxc package in Ubuntu: New Status in pidgin package in Ubuntu: New Status in proftpd-dfsg package in Ubuntu: New Status in thunderbird package in Ubuntu: New Status in ubuntu-push-qml package in Ubuntu: New Status in unity-control-center package in Ubuntu: New Status in hardening-wrapper package in Debian: Fix Released Bug description: stop using hardening-wrapper, obsoleted by recent dpkg-dev. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1620313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443590] Re: Not updated to latest upstream
** Changed in: lirc Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1443590 Title: Not updated to latest upstream Status in LIRC: Fix Released Status in lirc package in Ubuntu: Triaged Bug description: I am filing the same bug against Ubuntu as Alec Leamas (upstream lirc maintainer) did against Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777199 ===begin=== The lirc sources used (0.9.0-pre1) is now very old (2011), lagging two major and several minor releases behind upstream. I'm filing this in my capacity as the upstream maintainer. The very old sources used by Debian are becoming a problem also for us, since it makes a substantial part of the user base using sources we don't maintain any more. I'm perfectly aware that the decision to update, to what and when, is up to the Debian maintainers. That said, if I as the upstream could make anything to make an update easier, please let me know. --alec leamas ===end=== To manage notifications about this bug go to: https://bugs.launchpad.net/lirc/+bug/1443590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 694293] Re: Printing PDF containing png graphic results in bad text quality (pixelized)
** Tags added: natty oneiric yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/694293 Title: Printing PDF containing png graphic results in bad text quality (pixelized) Status in poppler package in Ubuntu: Confirmed Bug description: When printing a PDF containing a graphic in png format the print quality of that text is badly reduced. I realized this issue when I got a new color printer (Brother DCP-9045CDN). Text is printed badly pixelized looking like 150dpi (without hinting). Printing the same text containing a jpg (or without) graphic instead of a png does not show this problem and text is printed just fine. Printing the original document (incl png) directly from OpenOffice or printing the PDF with png from Windows with Acrobat Reader or OSX with preview works fine as well Not a printer or driver issue After some more investigation I realized that the problem also appears on other printers (tested with Brother HL-5250 and HP LaserJet 1210). Much less pronounced thought and therefore I haven't realized it before. Directly comparing the print out quality of PDF with png vs. one with jpg shows a slightly reduced text quality. Screen rendering is fine in both cases, even when zooming in. Is it not the application, its deeper in the stack I used Okular to print the PDF but I also tested XPDF which shows the same behaviour. Using Acrobat Reader it prints "fine" but with a lower over all quality (looks like the document is turned into a picture before being sent to the printer). Without being a specialist I assume that the problem is the PDF processing (poppler?) before its sent to the printer (Acrobat seems to use something different there). I can provide example documents if required as well as print out examples. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/694293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630349] Re: libwebp ftbfs on armhf
It would appear, though, that libwebp has neon support, it just needs to be modified (configure script) to detect it properly, rather than relying on the header's existence. The code has runtime neon detection, so it should be safe to compile-in, if hte compiler supports the optoin. ** Changed in: libwebp (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/1630349 Title: libwebp ftbfs on armhf Status in libwebp package in Ubuntu: In Progress Bug description: https://launchpadlibrarian.net/285964171/buildlog_ubuntu-yakkety- armhf.libwebp_0.5.1-2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1630349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624022] Re: Alias 'browse' to xdg-open
Forwarded to Debian yet? ** Changed in: xdg-utils (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1624022 Title: Alias 'browse' to xdg-open Status in xdg-utils package in Ubuntu: Fix Released Status in xdg-utils source package in Xenial: Fix Committed Bug description: [Impact] The 'sensible-browser' and 'xdg-open' commands are very useful, but it's a bit unwieldy to use everywhere in docs. How about aliasing to the simple 'browse', so I can recommend things like: sudo apt install foo; browse http://locahost:2022/ That would be crisp clean and friendly for current users. [Test Case] There is currently no simple 'browse' command. [Regression Potential] None. There are no name collisions with /usr/bin/browse in Debian or Ubuntu. [ Other Info ] Although the original request was to alias 'sensible-browser' it was decided that 'xdg-open' has the more consistent behaviour (in terms of selecting the correct web browser to use) and also falls back to 'sensible-browser'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1624022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1625877] Re: VLC screen always on top
Christopher M. Penalver Sorry about that, I test again with 16.10(daily build) and 14.04 with same hardware. everything work normally. -- 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/1625877 Title: VLC screen always on top Status in xorg package in Ubuntu: Incomplete Bug description: After new installed VLC on 16.04 The video screen always on top only while playing with VLC the interface disappeared while minimum VLC (video playing) video screen remains only but the situation is fixed after canceled the option "Accelerated video output(Overlay)" in Preference > Video > Display Reference: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-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 CurrentDesktop: Unity Date: Wed Sep 21 09:23:57 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6588] InstallationDate: Installed on 2016-09-01 (19 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5b0 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: COPELION INTERNATIONAL CO., LTD. SY Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=5e244808-04fe-428e-993a-b6260daede38 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: SY Series dmi.board.vendor: COPELION INTERNATIONAL CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/09/2016:svnCOPELIONINTERNATIONALCO.,LTD.:pnSYSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALCO.,LTD.:rnSYSeries:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: SY Series dmi.product.version: Not Applicable dmi.sys.vendor: COPELION INTERNATIONAL CO., LTD. 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.3-1ubuntu2.3 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 Sep 20 22:21:24 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1191 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406810] Re: [iMac11,1] Unable to boot
iMac11,1 (RV770/M98L [Mobility Radeon HD 4850]) needs nomodeset to boot https://bugs.freedesktop.org/show_bug.cgi?id=98046 ** Bug watch added: freedesktop.org Bugzilla #98046 https://bugs.freedesktop.org/show_bug.cgi?id=98046 -- 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/1406810 Title: [iMac11,1] Unable to boot Status in xorg package in Ubuntu: Triaged Bug description: I'm unable to boot. WORKAROUND: Use kernel parameter: nomodeset The causes a sluggish display and an inability to wake up the screen after going to sleep. --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770/M98L [Mobility Radeon HD 4850] [1002:944a] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00b5] InstallationDate: Installed on 2015-01-01 (440 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) MachineType: Apple Inc. iMac11,1 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic root=UUID=f19c8f84-1553-4a36-889a-acfb8a13da9a ro ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.13.0-79-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 03/17/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM111.88Z.0034.B02.1003171314 dmi.board.name: Mac-F2268DAE dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268DAE dmi.modalias: dmi:bvnAppleInc.:bvrIM111.88Z.0034.B02.1003171314:bd03/17/10:svnAppleInc.:pniMac11,1:pvr1.0:rvnAppleInc.:rnMac-F2268DAE:rvr:cvnAppleInc.:ct13:cvrMac-F2268DAE: dmi.product.name: iMac11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Mar 16 19:43:11 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: radeon --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-31 (29 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) Package: linux (not installed) Tags: xenial Uname: Linux 4.8.0-040800rc8-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406810/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1203592] Re: Keyboard backlight does not work in Samsung Series 9 NP900X4C
i have the solution contact me in my facebook https://www.facebook.com/badiis1916 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1203592 Title: Keyboard backlight does not work in Samsung Series 9 NP900X4C Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: In Ubuntu 13.04, the keyboard backlight does not work in Samsung Series 9 NP900X4C. Adding the FN key mappings as described in https://help.ubuntu.com/community/SamsungSeries9 does show information in the notification area when pressing the keyboard backlight's + and - buttons, but: 1) The notification always identifies the backlight as "full max" 2) It has no effect on the backlight - it's always off When I first installed Ubuntu on this machine (12.10), even though the fn keys never worked I did have intermitent backlight functionality - the light sensor would sometimes work and I'd see light in the keyboard. I dual boot in Windows 8 and backlighting works there, so this is not a hardware issue. More discussion can be found here: http://askubuntu.com/questions/233312/how-to-make-keyboard-backlight- fn-buttons-work-in-samsung-series-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1203592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630336] Re: NM doesn't scan for wifi networks after hibernation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager-applet (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1630336 Title: NM doesn't scan for wifi networks after hibernation Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Sometimes, after waking up the laptop from hibernation, nm-applet won't scan for networks. In these cases, the list of available Wifis can be just outdated or directly empty. Switching Wireless on/off and Network on/off doesn't trigger a scan. Usually running sudo iwlist scan on a terminal makes the wifi networks available immediately in nm-applet I'm using 16.04 (ubt had the same problem on 15.10) network-manager-gnome: Installed: 1.2.0-0ubuntu0.16.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1630336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630176] Re: Ubuntu version reported wrong in system settings
** Also affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-system-settings (Ubuntu) -- 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/1630176 Title: Ubuntu version reported wrong in system settings Status in unity-control-center package in Ubuntu: New Bug description: https://help.ubuntu.com/community/CheckingYourUbuntuVersion describes two ways of getting your current Ubuntu version: via system settings, and via terminal. For me, those two methods give me a different version (14.04 vs 16.04, see attached screenshot). I upgraded my pre- installed trusty to xenial, so the version printed on terminal is correct. That means that the system settings displays the wrong version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1630176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
** Attachment added: "udev.txt" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4754480/+files/udev.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1626651 Title: brightness keys are handled slower in Yakkety than Xenial Status in policykit-1 package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Bug description: I've noticed on Lenovo X220 and X230 laptops that pressing brightness keys on Yakkety seems less responsive and slower than Xenial. I ran forkstat on Xenial and just observed udev being forked off: Xenial: $ sudo forkstat Time Event PID Info Duration Process 17:37:35 fork273 parent /lib/systemd/systemd-udevd 17:37:35 fork 1977 child /lib/systemd/systemd-udevd 17:37:35 exit 1977 00.008 /lib/systemd/systemd-udevd Whereas on Yakkety, there is far more activity: Time Event PID Info Duration Process 16:35:34 fork 2626 parent update-notifier 16:35:34 fork 2645 child update-notifier 16:35:34 exec 2645 /usr/bin/python3 /usr/share/apport/apport-checkreports 16:35:34 exit 26452560.221 /usr/bin/python3 /usr/share/apport/apport-checkreports 16:35:34 fork 2626 parent update-notifier 16:35:34 fork 2646 child update-notifier 16:35:34 exec 2646 /usr/bin/python3 /usr/share/apport/apport-checkreports --system 16:35:34 exit 26462560.188 /usr/bin/python3 /usr/share/apport/apport-checkreports --system 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2647 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2647 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 exit 2647 00.008 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2648 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2648 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 exit 2648 00.006 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2649 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2649 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 exit 2649 00.007 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2650 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2650 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 exit 2650 00.006 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2651 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2651 pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2651 parent pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2652 thread pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2651 parent pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2653 thread pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 fork 1 parent /sbin/init splash 16:35:36 fork 2654 child /sbin/init splash Time Event PID Info Duration Process 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2655 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2656 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2657 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2658 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2659 child /lib/systemd/systemd-udevd 16:35:36 exit 2659 0
[Desktop-packages] [Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
I have similar problem on Dell XPS 15 (l521x). It is not quick and it seems that for every key-press it's trying to change brightness twice. I'll attach evtest and udev monitor outputs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1626651 Title: brightness keys are handled slower in Yakkety than Xenial Status in policykit-1 package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Bug description: I've noticed on Lenovo X220 and X230 laptops that pressing brightness keys on Yakkety seems less responsive and slower than Xenial. I ran forkstat on Xenial and just observed udev being forked off: Xenial: $ sudo forkstat Time Event PID Info Duration Process 17:37:35 fork273 parent /lib/systemd/systemd-udevd 17:37:35 fork 1977 child /lib/systemd/systemd-udevd 17:37:35 exit 1977 00.008 /lib/systemd/systemd-udevd Whereas on Yakkety, there is far more activity: Time Event PID Info Duration Process 16:35:34 fork 2626 parent update-notifier 16:35:34 fork 2645 child update-notifier 16:35:34 exec 2645 /usr/bin/python3 /usr/share/apport/apport-checkreports 16:35:34 exit 26452560.221 /usr/bin/python3 /usr/share/apport/apport-checkreports 16:35:34 fork 2626 parent update-notifier 16:35:34 fork 2646 child update-notifier 16:35:34 exec 2646 /usr/bin/python3 /usr/share/apport/apport-checkreports --system 16:35:34 exit 26462560.188 /usr/bin/python3 /usr/share/apport/apport-checkreports --system 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2647 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2647 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 exit 2647 00.008 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2648 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2648 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 exit 2648 00.006 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2649 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2649 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 exit 2649 00.007 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2650 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2650 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 exit 2650 00.006 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2651 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2651 pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2651 parent pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2652 thread pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2651 parent pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2653 thread pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 fork 1 parent /sbin/init splash 16:35:36 fork 2654 child /sbin/init splash Time Event PID Info Duration Process 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2655 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2656 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2657 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2658 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2659 child
[Desktop-packages] [Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
** Attachment added: "evdtest.txt" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4754481/+files/evdtest.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1626651 Title: brightness keys are handled slower in Yakkety than Xenial Status in policykit-1 package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Bug description: I've noticed on Lenovo X220 and X230 laptops that pressing brightness keys on Yakkety seems less responsive and slower than Xenial. I ran forkstat on Xenial and just observed udev being forked off: Xenial: $ sudo forkstat Time Event PID Info Duration Process 17:37:35 fork273 parent /lib/systemd/systemd-udevd 17:37:35 fork 1977 child /lib/systemd/systemd-udevd 17:37:35 exit 1977 00.008 /lib/systemd/systemd-udevd Whereas on Yakkety, there is far more activity: Time Event PID Info Duration Process 16:35:34 fork 2626 parent update-notifier 16:35:34 fork 2645 child update-notifier 16:35:34 exec 2645 /usr/bin/python3 /usr/share/apport/apport-checkreports 16:35:34 exit 26452560.221 /usr/bin/python3 /usr/share/apport/apport-checkreports 16:35:34 fork 2626 parent update-notifier 16:35:34 fork 2646 child update-notifier 16:35:34 exec 2646 /usr/bin/python3 /usr/share/apport/apport-checkreports --system 16:35:34 exit 26462560.188 /usr/bin/python3 /usr/share/apport/apport-checkreports --system 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2647 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2647 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 exit 2647 00.008 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2648 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2648 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 exit 2648 00.006 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2649 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2649 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 exit 2649 00.007 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2650 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2650 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 exit 2650 00.006 /usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness 16:35:36 fork 1576 parent /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 fork 2651 child /usr/lib/unity-settings-daemon/unity-settings-daemon 16:35:36 exec 2651 pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2651 parent pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2652 thread pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2651 parent pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 clone 2653 thread pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250 16:35:36 fork 1 parent /sbin/init splash 16:35:36 fork 2654 child /sbin/init splash Time Event PID Info Duration Process 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2655 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2656 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2657 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2658 child /lib/systemd/systemd-udevd 16:35:36 fork233 parent /lib/systemd/systemd-udevd 16:35:36 fork 2659 child /lib/systemd/systemd-udevd 16:35:36 exit 2659
[Desktop-packages] [Bug 1630176] Re: Ubuntu version reported wrong in system settings
@Tim, Can you please run a few commands to make sure that you have an updated 16.04: sudo apt install --reinstall ubuntu-docs sudo apt update sudo apt full-upgrade Then reboot, and let us know if the problem is still present. ** Changed in: unity-control-center (Ubuntu) Status: New => Incomplete -- 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/1630176 Title: Ubuntu version reported wrong in system settings Status in unity-control-center package in Ubuntu: Incomplete Bug description: https://help.ubuntu.com/community/CheckingYourUbuntuVersion describes two ways of getting your current Ubuntu version: via system settings, and via terminal. For me, those two methods give me a different version (14.04 vs 16.04, see attached screenshot). I upgraded my pre- installed trusty to xenial, so the version printed on terminal is correct. That means that the system settings displays the wrong version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1630176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575354] Re: Connecting to VPN times out after 25 seconds if login credentials not entered
Hi, for me this bug is absolutely critical - because it I'm not able to type in credentials since majority of time is taken by connection to server - so I have something like 5-7 secs to write credentials. So basically now I cannot use VPN which is absolutely critical for me. It works fine in 14.04, so why it's broken now - can you fix it with priority? 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/1575354 Title: Connecting to VPN times out after 25 seconds if login credentials not entered Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Connecting to OpenConnect VPN through the Gnome GUI fails because NetworkManager times out while requesting credentials through the GUI form in Ubuntu 16.04. It worked (is working on other computers I'm working on) fine from Ubuntu 12.04-15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-openconnect 1.0.2-1build1 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: GNOME Date: Tue Apr 26 22:06:41 2016 SourcePackage: network-manager-openconnect UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1575354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly
@jim afaict this change to fix the deadlock made it into ota12 at the final hour http://bazaar.launchpad.net/~phablet-team/media-hub/trunk/revision/198 at least ota12 has media-hub version 4.2.0+15.04.20160704-0ubuntu1 Would be worth reviewing it again to see if it could have triggered this symptom. ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: media-hub (Ubuntu) Importance: Undecided => High ** Changed in: media-hub (Ubuntu) Assignee: (unassigned) => Jim Hodapp (jhodapp) ** Changed in: canonical-devices-system-image Assignee: Pat McGowan (pat-mcgowan) => John McAleely (john.mcaleely) -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Attached is a debdiff for gtk+2.0 (Yakkety) that adds a patch to explicitly disconnect keymap signals. ** Patch added: "gtk2-yakkety-explicitly-disconnect-keymap-signals.diff" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1576424/+attachment/4754403/+files/gtk2-yakkety-explicitly-disconnect-keymap-signals.diff -- 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: In Progress 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 1630349] Re: libwebp ftbfs on armhf
I found a reference to a similar issue in openal-soft_1:1.16.0-3 from earlier this year. http://gcc.1065356.n8.nabble.com/distro-test-rebuild-using- GCC-6-td1224722.html#a1226791 It seems the arm headers have changed how configure should detect neon support, and now the build is falsely detecting neon support, even though it's not passing the required -mfpu=neon flag. Given that neon support was not enabled before, I believe the best choice is to disable it via a configure flag. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/1630349 Title: libwebp ftbfs on armhf Status in libwebp package in Ubuntu: In Progress Bug description: https://launchpadlibrarian.net/285964171/buildlog_ubuntu-yakkety- armhf.libwebp_0.5.1-2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1630349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630349] [NEW] libwebp ftbfs on armhf
Public bug reported: https://launchpadlibrarian.net/285964171/buildlog_ubuntu-yakkety- armhf.libwebp_0.5.1-2_BUILDING.txt.gz ** Affects: libwebp (Ubuntu) Importance: Undecided Assignee: Nish Aravamudan (nacc) Status: In Progress ** Changed in: libwebp (Ubuntu) Status: New => In Progress ** Changed in: libwebp (Ubuntu) Assignee: (unassigned) => Nish Aravamudan (nacc) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/1630349 Title: libwebp ftbfs on armhf Status in libwebp package in Ubuntu: In Progress Bug description: https://launchpadlibrarian.net/285964171/buildlog_ubuntu-yakkety- armhf.libwebp_0.5.1-2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1630349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630336] [NEW] NM doesn't scan for wifi networks after hibernation
Public bug reported: Sometimes, after waking up the laptop from hibernation, nm-applet won't scan for networks. In these cases, the list of available Wifis can be just outdated or directly empty. Switching Wireless on/off and Network on/off doesn't trigger a scan. Usually running sudo iwlist scan on a terminal makes the wifi networks available immediately in nm-applet I'm using 16.04 (ubt had the same problem on 15.10) network-manager-gnome: Installed: 1.2.0-0ubuntu0.16.04.4 ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1630336 Title: NM doesn't scan for wifi networks after hibernation Status in network-manager-applet package in Ubuntu: New Bug description: Sometimes, after waking up the laptop from hibernation, nm-applet won't scan for networks. In these cases, the list of available Wifis can be just outdated or directly empty. Switching Wireless on/off and Network on/off doesn't trigger a scan. Usually running sudo iwlist scan on a terminal makes the wifi networks available immediately in nm-applet I'm using 16.04 (ubt had the same problem on 15.10) network-manager-gnome: Installed: 1.2.0-0ubuntu0.16.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1630336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630309] [NEW] plasma panel auto hide - panel disappears and does not come back
Public bug reported: I have to open plasmashellrc and set planelVisibility to 0 to make it return. Simple reboot doesn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-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: None CurrentDesktop: KDE Date: Tue Oct 4 13:33:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0591] InstallationDate: Installed on 2016-07-27 (68 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=11cb0acd-e2d1-4040-8e64-08167dfa22cf ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/07/2014:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. 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.3-1ubuntu2.3 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 Oct 4 08:52:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5238 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu third-party-packages 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/1630309 Title: plasma panel auto hide - panel disappears and does not come back Status in xorg package in Ubuntu: New Bug description: I have to open plasmashellrc and set planelVisibility to 0 to make it return. Simple reboot doesn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-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: None CurrentDesktop: KDE Date: Tue Oct 4 13:33:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0591] InstallationDate: Installed on 2016-07-27 (68 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=11cb0acd-e2d1-4040-8e64-08167dfa22cf ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/07/2014:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz
[Desktop-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
I'm the proud owner of a Acer Aspire VN7-792G Nitro and I'm encountering the same internal microphone problem. I've carefully read all the posts above and I focused on the link in comment #13. One thing seems to me pretty sure: snd_soc_skl won't detect hardware on the above mentioned machine because the later has Intel SST named "Sunrise Point-H" (ID: 8086:A170), which is not supported by the snd_soc_skl driver (only Sunrise Point-LP 8086:9D70 is listed). I'm pretty convinced an entry for Sunrise Point-H must be added to skylake/skl.c. I've tried locally updating as above: the snd_soc_skl driver then recognizes the device. However this is not sufficient: there are probably additional things to do to make it work... or maybe this is a conflict with snd_hda_intel ??? This is out of my current knowledge. I hope this helps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock
Attached is a debdiff for gtk+2.0 (Xenial) that adds a patch to explicitly disconnect keymap signals. ** Patch added: "gtk2-xenial-explicitly-disconnect-keymap-signals.diff" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1576424/+attachment/4754404/+files/gtk2-xenial-explicitly-disconnect-keymap-signals.diff ** Description changed: + [Impact] + Gimp crashes with a segfault when I use caps lock while renaming a - layer. Steps to reproduce: + 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. ** Tags added: patch -- 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: In Progress 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
[Desktop-packages] [Bug 1630324] [NEW] Broadcom wifi dies in 60s cycles with 4.8 kernel
Public bug reported: I have a Dell XPS 13 9350 with a Broadcom wifi adapter. Wifi connects fine, but dies for around 5-10s (the signal dies completely, tools like wavemon show "no interface data") in regular cycles of about 60s. dmesg logs the same brcmfmac errors every minute or so: "brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)". network-manager's icon doesn't change however (remains as if the adapter was connected). This issue started to affect me when using kernel 4.8 on Ubuntu 16.04. I previously used kernel 4.7 and did not experience this bug. I booted the 16.10 daily build and experienced exactly the same errors. $ lspci | grep BCM4350 3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless Network Adapter (rev 08) $ dmesg | grep brcm [5.864558] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 22 2015 06:16:26 version 7.35.180.119 (r594535) FWID 01-e791c176 [5.898803] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 74.991987] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 142.503220] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) ... $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 Uname: Linux 4.8.0-040800-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 4 14:15:02 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-26 (131 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.0.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 192.168.0.0/24 dev wlp58s0 proto kernel scope link src 192.168.0.29 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 CONNECTION CON-UUID CON-PATH wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 Guava Guest 1 68ae8dc2-ab23-42ef-9e41-ac8e9d91385a /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Summary changed: - wifi connection dies intermittently in 60s cycles + Broadcom wifi dies in 60s cycles with 4.8 kernel -- 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/1630324 Title: Broadcom wifi dies in 60s cycles with 4.8 kernel Status in network-manager package in Ubuntu: New Bug description: I have a Dell XPS 13 9350 with a Broadcom wifi adapter. Wifi connects fine, but dies for around 5-10s (the signal dies completely, tools like wavemon show "no interface data") in regular cycles of about 60s. dmesg logs the same brcmfmac errors every minute or so: "brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)". network-manager's icon doesn't change however (remains as if the adapter was connected). This issue started to affect me when using kernel 4.8 on Ubuntu 16.04. I previously used kernel 4.7 and did not experience this bug. I booted the 16.10 daily build and experienced exactly the same errors. $ lspci | grep BCM4350 3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless Network Adapter (rev 08) $ dmesg | grep brcm [5.864558] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 22 2015 06:16:26 version 7.35.180.119 (r594535) FWID 01-e791c176 [5.898803] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 74.991987] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) [ 142.503220] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30) ... $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 Uname: Linux 4.8.0-040800-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 4 14:15:02 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback
[Desktop-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock
** Changed in: gtk+2.0 (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: gtk+2.0 (Ubuntu) Status: Confirmed => In Progress ** Changed in: gtk+2.0 (Ubuntu) Importance: Undecided => High -- 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: In Progress 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 1629668] Re: [regression] Some Display settings have gone missing: Scale, Launcher placement
gnome-session (3.20.2-1ubuntu6) yakkety; urgency=medium * Set DesktopNames back to Unity. There are many buggy components that don't know how to deal with XDG_CURRENT_DESKTOP having multiple values, and it's too close to the release to fix them all. -- Iain LaneMon, 03 Oct 2016 17:37:57 +0100 ** Changed in: unity-control-center (Ubuntu) Status: Fix Committed => Invalid -- 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/1629668 Title: [regression] Some Display settings have gone missing: Scale, Launcher placement Status in unity-control-center package in Ubuntu: Invalid Bug description: There appear to be other options missing as well. They should be under "General options" but there is nothing there. Ubuntu Yakkety Yak (development branch) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity-control-center 15.04.0+16.10.20160705.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Oct 2 09:56:19 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-09-29 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= 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/unity-control-center/+bug/1629668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP
gnome-session (3.20.2-1ubuntu6) yakkety; urgency=medium * Set DesktopNames back to Unity. There are many buggy components that don't know how to deal with XDG_CURRENT_DESKTOP having multiple values, and it's too close to the release to fix them all. -- Iain LaneMon, 03 Oct 2016 17:37:57 +0100 -- 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/1554878 Title: fix up usage of XDG_CURRENT_DESKTOP Status in GLib: Confirmed Status in Python XDG App: Confirmed Status in empathy package in Ubuntu: Fix Released Status in eog package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in indicator-bluetooth package in Ubuntu: Fix Committed Status in nautilus package in Ubuntu: Fix Released Status in totem package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Committed Status in unity-settings-daemon package in Ubuntu: Fix Committed Status in yelp package in Ubuntu: Fix Released Bug description: Since being standardised XDG_CURRENT_DESKTOP supports specifying multiple Desktop Names seperated by a colon, however many of the patches in Ubuntu pre-date this change so don't correctly support the current format in some cases. These days XDG_CURRENT_DESKTOP will look something like Unity GNOME (gnome-shell) GNOME-Classic:GNOME (gnome-shell classic mode) GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use GNOME-Flashack:GNOME for this) Many of the patches only check for == "Unity" or == "GNOME", so misbehave for the latter cases in the list above. I suspect this will be more widespread than just nautilus, but fixing that would be a good start. Since most of this code is still Ubuntu specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc), probably taking the last value in the string would get the desired result of Unity vs GNOME3 behaviour ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 9 15:04:36 2016 SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1554878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1614050] Re: Window depth order messed up
This bug was fixed in the package metacity - 1:3.20.3-1ubuntu2 --- metacity (1:3.20.3-1ubuntu2) yakkety; urgency=medium * Backport upstream patch to fix stack order handling when windows are unmapped (no_remove_on_unmap.diff, LP: #1614050). -- Dmitry ShachnevTue, 04 Oct 2016 15:57:03 +0300 ** Changed in: metacity (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1614050 Title: Window depth order messed up Status in metacity package in Ubuntu: Fix Released Bug description: Using the gome-flashback session with metacity is totally messed up since I updated from Ubuntu 14.04.3 to 16.04.1. All the effects mentioned here do not appear when using compiz, so I guess Metacity is broken. -Windows that should open in front (like Kupfer) appear behind the windows already open. -Before nemo is run, the Ubuntu default desktop background image appear, it can't be changed by settings. I just guess this is due wrong ordering of the true background and some window used by Gnome for showing the selected background. -If nemo is run to take over the desktop, the destkop icons appear in front of all windows. I guess all those effects originate from a similiar reason. None of these problems where appearant at Ubuntu 14.04. This is a total show stopper for using metacity on 16.04 as everyday applications like nemo and Kupfer can't be used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1614050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629668] Re: [regression] Some Display settings have gone missing: Scale, Launcher placement
Marking invalid since it no longer occurs - it will be fixed by the linked branch ultimately which will allow gnome-session to update XDG_CURRENT_DESKTOP if they want. -- 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/1629668 Title: [regression] Some Display settings have gone missing: Scale, Launcher placement Status in unity-control-center package in Ubuntu: Invalid Bug description: There appear to be other options missing as well. They should be under "General options" but there is nothing there. Ubuntu Yakkety Yak (development branch) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity-control-center 15.04.0+16.10.20160705.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Oct 2 09:56:19 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-09-29 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= 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/unity-control-center/+bug/1629668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
This bug was fixed in the package accountsservice - 0.6.42-0ubuntu1 --- accountsservice (0.6.42-0ubuntu1) yakkety; urgency=medium * New upstream bugfix release. - allow a user to change his own data even if he's remote - add way to set password hint independent of password - conform to modern systemd library naming scheme - disable GVFS support in service, since it's not needed and has bad side effects * Drop patches applied in new version: - 0014-libsystemd.patch - change-own-data-inactive.patch * Add debian/patches/wtmp-fix-logout.patch: - Backport 0.6.43 commit to fix logout records when a user shuts down or restarts their computer (LP: #1443052) -- Jeremy BichaTue, 04 Oct 2016 09:04:41 -0400 ** Changed in: accountsservice (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1628666] Re: Ubuntu Software does not recognize Ubuntu one user / passwords when trying to install snap packages
*** This bug is a duplicate of bug 1616943 *** https://bugs.launchpad.net/bugs/1616943 ** This bug has been marked a duplicate of bug 1616943 Can't auth against U1 in g-s -- 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/1628666 Title: Ubuntu Software does not recognize Ubuntu one user / passwords when trying to install snap packages Status in gnome-software package in Ubuntu: New Bug description: When trying to install VLC using Ubuntu-Software asks me to enter my Ubuntu One account data. In so doing get the message that mail account or password are wrong. To eliminate typing errors I copied the data stored in Firefox that work seamlessly with the web. I also tried changing the password ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubuntu-software 3.20.1+git20160923.2.7374bdc-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 28 16:38:45 2016 InstallationDate: Installed on 2016-09-24 (4 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160914) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1628666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589810] Re: package libcuda1-361 361.45.11-0ubuntu2 failed to install/upgrade: there is no script in the new version of the package - giving up
Confirm this one on 16.04.1. I am open for trying patches. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu. https://bugs.launchpad.net/bugs/1589810 Title: package libcuda1-361 361.45.11-0ubuntu2 failed to install/upgrade: there is no script in the new version of the package - giving up Status in nvidia-graphics-drivers-361 package in Ubuntu: Confirmed Bug description: fails update ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libcuda1-361 361.45.11-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 Date: Tue Jun 7 13:11:49 2016 Dependencies: gcc-6-base 6.1.1-4ubuntu11 libc6 2.23-0ubuntu3 libgcc1 1:6.1.1-4ubuntu11 ErrorMessage: there is no script in the new version of the package - giving up InstallationDate: Installed on 2016-04-24 (43 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.7ubuntu1 apt 1.3~exp1 SourcePackage: nvidia-graphics-drivers-361 Title: package libcuda1-361 361.45.11-0ubuntu2 failed to install/upgrade: there is no script in the new version of the package - giving up UpgradeStatus: Upgraded to yakkety on 2016-05-28 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1589810/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619142] Re: [MRE] Update to 1.18.4
I've been running this on my main desktop for two weeks now without issues. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1619142 Title: [MRE] Update to 1.18.4 Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-lts-xenial package in Ubuntu: Invalid Status in xorg-server source package in Trusty: Invalid Status in xorg-server-lts-xenial source package in Trusty: New Status in xorg-server source package in Xenial: Fix Committed Status in xorg-server-lts-xenial source package in Xenial: Invalid Bug description: Update xserver to new minor release 1.18.4 in order to gain bugfixes from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1619142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly
@Pat: I was looking into this a bit more the other day, reading the attached logs. This no longer seems like a media-hub issue and instead seems more like an issue at one of the higher software layers. If you look at the time in the media-hub logs where Anupam has stated it happened to him, you'll see media-hub try to play the ringtone and then in less than 1 second it pauses it. It won't pause it itself so that means it's most likely a bug at the controlling layer above the media stack. -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1586260] Re: System freeze & no display if set External monitor as primary (Performance mode)
echoing what was mentioned on the private bug that the new version in xenial-proposed fixes the bug ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1586260 Title: System freeze & no display if set External monitor as primary (Performance mode) Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-lts-xenial package in Ubuntu: New Status in xorg-server source package in Trusty: Invalid Status in xorg-server-lts-vivid source package in Trusty: Fix Released Status in xorg-server source package in Xenial: Fix Committed Status in xorg-server source package in Yakkety: Fix Released Bug description: [Impact] System freeze & no display if set External monitor as primary (Performance mode) [Test case] 1. Setup Graphic mode to Performance mode 2. Plug External monitor with HDMI 3. Set display mode to External monitor only is pass 4. Set display mode to Extend/ Mirror mode Expected results: External monitor can be set as primary normally Actual results: System freeze & no display if set External monitor as primary (Performance mode) [Regression potential] Unknown right now, upstream review pending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1586260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP
This bug was fixed in the package indicator-bluetooth - 0.0.6+16.10.20161003-0ubuntu1 --- indicator-bluetooth (0.0.6+16.10.20161003-0ubuntu1) yakkety; urgency=medium [ Robert Ancell ] * Correctly use XDG_CURRENT_DESKTOP (LP: #1554878) -- i...@orangesquash.org.uk (i...@orangesquash.org.uk) Mon, 03 Oct 2016 10:15:04 + ** Changed in: indicator-bluetooth (Ubuntu) Status: Fix Committed => Fix Released -- 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/1554878 Title: fix up usage of XDG_CURRENT_DESKTOP Status in GLib: Confirmed Status in Python XDG App: Confirmed Status in empathy package in Ubuntu: Fix Released Status in eog package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in indicator-bluetooth package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in totem package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Committed Status in unity-settings-daemon package in Ubuntu: Fix Committed Status in yelp package in Ubuntu: Fix Released Bug description: Since being standardised XDG_CURRENT_DESKTOP supports specifying multiple Desktop Names seperated by a colon, however many of the patches in Ubuntu pre-date this change so don't correctly support the current format in some cases. These days XDG_CURRENT_DESKTOP will look something like Unity GNOME (gnome-shell) GNOME-Classic:GNOME (gnome-shell classic mode) GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use GNOME-Flashack:GNOME for this) Many of the patches only check for == "Unity" or == "GNOME", so misbehave for the latter cases in the list above. I suspect this will be more widespread than just nautilus, but fixing that would be a good start. Since most of this code is still Ubuntu specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc), probably taking the last value in the string would get the desired result of Unity vs GNOME3 behaviour ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 9 15:04:36 2016 SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1554878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1614576] Re: Upgrade from xenial to yakkety fails when install policykit-1
It's not really a bug with policykit-1, its just that the upgrader trips over this specific package. ** Package changed: policykit-1 (Ubuntu) => ubuntu-release-upgrader (Ubuntu) ** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => High ** Summary changed: - Upgrade from xenial to yakkety fails when install policykit-1 + Upgrade from xenial to yakkety fails due to a UnicodeDecodeError -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1614576 Title: Upgrade from xenial to yakkety fails due to a UnicodeDecodeError Status in ubuntu-release-upgrader package in Ubuntu: Triaged Bug description: When doing an automated upgrade from xenial to yakkey, I get: Preparing to unpack .../policykit-1_0.105-16_amd64.deb ... Created symlink /run/systemd/system/polkitd.service auto-upgrade [10:48:43]: ERROR: ERROR: Something went wrong with the upgrade. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: policykit-1 0.105-16 ProcVersionSignature: User Name 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 Date: Thu Aug 18 11:02:06 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: Upgraded to yakkety on 2016-08-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1614576/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1614050] Re: Window depth order messed up
Can anyone confirm that version in my ppa does fix problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1614050 Title: Window depth order messed up Status in metacity package in Ubuntu: Confirmed Bug description: Using the gome-flashback session with metacity is totally messed up since I updated from Ubuntu 14.04.3 to 16.04.1. All the effects mentioned here do not appear when using compiz, so I guess Metacity is broken. -Windows that should open in front (like Kupfer) appear behind the windows already open. -Before nemo is run, the Ubuntu default desktop background image appear, it can't be changed by settings. I just guess this is due wrong ordering of the true background and some window used by Gnome for showing the selected background. -If nemo is run to take over the desktop, the destkop icons appear in front of all windows. I guess all those effects originate from a similiar reason. None of these problems where appearant at Ubuntu 14.04. This is a total show stopper for using metacity on 16.04 as everyday applications like nemo and Kupfer can't be used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1614050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
The following is from dbus-update-activation-environment --verbose --systemd $$v; \ systemctl --user show-environment | grep XMODIFIERS; \ initctl set-env -gr $$v=$$(eval "echo \\{v}") || true; \ systemctl --user show-environment | grep XMODIFIERS; \ Oct 04 10:34:56 yakkety-vm sh[1960]: + dbus-update-activation-environment --verbose --systemd XMODIFIERS Oct 04 10:34:56 yakkety-vm sh[1960]: dbus-update-activation-environment: setting XMODIFIERS=@im=ibus Oct 04 10:34:56 yakkety-vm sh[1960]: + grep XMODIFIERS Oct 04 10:34:56 yakkety-vm sh[1960]: + systemctl --user show-environment Oct 04 10:34:56 yakkety-vm sh[1960]: XMODIFIERS=@im=ibus Oct 04 10:34:56 yakkety-vm sh[1960]: + eval echo $XMODIFIERS Oct 04 10:34:56 yakkety-vm sh[1960]: + echo @im=ibus Oct 04 10:34:56 yakkety-vm sh[1960]: + initctl set-env -gr XMODIFIERS=@im=ibus Oct 04 10:34:56 yakkety-vm sh[1960]: + systemctl --user show-environment Oct 04 10:34:56 yakkety-vm sh[1960]: + grep XMODIFIERS Oct 04 10:34:56 yakkety-vm sh[1960]: XMODIFIERS=@im What is shows is that the value of XMODIFIERS in "systemctl --user show- environment" changes after "initctl set-env -gr $$v=$$(eval "echo \\{v}") || true;" is run -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: New Bug description: The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629132] Re: Please merge network-manager-openvpn 1.2.4-1 from Debian (unstable) to Ubuntu (yakkety)
Aron, could you test the 1.6 packages from https://launchpad.net/~jbicha/+archive/ubuntu/arch/+packages Please don't permanently add that PPA to your sources since I push all sorts of things to my development PPAs. As you can see it builds on all regular PPA architectures on yakkety. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1629132 Title: Please merge network-manager-openvpn 1.2.4-1 from Debian (unstable) to Ubuntu (yakkety) Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: Please merge network-manager-openvpn 1.2.4-1 from Debian (unstable) to Ubuntu (yakkety), to match with the version of main network-manager package (1.2.4). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1629132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630156] [NEW] No password needed to Log in after cancel the password and then reset again
Public bug reported: OS: 14.04 trusty 1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system setting. 2. Click "Password --> Action --> Log in without password -->Change to clear Log in password. 3. Reboot and log to desktop without password. 4. Then do the similar action "Set a password now" as the same way to set Log in password. 5. Reboot but still no password needed at Log in interface. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1630156 Title: No password needed to Log in after cancel the password and then reset again Status in lightdm package in Ubuntu: New Bug description: OS: 14.04 trusty 1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system setting. 2. Click "Password --> Action --> Log in without password -->Change to clear Log in password. 3. Reboot and log to desktop without password. 4. Then do the similar action "Set a password now" as the same way to set Log in password. 5. Reboot but still no password needed at Log in interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1630156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630152] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with a
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1630152 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with apt-update as well. Status in fontconfig package in Ubuntu: New Bug description: Just an overall problem with apt-update from the CL after a fresh install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 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 Date: Tue Oct 4 02:28:16 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1630152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630152] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with a
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: fontconfig (Ubuntu) Importance: Undecided => Low ** Changed in: fontconfig (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1630152 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with apt-update as well. Status in fontconfig package in Ubuntu: Invalid Bug description: Just an overall problem with apt-update from the CL after a fresh install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 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 Date: Tue Oct 4 02:28:16 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1630152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1514267] Re: no display with prime on 14.04 - GT730M - Toshiba Tecra A50-a
One year and still not working... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1514267 Title: no display with prime on 14.04 - GT730M - Toshiba Tecra A50-a Status in nvidia-prime package in Ubuntu: New Bug description: I get kind of black screen after boot, before session login. If I try to go to terminal (Ctl+Alt+F1), it goe's for a few seconds, then turns back to the black screen. Doesn't work even with X safe boot, return to safe boot menu after I accept to run in low-graphic mode. System: 14.04 64bits GT730M Toshiba Tecra A50-a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1514267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630152] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with
Public bug reported: Just an overall problem with apt-update from the CL after a fresh install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 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 Date: Tue Oct 4 02:28:16 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1630152 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with apt-update as well. Status in fontconfig package in Ubuntu: New Bug description: Just an overall problem with apt-update from the CL after a fresh install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 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 Date: Tue Oct 4 02:28:16 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1630152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629668] Re: [regression] Some Display settings have gone missing: Scale, Launcher placement
Seems to be fixed today. But what fixed it? -- 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/1629668 Title: [regression] Some Display settings have gone missing: Scale, Launcher placement Status in unity-control-center package in Ubuntu: Fix Committed Bug description: There appear to be other options missing as well. They should be under "General options" but there is nothing there. Ubuntu Yakkety Yak (development branch) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity-control-center 15.04.0+16.10.20160705.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Oct 2 09:56:19 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-09-29 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= 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/unity-control-center/+bug/1629668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 887821] Re: "Show copy dialog" right click launcher entry doesn't work (on nautilus copy)
** Attachment removed: "Monitor for windows with certain title and strip them of "skip_taskbar" property." https://bugs.launchpad.net/ubuntu/+source/unity/+bug/887821/+attachment/4753662/+files/fix_skip_taskbar.sh ** Attachment added: "Monitor for windows with certain title and strip them of "skip_taskbar" property." https://bugs.launchpad.net/ubuntu/+source/unity/+bug/887821/+attachment/4754095/+files/fix_skip_taskbar.sh -- 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/887821 Title: "Show copy dialog" right click launcher entry doesn't work (on nautilus copy) Status in Unity: Fix Released Status in Unity 5.0 series: Won't Fix Status in nautilus package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in nautilus source package in Precise: Fix Released Status in unity source package in Precise: Invalid Bug description: Impact: the nautilus copy dialog don't get properly focussed by unity Test Case: - log into an unity session - copy a not too small file (so you have time to interact with the copy dialog) - minimize the copy dialog - right click on the corresponding unity-launcher's icon, and pick "show copy dialog" -> the dialog should be displayed Regression testing: Check that there is no focus issue with that dialog and the launcher -- While copying a large (8 gig) file across an SMB network, I minimized it. The right click on the Nautilus Unity bar showed a "Show copy dialog" item. Clicking on that item did nothing. The only way to get the dialog back up was to open one of the two minimized Nautilus windows and then minimize the one on top. After that minimize, then the copy dialog was displayed on top of the other Nautilus window. I couldn't find any way to get the copy dialog back on screen without clicking around somewhat aimlessly displaying and minimizing Nautilus windows until it appeared. The "Show copy dialog" right-click menu appeared to have no affect. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Nov 8 18:12:10 2011 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: PATH=(custom, no user) 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/unity/+bug/887821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
Now I modified each iteration of the loop in im-config.service to show the environment Oct 04 10:21:20 yakkety-vm sh[1972]: + dbus-update-activation-environment --verbose --systemd XMODIFIERS Oct 04 10:21:20 yakkety-vm sh[1972]: dbus-update-activation-environment: setting XMODIFIERS=@im=ibus Oct 04 10:21:20 yakkety-vm sh[1972]: + systemctl --user show-environment […] Oct 04 10:21:20 yakkety-vm sh[1972]: XMODIFIERS=@im=ibus Oct 04 10:21:20 yakkety-vm sh[1972]: + dbus-update-activation-environment --verbose --systemd GTK_IM_MODULE Oct 04 10:21:20 yakkety-vm sh[1972]: dbus-update-activation-environment: setting GTK_IM_MODULE=ibus Oct 04 10:21:20 yakkety-vm sh[1972]: + systemctl --user show-environment Oct 04 10:21:20 yakkety-vm sh[1972]: XMODIFIERS=@im ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: New Bug description: The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1618363] Re: /dev/urandom not included in chroot, leads to crashes with static key
No, only the openvpn process crashes. ** Changed in: network-manager-openvpn (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1618363 Title: /dev/urandom not included in chroot, leads to crashes with static key Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-openvpn package in Debian: New Bug description: I am trying to connect to an OpenVPN server with a static key and get these error messages in the logfile: Aug 30 10:31:37 defiant nm-openvpn[11201]: RAND_bytes() failed Aug 30 10:31:37 defiant nm-openvpn[11201]: Assertion failed at crypto.c:1386 (rand_bytes (output, len)) Aug 30 10:31:37 defiant nm-openvpn[11201]: Exiting due to fatal error This looks like Debian bug #820554 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-openvpn 1.1.93-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 30 10:37:43 2016 InstallationDate: Installed on 2012-06-14 (1537 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to xenial on 2016-08-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1618363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629132] Re: Please merge network-manager-openvpn 1.2.4-1 from Debian (unstable) to Ubuntu (yakkety)
It's funny you say that, because the build fails here with my yakkety schroot with 1.2.4-1ubuntu1: make[5]: Entering directory '/<>/properties/tests' gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_32 -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircommon -I/usr/include/mircookie -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_4 -pthread -I/usr/include/libnm -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DNM_VERSION_MIN_REQUIRED=NM_VERSION_1_2 -DNM_VERSION_MAX_ALLOWED=NM_VERSION_1_2 -pthrea d -I/usr/include/libnma -I/usr/include/libnm -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 -I../../shared -I../../properties -DTEST_SRCDIR="\"/<>/properties/tests\"" -DTEST_BUILDDIR="\"/<>/properties/tests\"" -Wall -std=gnu89 -Wshadow -Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement -Wformat-security -Wfloat-equal -Wno-unused-parameter -Wno-sign-compare -fno-strict-aliasing -Wno-unused-but-set-variable -Wundef -Wimplicit-function-declaration -Wpointer-arith -Winit-self -Wmissing-include-dirs -Wno-pragmas -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Warray-bounds -Wunused-value -c -o test_import_export-test-import-export.o `test -f 'test-import-export.c' || echo './'`test-import-export.c /bin/bash ../../libtool --tag=CC --mode=link gcc -I../../shared -I../../properties -DTEST_SRCDIR="\"/<>/properties/tests\"" -DTEST_BUILDDIR="\"/<>/properties/tests\"" -Wall -std=gnu89 -Wshadow -Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement -Wformat-security -Wfloat-equal -Wno-unused-parameter -Wno-sign-compare -fno-strict-aliasing -Wno-unused-but-set-variable -Wundef -Wimplicit-function-declaration -Wpointer-arith -Winit-self -Wmissing-include-dirs -Wno-pragmas -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Warray-bounds -Wunused-value -Wl,-Bsymbolic-functions -Wl,-z,relro -o test-import-export test_import_export-test-import-export.o -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lnm -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lnma -lnm -lgio-2.0 -lgobject-2.0 -lglib-2.0 -ldl ../../properties/li bnm-vpn-plugin-openvpn-test.la libtool: link: gcc -I../../shared -I../../properties -DTEST_SRCDIR=\"/<>/properties/tests\" -DTEST_BUILDDIR=\"/<>/properties/tests\" -Wall -std=gnu89 -Wshadow -Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement -Wformat-security -Wfloat-equal -Wno-unused-parameter -Wno-sign-compare -fno-strict-aliasing -Wno-unused-but-set-variable -Wundef -Wimplicit-function-declaration -Wpointer-arith -Winit-self -Wmissing-include-dirs -Wno-pragmas -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Warray-bounds -Wunused-value -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -o test-import-export test_import_export-test-import-export.o -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lnma -ldl ../../properties/.libs/libnm-vpn-plugin-openvpn-test.a -lnm -lgio-2.0 -lgobject-2.0 -lglib-2.0 -pthread /usr/bin/ld: ../../properties/.libs/libnm-vpn-plugin-openvpn-test.a(libnm_vpn_plugin_openvpn_test_la-nm-vpn-plugin-utils.o): undefined reference to symbol 'dlclose@@GLIBC_2.2.5' /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libdl.so: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status Makefile:691: recipe for target 'test-import-export' failed make[5]: *** [test-import-export] Error 1 make[5]: Leaving directory '/<>/properties/tests' Makefile:769: recipe for target 'all-recursive' failed Maybe this is what you saw when you tried to compile 1.2.6 today? When did this last build on yakkety for you, because maybe there's a serious regression caused by another package? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1629132 Title: Please merge network-manager-openvpn 1.2.4-1 from Debian (unstable) to Ubuntu (yakkety) Status in network-manager-openvpn package in Ubuntu:
[Desktop-packages] [Bug 1630181] [NEW] Solver for Non-Linear Programming Gone in Yakkety
Public bug reported: As the title says. This used to be provided by a separate source package, nlpsolver . This is gone in both Debian Sid and Yakkety. In debian, they have integrated this into the libreoffice source, which now provides the deb libreoffice-nlpsolver which used to come from nlpsolver. This has not been brought into the Ubuntu version however. Simple fix would be to copy the relevant packaging from debian. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1630181 Title: Solver for Non-Linear Programming Gone in Yakkety Status in libreoffice package in Ubuntu: New Bug description: As the title says. This used to be provided by a separate source package, nlpsolver . This is gone in both Debian Sid and Yakkety. In debian, they have integrated this into the libreoffice source, which now provides the deb libreoffice-nlpsolver which used to come from nlpsolver. This has not been brought into the Ubuntu version however. Simple fix would be to copy the relevant packaging from debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1630181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
>From ExecStart of im-config.service (modified slightly to eliminate quoting issues) Oct 04 10:09:43 yakkety-vm sh[1925]: + dbus-update-activation-environment --verbose --systemd XMODIFIERS Oct 04 10:09:43 yakkety-vm sh[1925]: dbus-update-activation-environment: setting XMODIFIERS=@im=ibus and then I added to the bottom of the same ExecStart: Oct 04 10:09:43 yakkety-vm sh[1925]: + systemctl --user show-environment […] Oct 04 10:09:43 yakkety-vm sh[1925]: XMODIFIERS=@im So it does *not* seem to be a problem with overwriting to me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: New Bug description: The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629132] Re: Please merge network-manager-openvpn 1.2.4-1 from Debian (unstable) to Ubuntu (yakkety)
Actually 1.2.6 builds here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1629132 Title: Please merge network-manager-openvpn 1.2.4-1 from Debian (unstable) to Ubuntu (yakkety) Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: Please merge network-manager-openvpn 1.2.4-1 from Debian (unstable) to Ubuntu (yakkety), to match with the version of main network-manager package (1.2.4). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1629132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
sorry, initctl set-env -g -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
I think it's upstart being buggy when forwarding the initctl set-env -g to the dbus activation environment ‣ Type=method_call Endian=l Flags=0 Version=1 Priority=0 Cookie=5665 Sender=:1.15 Destination=org.freedesktop.DBus Path=/org/freedesktop/DBus Interface=org.freedesktop.DBus Member=UpdateActivationEnvironment UniqueName=:1.15 MESSAGE "a{ss}" { ARRAY "{ss}" { DICT_ENTRY "ss" { STRING "FOO"; STRING "bar"; }; }; }; -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: New Bug description: The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
That was from "initctl set-env FOO=bar=baz" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630088] Re: Sync c2esp 27-3 (main) from Debian unstable (main)
Synced. It's sitting in the review queue now: https://launchpad.net/ubuntu/yakkety/+queue?queue_state=1_text= Please close the bug manually once it's accepted. ** Changed in: c2esp (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to c2esp in Ubuntu. https://bugs.launchpad.net/bugs/1630088 Title: Sync c2esp 27-3 (main) from Debian unstable (main) Status in c2esp package in Ubuntu: Fix Committed Bug description: Please sync c2esp 27-3 (main) from Debian unstable (main) http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html Changelog entries since current yakkety version 27-2: c2esp (27-3) unstable; urgency=medium * Update patch fixing missing includes to add to fix FTBFS (Closes: #839344) -- Didier RaboudMon, 03 Oct 2016 09:22:26 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/1630088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
I don't think it's a quoting issue (or issue with parsing the extra '=') in d-u-a-e, as when I run this manually it works: $ export XMODIFIERS=@im=ibus $ dbus-update-activation-environment --verbose --systemd XMODIFIERS dbus-update-activation-environment: setting XMODIFIERS=@im=ibus $ systemctl --user show-environment |grep XMODIF XMODIFIERS=@im=ibus But clearly in a freshly started desktop the value is just "@im". My buest guess is that something else also sets $XMODIFIERS later on, and overwrites the value from im-config.service? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: New Bug description: The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1060167] Re: indicator doesn't always work properly after suspend
I get the problem on two laptops (16.04 up to date), after a suspend/resume cycle, wifi network list disappears from nm-applet. If I kill and restart nm-applet, wifi network list is displayed again. On a third laptop, I have to restart network-manager service daemon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1060167 Title: indicator doesn't always work properly after suspend Status in network-manager-applet package in Ubuntu: Confirmed Bug description: This is not a new bug but I finally decided to report it. I have a wired and a wireless connection at home. I usually disconnect the wireless via network-manager while at home. After suspend, both connections come up. If I use the network-manager indicator to disconnect, I am unable to-- I can navigate the menus in the indicator but clicking on things does not work (eg, disconnect from my home connection, Edit connections, etc). This seems to be related to suspending for some period of time: ie, it seems to always happen after suspending at night/resuming in the morning whereas booting the computer, logging in, suspending, resuming and using the indicator straight away tends to work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1060167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630088] Re: Sync c2esp 27-3 (main) from Debian unstable (main)
** Changed in: c2esp (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to c2esp in Ubuntu. https://bugs.launchpad.net/bugs/1630088 Title: Sync c2esp 27-3 (main) from Debian unstable (main) Status in c2esp package in Ubuntu: Fix Released Bug description: Please sync c2esp 27-3 (main) from Debian unstable (main) http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html Changelog entries since current yakkety version 27-2: c2esp (27-3) unstable; urgency=medium * Update patch fixing missing includes to add to fix FTBFS (Closes: #839344) -- Didier RaboudMon, 03 Oct 2016 09:22:26 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/1630088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1165382] Re: No sound output/input to Plantronics .Audio 478 USB
UPDATE: working after disabling the Intel HD on motherboard, seem bug in Pulseaudio UI. -- 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/1165382 Title: No sound output/input to Plantronics .Audio 478 USB Status in pulseaudio package in Ubuntu: Invalid Bug description: Plantronics .Audio 478 USB works well with Ubuntu 12.04. Ubuntu 13.04 beta2 has option for sound output to it but really sound outputs to standart laptop speakers. There is no Plantronics .Audio 478 in input devices list and sound input not work from it. lsusb: Bus 003 Device 004: ID 047f:c011 Plantronics, Inc. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:3.0-0ubuntu4b2 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 4416 F pulseaudio /dev/snd/controlC0: ubuntu 3483 F pulseaudio ubuntu 4416 F pulseaudio /dev/snd/pcmC0D0c: ubuntu 3483 F...m pulseaudio CasperVersion: 1.330 Date: Sat Apr 6 11:57:20 2013 ExecutablePath: /usr/bin/pulseaudio LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2008 dmi.bios.vendor: Acer dmi.bios.version: V3.13 dmi.board.name: Navarro dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5110:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5110 dmi.product.version: V3.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1165382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1165382] Re: No sound output/input to Plantronics .Audio 478 USB
16.04, now sound is ok, but no input from microphone. -- 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/1165382 Title: No sound output/input to Plantronics .Audio 478 USB Status in pulseaudio package in Ubuntu: Invalid Bug description: Plantronics .Audio 478 USB works well with Ubuntu 12.04. Ubuntu 13.04 beta2 has option for sound output to it but really sound outputs to standart laptop speakers. There is no Plantronics .Audio 478 in input devices list and sound input not work from it. lsusb: Bus 003 Device 004: ID 047f:c011 Plantronics, Inc. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:3.0-0ubuntu4b2 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 4416 F pulseaudio /dev/snd/controlC0: ubuntu 3483 F pulseaudio ubuntu 4416 F pulseaudio /dev/snd/pcmC0D0c: ubuntu 3483 F...m pulseaudio CasperVersion: 1.330 Date: Sat Apr 6 11:57:20 2013 ExecutablePath: /usr/bin/pulseaudio LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2008 dmi.bios.vendor: Acer dmi.bios.version: V3.13 dmi.board.name: Navarro dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5110:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5110 dmi.product.version: V3.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1165382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617204] Re: NM does not offer VPN options
Solved. Turns out Lubuntu also needs network-manager-pptp-gnome -- 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/1617204 Title: NM does not offer VPN options Status in network-manager package in Ubuntu: New Bug description: network-manager-pptp is installed, but when I select "Configure VPN" NM offers only Hardware and Virtual options, no VPN options., Observed on two Lubuntu 16.04 and one LXLE 16.04 system; everything works as expected on Lubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Aug 26 09:05:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-08 (17 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) IpRoute: default via 172.16.0.27 dev wlp2s0 proto static metric 600 172.16.0.0/16 dev wlp2s0 proto kernel scope link src 172.16.0.182 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 CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 haywiredcce62ca8-d2bd-480e-b67b-f4cf93a54d8b /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.0connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1617204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
This bug was fixed in the package im-config - 0.29-1ubuntu16 --- im-config (0.29-1ubuntu16) yakkety; urgency=medium * debian/user/im-config.service: Reverse the order of "initctl set-env" and "dbus-update-activation-environment". $XMODIFIERS can contain an "=" (its value might be, for example, "@im=ibus"). upstart forwards "set-env -g" calls to D-Bus, but it constructs the parameters to the call incorrectly and splits on "=" characters in the value, discarding anything which follows. We can work around this bug by calling "initctl set-env -g" first, and then "dbus-update-activation-environment" to overwrite the buggy value. (LP: #1630090) * debian/user/im-config.service: Get rid of one eval - "dbus-update-activation-environment" will look up the variable in the environment if you don't specify a value. -- Iain LaneTue, 04 Oct 2016 12:28:35 +0100 ** Changed in: im-config (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Bug description: When "initctl set-env -g" is called, upstart calls D-Bus to also update its activation environment (the environment that D-Bus activated services get). There is a bug here: - SetEnv takes a parameter of the form "VARIABLE=VALUE" - This is split on "=" to determine the two parts - If the VALUE has an "=" character in it, everything after the first "=" is lost, because all "=" characters are split and not the first one In this case, XMODIFIERS=@im=ibus was being turned into XMODIFIERS=@im. upstart should only split on the first "=", and keep the rest of the string unsplit. It doesn't look like nih_str_split is going to be very helpful here. [ Original description ] The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619442] Re: An empty bar appeared above the toolbar after upgrade to version 5.2 (Unity7/gtk2)
Closing as per comment 7 and comment 8. ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1619442 Title: An empty bar appeared above the toolbar after upgrade to version 5.2 (Unity7/gtk2) Status in libreoffice package in Ubuntu: Fix Released Bug description: After upgrade of LibreOffice to version 5.2, an empty bar appeared between the toolbar and the window header. The empty bar contains only the button Close Document. If a new instance of LO window is opened from an existing LO window via Window -> New Window, the empty bar is absent in the new window and the UI looks correctly. Version: 5.2.0.4 Build ID: 1:5.2.0~rc4-0ubuntu1~xenial2 installed from ppa:libreoffice/ppa Ubuntu 16.04 LTS amd64 Unity7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1619442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
This bug was fixed in the package gnome-control-center - 1:3.20.1-2ubuntu2 --- gnome-control-center (1:3.20.1-2ubuntu2) yakkety; urgency=medium * Cherrypick commits from the 3.20 branch since there was never a 3.20.2 release. See patch headers or git for descriptions of issues fixed. - 0002-mouse-Make-touchpad-capability-checking-on-wayland-w.patch - 0007-universal-access-allow-focus-on-row-switches.patch - 0008-mouse-allow-focus-on-switches-in-the-Touchpad-sectio.patch - 0014-network-fix-some-SSID-escaping-issues.patch - 0016-user-accounts-Fix-missing-records-in-the-history-dia.patch (LP: #1443052) - 0020-privacy-React-to-changes-in-permissions-store.patch - 0021-privacy-Update-for-PermissionStore-DBus-API-changes.patch - 0025-power-Fix-hiding-wi-fi-mobile-broadband-toggles.patch - 0026-power-Fix-wifi-device-state-when-opening-power-panel.patch - 0027-printers-Fix-compilation-warning.patch - 0028-display-Fix-possible-crash-on-startup.patch -- Jeremy BichaTue, 04 Oct 2016 06:52:59 -0400 ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Confirmed Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 797485] Re: Status Bar Covers File Name at Bottom
** Description changed: + [Impact] + + If using Nautilus without a status bar the selected item title 'floats' + at the bottom of the file listing. + + If you choose the last file item in a list this 'floating' title + prevents you seeing the actual title making editing + difficult/impossible. This issue is also present in icon view if you + have an even number of files on the bottom row it becomes difficult to + rename the last file as the status bar covers the text area. + + [Test Case] + + Using Ubuntu 16.04.1 open the file manager, click "Home", enable list + view and resize the file manager window so that the contents of the home + directory just fit vertically and horizontally. Select the last item in + the file listing and then move the mouse slowly from left to right and + back again several time. You will see the floating status bar will jump + from left to right, obscuring details of the selected item. + + After the patched nautilus package is installed, performing the same + test will result on the floating status bar being hidden when the mouse + hovers over it. + + [Regression Potential] + + None. This patch has been adapted from the following upstream commit: + + * https://git.gnome.org/browse/nautilus/commit/?id=e66d3ca + + [ Other Info ] + Binary package hint: nautilus - In Nautilus when you have an even number of files on the bottom row it - becomes difficult to rename the last file as the status bar covers the - text area. + The following possible solutions were considered: - I realize this is likely a rare occurrence, and can be gotten around by - adjusting the width of the window, but it is a minor bug. - - Possible solutions: - - Move status bar to the left side when working with files in that corner. - - Do not show status bar while renaming. - - Best IMHO: Give the file area a bottom margin of the height of the - status bar. - - - Ubuntu 11.04, Gnome-Shell (Although it should just be nautilus in general.) - nautilus: 1:3.0.2-0ubuntu2~natty1 + * Give the file list a bottom margin of the height of the status bar. + * Move status bar to the left side when working with files in that corner. + * Do not show status bar while renaming. + * Hide the floating bars when hovering over part of the selection. ** Summary changed: - Status Bar Covers File Name at Bottom + SRU: Status Bar Covers File Name at Bottom ** Tags removed: rls-x-notfixing ** Tags added: patch ** Description changed: [Impact] If using Nautilus without a status bar the selected item title 'floats' at the bottom of the file listing. If you choose the last file item in a list this 'floating' title prevents you seeing the actual title making editing difficult/impossible. This issue is also present in icon view if you have an even number of files on the bottom row it becomes difficult to rename the last file as the status bar covers the text area. [Test Case] Using Ubuntu 16.04.1 open the file manager, click "Home", enable list view and resize the file manager window so that the contents of the home directory just fit vertically and horizontally. Select the last item in the file listing and then move the mouse slowly from left to right and back again several time. You will see the floating status bar will jump from left to right, obscuring details of the selected item. After the patched nautilus package is installed, performing the same test will result on the floating status bar being hidden when the mouse hovers over it. [Regression Potential] None. This patch has been adapted from the following upstream commit: * https://git.gnome.org/browse/nautilus/commit/?id=e66d3ca + Packages have been built in a PPA and tested for regressions. + [ Other Info ] Binary package hint: nautilus The following possible solutions were considered: * Give the file list a bottom margin of the height of the status bar. * Move status bar to the left side when working with files in that corner. * Do not show status bar while renaming. * Hide the floating bars when hovering over part of the selection. -- 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/797485 Title: SRU: Status Bar Covers File Name at Bottom Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Xenial: In Progress Bug description: [Impact] If using Nautilus without a status bar the selected item title 'floats' at the bottom of the file listing. If you choose the last file item in a list this 'floating' title prevents you seeing the actual title making editing difficult/impossible. This issue is also present in icon view if you have an even number of files on the bottom row it becomes difficult to rename the last file as the status bar covers the text area.
[Desktop-packages] [Bug 1591785] Re: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc and g++ are set to v4.8 instead of default v5.3
** Changed in: nvidia-graphics-drivers-361 (Ubuntu) Status: Confirmed => New ** Changed in: hundredpapercuts Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu. https://bugs.launchpad.net/bugs/1591785 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc and g++ are set to v4.8 instead of default v5.3 Status in One Hundred Papercuts: New Status in nvidia-graphics-drivers-361 package in Ubuntu: New Bug description: after a routine system update, Linux kernel was upgraded to 4.4.0-24-generic. Since then, the nvidia graphic drivers simply refuses to build: > Building initial module for 4.4.0-24-generic > Error! Bad return status for module build on kernel: 4.4.0-24-generic (x86_64) > Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 DKMSKernelVersion: 4.4.0-24-generic Date: Sun Jun 12 19:45:40 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized command line option ‘-fstack-protector-strong’ InstallationDate: Installed on 2015-10-31 (225 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1591785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
** Also affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 797485] Re: Status Bar Covers File Name at Bottom
Oops, the patch above is not the debdiff. This is the debdiff for Xenial) that implements hiding the nautilus-floating-bar on hover. ** Patch added: "nautilus-floating-bar-hode-on-hover.diff" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/797485/+attachment/4754165/+files/nautilus-floating-bar-hode-on-hover.diff -- 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/797485 Title: Status Bar Covers File Name at Bottom Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Xenial: New Bug description: Binary package hint: nautilus In Nautilus when you have an even number of files on the bottom row it becomes difficult to rename the last file as the status bar covers the text area. I realize this is likely a rare occurrence, and can be gotten around by adjusting the width of the window, but it is a minor bug. Possible solutions: Move status bar to the left side when working with files in that corner. Do not show status bar while renaming. Best IMHO: Give the file area a bottom margin of the height of the status bar. Ubuntu 11.04, Gnome-Shell (Although it should just be nautilus in general.) nautilus: 1:3.0.2-0ubuntu2~natty1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/797485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 797485] Re: Status Bar Covers File Name at Bottom
** Also affects: nautilus (Ubuntu Xenial) Importance: Undecided Status: New -- 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/797485 Title: Status Bar Covers File Name at Bottom Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Xenial: In Progress Bug description: Binary package hint: nautilus In Nautilus when you have an even number of files on the bottom row it becomes difficult to rename the last file as the status bar covers the text area. I realize this is likely a rare occurrence, and can be gotten around by adjusting the width of the window, but it is a minor bug. Possible solutions: Move status bar to the left side when working with files in that corner. Do not show status bar while renaming. Best IMHO: Give the file area a bottom margin of the height of the status bar. Ubuntu 11.04, Gnome-Shell (Although it should just be nautilus in general.) nautilus: 1:3.0.2-0ubuntu2~natty1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/797485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 797485] Re: Status Bar Covers File Name at Bottom
** Changed in: nautilus (Ubuntu Xenial) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: nautilus (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: nautilus (Ubuntu Xenial) Status: New => In Progress -- 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/797485 Title: Status Bar Covers File Name at Bottom Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Xenial: In Progress Bug description: Binary package hint: nautilus In Nautilus when you have an even number of files on the bottom row it becomes difficult to rename the last file as the status bar covers the text area. I realize this is likely a rare occurrence, and can be gotten around by adjusting the width of the window, but it is a minor bug. Possible solutions: Move status bar to the left side when working with files in that corner. Do not show status bar while renaming. Best IMHO: Give the file area a bottom margin of the height of the status bar. Ubuntu 11.04, Gnome-Shell (Although it should just be nautilus in general.) nautilus: 1:3.0.2-0ubuntu2~natty1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/797485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
Just updated the description. The problem is now understood, and we worked around the upstart bug in gnome-session and im-config. ** Description changed: + When "initctl set-env -g" is called, upstart calls D-Bus to also update + its activation environment (the environment that D-Bus activated + services get). There is a bug here: + + - SetEnv takes a parameter of the form "VARIABLE=VALUE" + - This is split on "=" to determine the two parts + - If the VALUE has an "=" character in it, everything after the first "=" is lost, because all "=" characters are split and not the first one + + In this case, XMODIFIERS=@im=ibus was being turned into XMODIFIERS=@im. + + upstart should only split on the first "=", and keep the rest of the + string unsplit. It doesn't look like nih_str_split is going to be very + helpful here. + + [ Original description ] + The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. ** Changed in: im-config (Ubuntu) Status: New => Fix Committed ** Changed in: upstart (Ubuntu) Status: New => Triaged ** Changed in: upstart (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: Fix Committed Status in upstart package in Ubuntu: Triaged Bug description: When "initctl set-env -g" is called, upstart calls D-Bus to also update its activation environment (the environment that D-Bus activated services get). There is a bug here: - SetEnv takes a parameter of the form "VARIABLE=VALUE" - This is split on "=" to determine the two parts - If the VALUE has an "=" character in it, everything after the first "=" is lost, because all "=" characters are split and not the first one In this case, XMODIFIERS=@im=ibus was being turned into XMODIFIERS=@im. upstart should only split on the first "=", and keep the rest of the string unsplit. It doesn't look like nih_str_split is going to be very helpful here. [ Original description ] The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630199] [NEW] [Torino Z200, Realtek ALC269VB, Speaker, Internal] No sound at all
Public bug reported: No sound via speaker, sound is obtainable by using alsamixer and increasing the volume of the 'headset' the control labelled 'speaker' does not have any apparent effect. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mick 1728 F pulseaudio CurrentDesktop: MATE Date: Tue Oct 4 11:21:27 2016 InstallationDate: Installed on 2016-09-29 (4 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all 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: mick 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Torino Z200, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.01 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 079114 dmi.board.vendor: DSG Retail Ltd dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: DSG Retail Ltd dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.01:bd02/08/2014:svnAdvent:pnTorinoZ200:pvr1.01:rvnDSGRetailLtd:rn079114:rvrTobefilledbyO.E.M.:cvnDSGRetailLtd:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Torino Z200 dmi.product.version: 1.01 dmi.sys.vendor: Advent ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1630199 Title: [Torino Z200, Realtek ALC269VB, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound via speaker, sound is obtainable by using alsamixer and increasing the volume of the 'headset' the control labelled 'speaker' does not have any apparent effect. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mick 1728 F pulseaudio CurrentDesktop: MATE Date: Tue Oct 4 11:21:27 2016 InstallationDate: Installed on 2016-09-29 (4 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all 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: mick 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Torino Z200, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.01 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 079114 dmi.board.vendor: DSG Retail Ltd dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: DSG Retail Ltd dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.01:bd02/08/2014:svnAdvent:pnTorinoZ200:pvr1.01:rvnDSGRetailLtd:rn079114:rvrTobefilledbyO.E.M.:cvnDSGRetailLtd:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Torino Z200 dmi.product.version: 1.01 dmi.sys.vendor: Advent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1630199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
I have been running a manual script ten times a day for half a year to live with this bug. The bug I reported upstream are either waiting for us here on launchpad or the bug's not being taken serious. Are there anyone reading this that knows anything about how we can get this fixed, I don't have the experience or the skills to set things in motion. It does seem like there only a handful of us regular users that's aware of this problem. Please anyone? -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630195] [NEW] Pages are reloaded continuously, making the website useless
Public bug reported: Steps to reproduce: 1. Open Firefox on "www.hpe.com". You will be redirected to a localized web page. Mine is "https://www.hpe.com/it/it/home.html; 2. Try to click on the video link on the top of the page or any of the links in the top bar like "Solutions", "Services", "Products", "About". Expexted results: Normal(tm) browsing experience Actual results: You cannot jump to the linked web pages unless you are fast enough. The web page(s) are reloaded about once every 5 seconds. In case the page is long, you don't have time to read or scroll it. It happens: Always on this web site It doesn't happen: By using Microsoft Edge browser (on a windows machine) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 49.0+build4-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-lowlatency 4.4.19 Uname: Linux 4.4.0-38-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: support1631 F pulseaudio BuildID: 20160920074044 Channel: Unavailable CurrentDesktop: KDE Date: Tue Oct 4 12:13:21 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.1.1 dev enxc4e9840ddc04 proto static metric 600 169.254.0.0/16 dev enxc4e9840ddc04 scope link metric 1000 192.168.1.0/24 dev enxc4e9840ddc04 proto kernel scope link src 192.168.1.68 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=49.0/20160920074044 (In use) RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L02 v02.01 dmi.board.asset.tag: CZC3523T17 dmi.board.name: 18EB dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC3523T17 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL02v02.01:bd09/22/2013:svnHewlett-Packard:pnHPProDesk490G1MT:pvr:rvnHewlett-Packard:rn18EB:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP ProDesk 490 G1 MT dmi.sys.vendor: Hewlett-Packard ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1630195 Title: Pages are reloaded continuously, making the website useless Status in firefox package in Ubuntu: New Bug description: Steps to reproduce: 1. Open Firefox on "www.hpe.com". You will be redirected to a localized web page. Mine is "https://www.hpe.com/it/it/home.html; 2. Try to click on the video link on the top of the page or any of the links in the top bar like "Solutions", "Services", "Products", "About". Expexted results: Normal(tm) browsing experience Actual results: You cannot jump to the linked web pages unless you are fast enough. The web page(s) are reloaded about once every 5 seconds. In case the page is long, you don't have time to read or scroll it. It happens: Always on this web site It doesn't happen: By using Microsoft Edge browser (on a windows machine) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 49.0+build4-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-lowlatency 4.4.19 Uname: Linux 4.4.0-38-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: support1631 F pulseaudio BuildID: 20160920074044 Channel: Unavailable CurrentDesktop: KDE Date: Tue Oct 4 12:13:21 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.1.1 dev enxc4e9840ddc04 proto static metric 600 169.254.0.0/16 dev enxc4e9840ddc04 scope link metric 1000 192.168.1.0/24 dev enxc4e9840ddc04 proto kernel scope link src 192.168.1.68 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=49.0/20160920074044 (In use) RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage:
[Desktop-packages] [Bug 797485] Re: Status Bar Covers File Name at Bottom
Attached is a debdiff (for Xenial) that implements hiding the nautilus- floating-bar on hover. ** Patch added: "Adapted from https://git.gnome.org/browse/nautilus/commit/?id=e66d3ca; https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/797485/+attachment/4754164/+files/lp787485-hide-floatingbar-on-hover.patch -- 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/797485 Title: Status Bar Covers File Name at Bottom Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: Binary package hint: nautilus In Nautilus when you have an even number of files on the bottom row it becomes difficult to rename the last file as the status bar covers the text area. I realize this is likely a rare occurrence, and can be gotten around by adjusting the width of the window, but it is a minor bug. Possible solutions: Move status bar to the left side when working with files in that corner. Do not show status bar while renaming. Best IMHO: Give the file area a bottom margin of the height of the status bar. Ubuntu 11.04, Gnome-Shell (Although it should just be nautilus in general.) nautilus: 1:3.0.2-0ubuntu2~natty1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/797485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575338] Re: Gnome Software catalog entry missing for Pidgin
not from my side -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1575338 Title: Gnome Software catalog entry missing for Pidgin Status in appstream-dep11 package in Ubuntu: New Status in pidgin package in Ubuntu: Fix Released Bug description: The Pidgin package cannot be installed using the Gnome Software application because it's missing the needed metadata. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-dep11/+bug/1575338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 720327] Re: [Upstream] [regression] font display corruption in merged cells containing line breaks in Calc when scrolling
Resolving as per upstream: https://bugs.documentfoundation.org/show_bug.cgi?id=34558#c10 ** Bug watch added: Document Foundation Bugzilla #34558 https://bugs.documentfoundation.org/show_bug.cgi?id=34558 ** Changed in: df-libreoffice Importance: Medium => Unknown ** Changed in: df-libreoffice Status: Confirmed => Unknown ** Changed in: df-libreoffice Remote watch: freedesktop.org Bugzilla #34558 => Document Foundation Bugzilla #34558 ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/720327 Title: [Upstream] [regression] font display corruption in merged cells containing line breaks in Calc when scrolling Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Fix Released Bug description: Binary package hint: openoffice.org Pixel rows inside merged and centered cells in Calc get randomly dropped or (seldom) duplicated when scrolling the sheet. This is a regression from openoffice.org-calc 3.2.1-7ubuntu1 res. OpenOffice.org 3.2.1 which I see in Ubuntu's openoffice.org-calc 3.2.1-7ubuntu1.1 as well as in OpenOffice.org 3.3.0 from Sun/Oracle. Steps to reproduce: 1. Select a cell range spanning some cell rows, merge and center the selected cells. 2. Activate "wrap text automatically" for the merged cells. 3. Insert a (long) text and leave the cell. 4. Scroll the sheet. Ubuntu release: 10.10 openoffice.org-calc 3.2.1-7ubuntu1.1 I see this both with Metacity and with Compiz. It doesn't matter whether Calc runs fullscreen or in a window. lspci -nnk | grep -A 2 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation N10 Family Integrated Graphics Controller [8086:a011] Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] Kernel driver in use: i915 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/720327/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630258] [NEW] unity crashes when adding external monitor
Public bug reported: I was told to create a new bug after commenting on another issue, https://bugs.launchpad.net/ubuntu/+source/unity-control- center/+bug/1539597 I am running: Ubuntu 16.04 Dell 7510 I have tried the last three drivers and they all exhibit the same issue. When I plug in my external monitor via the display port on the 7510, unity crashes. If I try to open the display panel application, it crashes too. The second monitor is not recognized. If I run on the on-board Intel driver (Intel Prime Profile), everything works great. This started happening after my upgrade to 16.04 from 15.10. ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_lib_unity-settings-daemon_unity-settings-daemon.1000.crash" https://bugs.launchpad.net/bugs/1630258/+attachment/4754332/+files/_usr_lib_unity-settings-daemon_unity-settings-daemon.1000.crash -- 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/1630258 Title: unity crashes when adding external monitor Status in unity-control-center package in Ubuntu: New Bug description: I was told to create a new bug after commenting on another issue, https://bugs.launchpad.net/ubuntu/+source/unity-control- center/+bug/1539597 I am running: Ubuntu 16.04 Dell 7510 I have tried the last three drivers and they all exhibit the same issue. When I plug in my external monitor via the display port on the 7510, unity crashes. If I try to open the display panel application, it crashes too. The second monitor is not recognized. If I run on the on-board Intel driver (Intel Prime Profile), everything works great. This started happening after my upgrade to 16.04 from 15.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1630258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1563229] Re: Touchpad recognised as mouse FTE1000
I have TP200SA and have the same problem. Additionally touch screen is functional but can't scroll, only clicks. -- 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/1563229 Title: Touchpad recognised as mouse FTE1000 Status in linux package in Ubuntu: Triaged Status in xinput package in Ubuntu: Confirmed Status in linux source package in Trusty: Triaged Status in xinput source package in Trusty: Confirmed Status in linux source package in Wily: Triaged Status in xinput source package in Wily: Confirmed Status in linux source package in Xenial: Triaged Status in xinput source package in Xenial: Confirmed Bug description: In my Asus e200ha touchpad is recognized as mouse, only one click, no two finger click and scrolling Xinput say: FTE1000:00 0B05:0101 id=12[slave pointer (2)] i've tried: - ubuntu 14.04 with stock kernel - ubuntu 14.04 with 4.6rc1 kernel - Linux mint 17.3 with stock kernel --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: xinput 1.6.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563229/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575338] Re: Gnome Software catalog entry missing for Pidgin
Any news regarding this issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1575338 Title: Gnome Software catalog entry missing for Pidgin Status in appstream-dep11 package in Ubuntu: New Status in pidgin package in Ubuntu: Fix Released Bug description: The Pidgin package cannot be installed using the Gnome Software application because it's missing the needed metadata. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-dep11/+bug/1575338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1297790] Re: "Unknown audio device" dialog pops up every time I plug in headphones
This might be related https://bugs.launchpad.net/ubuntu/+source/unity- settings-daemon/+bug/1239605/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1297790 Title: "Unknown audio device" dialog pops up every time I plug in headphones Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: I've got a combined headphone/headset socket on my Laptop. Every time I plug in my headphones, an "unknown audio device" dialog pops up asking whether I've plugged in headphones or a headset. This is isn't a great user experience as my phone can auto-detect the device. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1949 F pulseaudio /dev/snd/controlC0: mark 1949 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 26 11:03:29 2014 InstallationDate: Installed on 2014-03-24 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Latitude E7440, Realtek ALC292, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.asset.tag: DE004505 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: DE004505 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1297790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629558] Re: Chromium sync says service unavailible
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/1629558 Title: Chromium sync says service unavailible Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hello. I'm building the packages for the Raspberry Pi and currently, I'm building from upstream, but using your options. It seems like the API keys are not working. I built a version and then tried my own keys and the new keys you supplied in v52, but the same issue persists. This is using v51. I've attached the network log and it seems like it's getting a 404 for some reason. Any assistance is appreciated! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1629558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276186] Re: System becomes unresponsive, ibus-ui-daemon takes ~150 % cpu
I had the same issue on ubuntu 16.04. When I used F2 to rename files, nautilus crashed when I did it to the third file. After that I didn't give up. Still the nautilus crashed when I left-clicked the nautilus. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1276186 Title: System becomes unresponsive, ibus-ui-daemon takes ~150 % cpu Status in ibus package in Ubuntu: Confirmed Bug description: As stated the graphical desktop became unresponsive. Dropping to CTRL + ALT + F1 terminal and `top`showed ibus-ui-daemon taking around 150 % cpu time and ibus-ui-gtk3 taking around 50 % cpu time. (names may contain minor errors) Tried to kill processes, rebooted. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 16:41:03 2014 InstallationDate: Installed on 2013-09-10 (147 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: ibus UpgradeStatus: Upgraded to saucy on 2013-10-23 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1276186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1447956] Re: Banshee interface unresponsive after upgrade to 15.04
** Changed in: banshee Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1447956 Title: Banshee interface unresponsive after upgrade to 15.04 Status in Banshee: Fix Released Status in banshee package in Ubuntu: Fix Released Status in banshee source package in Vivid: Fix Released Status in banshee package in Debian: Fix Released Bug description: I upgraded to the newest version yesterday. Some times it ran yesterday but i had some issues too. Today I cannot run it at all. When I start it from terminal I get amongst others: [Info 10:07:03.122] All services are started 0.997291 But all I get is an unresponsive white window. I will attach the entire terminal output bellow. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: banshee 2.9.0+really2.6.2-2ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 24 10:10:53 2015 ExecutablePath: /usr/lib/banshee/Banshee.exe InstallationDate: Installed on 2013-12-29 (480 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/mono-sgen SourcePackage: banshee UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago) [Impact] The SQLite performance regression has caused Banshee to hang on startup and become completely unusable. [Test Case] Launch banshee. See if it starts up correctly. [Regression Potential] Negligible -- it's hard to get any worse than completely unusable. [Other info] The fix has been in Debian unstable for a couple of months now with no new related bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/1447956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1621338] Re: nautilus[2221]: Theme parsing error: Adwaita.css:51:71: Using one color stop with linear-gradient() is deprecated.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1621338 Title: nautilus[2221]: Theme parsing error: Adwaita.css:51:71: Using one color stop with linear-gradient() is deprecated. Status in adwaita package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: Get this logged: gnome-shell[1838]: Theme parsing error: nautilus.css:55:71: Using one color stop with linear-gradient() is deprecated. gnome-shell[1838]: Theme parsing error: nautilus.css:56:71: Using one color stop with linear-gradient() is deprecated. gnome-shell[1838]: Theme parsing error: nautilus.css:55:71: Using one color stop with linear-gradient() is deprecated. gnome-shell[1838]: Theme parsing error: nautilus.css:56:71: Using one color stop with linear-gradient() is deprecated. nautilus[2221]: Theme parsing error: Adwaita.css:51:71: Using one color stop with linear-gradient() is deprecated. nautilus[2221]: Theme parsing error: Adwaita.css:52:71: Using one color stop with linear-gradient() is deprecated. Also the css settings are missing: The resource at '/org/gnome/libgd/tagged-entry/default.css' does not exist ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-6.7-generic 4.8.0-rc5 Uname: Linux 4.8.0-6-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 8 08:20:28 2016 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita/+bug/1621338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1621338] Re: nautilus[2221]: Theme parsing error: Adwaita.css:51:71: Using one color stop with linear-gradient() is deprecated.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: adwaita (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1621338 Title: nautilus[2221]: Theme parsing error: Adwaita.css:51:71: Using one color stop with linear-gradient() is deprecated. Status in adwaita package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: Get this logged: gnome-shell[1838]: Theme parsing error: nautilus.css:55:71: Using one color stop with linear-gradient() is deprecated. gnome-shell[1838]: Theme parsing error: nautilus.css:56:71: Using one color stop with linear-gradient() is deprecated. gnome-shell[1838]: Theme parsing error: nautilus.css:55:71: Using one color stop with linear-gradient() is deprecated. gnome-shell[1838]: Theme parsing error: nautilus.css:56:71: Using one color stop with linear-gradient() is deprecated. nautilus[2221]: Theme parsing error: Adwaita.css:51:71: Using one color stop with linear-gradient() is deprecated. nautilus[2221]: Theme parsing error: Adwaita.css:52:71: Using one color stop with linear-gradient() is deprecated. Also the css settings are missing: The resource at '/org/gnome/libgd/tagged-entry/default.css' does not exist ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-6.7-generic 4.8.0-rc5 Uname: Linux 4.8.0-6-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 8 08:20:28 2016 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita/+bug/1621338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP
This bug was fixed in the package unity-settings-daemon - 15.04.1+16.10.20161003-0ubuntu1 --- unity-settings-daemon (15.04.1+16.10.20161003-0ubuntu1) yakkety; urgency=medium [ Dmitry Shachnev ] * Upstart: Split XDG_CURRENT_DESKTOP properly and start only on Unity sessions [ Iain Lane ] * Check XDG_CURRENT_DESKTOP properly in the keyboard plugin (LP: #1554878) -- i...@orangesquash.org.uk (i...@orangesquash.org.uk) Mon, 03 Oct 2016 10:15:27 + ** Changed in: unity-settings-daemon (Ubuntu) Status: Fix Committed => Fix Released -- 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/1554878 Title: fix up usage of XDG_CURRENT_DESKTOP Status in GLib: Confirmed Status in Python XDG App: Confirmed Status in empathy package in Ubuntu: Fix Released Status in eog package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in indicator-bluetooth package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in totem package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Committed Status in unity-settings-daemon package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Fix Released Bug description: Since being standardised XDG_CURRENT_DESKTOP supports specifying multiple Desktop Names seperated by a colon, however many of the patches in Ubuntu pre-date this change so don't correctly support the current format in some cases. These days XDG_CURRENT_DESKTOP will look something like Unity GNOME (gnome-shell) GNOME-Classic:GNOME (gnome-shell classic mode) GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use GNOME-Flashack:GNOME for this) Many of the patches only check for == "Unity" or == "GNOME", so misbehave for the latter cases in the list above. I suspect this will be more widespread than just nautilus, but fixing that would be a good start. Since most of this code is still Ubuntu specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc), probably taking the last value in the string would get the desired result of Unity vs GNOME3 behaviour ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 9 15:04:36 2016 SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1554878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1386724] Re: totem shows dvd menus as black screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1386724 Title: totem shows dvd menus as black screen Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: totem 3.10.1-1ubuntu4 shows dvd menus as black screen. VLC Media player shows the correct menu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgstreamer1.0-0 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 28 15:35:30 2014 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2013-02-20 (615 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=de_DE PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to trusty on 2014-10-08 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1386724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624022] Please test proposed package
Hello Mark, or anyone else affected, Accepted xdg-utils into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xdg- utils/1.1.1-1ubuntu1.16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1624022 Title: Alias 'browse' to xdg-open Status in xdg-utils package in Ubuntu: Fix Released Status in xdg-utils source package in Xenial: Fix Committed Bug description: [Impact] The 'sensible-browser' and 'xdg-open' commands are very useful, but it's a bit unwieldy to use everywhere in docs. How about aliasing to the simple 'browse', so I can recommend things like: sudo apt install foo; browse http://locahost:2022/ That would be crisp clean and friendly for current users. [Test Case] There is currently no simple 'browse' command. [Regression Potential] None. There are no name collisions with /usr/bin/browse in Debian or Ubuntu. [ Other Info ] Although the original request was to alias 'sensible-browser' it was decided that 'xdg-open' has the more consistent behaviour (in terms of selecting the correct web browser to use) and also falls back to 'sensible-browser'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1624022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629754] Re: Add-ons not showing
Hello Robert, or anyone else affected, Accepted appstream-glib into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/appstream- glib/0.5.13-1ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1629754 Title: Add-ons not showing Status in appstream-glib package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Invalid Status in appstream-glib source package in Xenial: Fix Committed Status in appstream-glib source package in Yakkety: Fix Released Bug description: [Impact] Add-ons are not installable from GNOME Software. This is due to appstream-glib incorrectly filtering them out. [Test Case] 1. Open GNOME Software on Files app (gnome-software --details=org.gnome.Nautilus.desktop) 2. Browse add-ons Expected result: Can install/remove add-ons Observed result: No add-ons are shown (entire section is missing) [Regression Potential] By enabling add-ons there is a small risk of a new code-path being enabled that could expose a bug. This feature has been fixed in upstream git and Yakkety for some time so this risk seems low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1629754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630411] [NEW] bugs in the Ubuntu Software Store
Public bug reported: the store does not install or uninstall the packages correctly, you need to click several times on buttons the store does not install external packages .deb without first having given permission to the package Many packages do not have pictures ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-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: Tue Oct 4 18:29:00 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:10ac] InstallationDate: Installed on 2016-09-29 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. K45A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=a9b99d83-330d-4630-adcf-2214e79da046 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 230 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K45A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr230:bd01/24/2013:svnASUSTeKCOMPUTERINC.:pnK45A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK45A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K45A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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.3-1ubuntu2.3 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 Oct 4 16:15:14 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5272 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial ** Attachment added: "OMG that borders" https://bugs.launchpad.net/bugs/1630411/+attachment/4754544/+files/Picture1.png -- 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/1630411 Title: bugs in the Ubuntu Software Store Status in xorg package in Ubuntu: New Bug description: the store does not install or uninstall the packages correctly, you need to click several times on buttons the store does not install external packages .deb without first having given permission to the package Many packages do not have pictures ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-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: Tue Oct 4 18:29:00 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:10ac] InstallationDate: Installed on 2016-09-29 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. K45A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=a9b99d83-330d-4630-adcf-2214e79da046 ro quiet splash vt.handoff=7
[Desktop-packages] [Bug 1627641] Re: Backport netplan to xenial
Hello Martin, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1627641 Title: Backport netplan to xenial Status in network-manager package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Committed Bug description: For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more. netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager. PATCHES: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial=6dcdb85 https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=4e9c52b0bb REGRESSION POTENTIAL: netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades. NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work. systemd: This does change behavior of networkd quite a bit: RA is now being handled in userpsace instead of the kernel, there are some new virtual device types, LLDP support, etc., and there are no (known) backwards incompatibilities. The 229 version was known buggy with DHCPv6 (we disabled these two test cases), and judging by the feedback in Debian 231 is now reasonably stable. networkd is not being used by default or advertised in Ubuntu 16.04 (so far), so this will not affect the vast majority of installations. But while we have quite good test coverage, it cannot be ruled out that we break some custom setup that uses networkd. TEST PLAN: 1. Run "NetworkManager --print-config" and save the output. 2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work. 3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1. 4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp