[Bug 1297849] Re: [SRU] Virtual private network connection fails after distribution upgrade due to outdated Network Manager configuration files
** Also affects: network-manager-vpnc Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1297849 Title: [SRU] Virtual private network connection fails after distribution upgrade due to outdated Network Manager configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1297849/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1377897] Re: [Ubuntu trusty]Errors while using gedit
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gedit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1377897 Title: [Ubuntu trusty]Errors while using gedit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1377897/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1377897] Re: [Ubuntu trusty]Errors while using gedit
Happens when I use gksudo (not sudo) Tahr with Gnome-flashback, fully updated -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1377897 Title: [Ubuntu trusty]Errors while using gedit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1377897/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1560162] Re: Xenial: scaling is horribly out on xps13 install session
This issue is happening in OOBE. Enable -proposed then update is only available after boot into OS. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1560162 Title: Xenial: scaling is horribly out on xps13 install session To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1560162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
Having too on desktop ubuntu lts 16.04.1 with usb 3.0, new hdd, ntfs. Also, speed continuously slowing down and then freezes and power led of the disk start flapping. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1208993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 967471] Re: eog 3.2.1 doesn't display raw files
** Bug watch added: GNOME Bug Tracker #344601 https://bugzilla.gnome.org/show_bug.cgi?id=344601 ** Also affects: eog via https://bugzilla.gnome.org/show_bug.cgi?id=344601 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/967471 Title: eog 3.2.1 doesn't display raw files To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/967471/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1061195] Re: Evolution appears unable to create EWS or Exchange MAPI account
Same problem, 2016. Restarting works. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1061195 Title: Evolution appears unable to create EWS or Exchange MAPI account To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-ews/+bug/1061195/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626935] Re: [Yakkety] desktop in black background on extended HDMI display
Workarounds: (a) Plug your monitor in before logging in; or (b) Kill and restart nautilus. Given that the desktop selection rectangle still works while the black/flickering is happening around it, it appears the only thing that's broken is nautilus' wallpaper logic. ** Summary changed: - [Yakkety] desktop in black background on extended HDMI display + [yakkety] desktop is black and/or flickering after plugging in a second monitor ** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Changed in: nautilus (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1626935 Title: [yakkety] desktop is black and/or flickering after plugging in a second monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1626935/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626935] Re: [Yakkety] desktop in black background on extended HDMI display
Also not a compiz bug. The problem still happens if I replace compiz with metacity. ** Changed in: compiz (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1626935 Title: [Yakkety] desktop in black background on extended HDMI display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1626935/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1635023] [NEW] yakkkety boot is erratic
Public bug reported: After an upgrade from xenial to yakkety, the system does not boot reliably. Only 1 boot over 3-4 seems to succeed. Quite often, the system seems to hang during boot and then drops into an emergency prompt. Pressing esc during the boot to show what is going on reveals that there are processes waiting for the disks to become ready. This is likely to be related to the specific system configuration, with a raid array of two disks managed by dmraid (it is an intel fake raid) and lvm2 on top of it. Most stuff is on it in logical disks, but for the boot partition that is on a fast ssd, and the root of the filesystem that is on lvm2 with a physical volume spanning the rest of the ssd. The very same configuration worked just fine on xenial. To make the matter worse, it is impossible to boot in "recovery mode" to get a root prompt, because after you login as root something suddenly times out and the screen gets messed up (not a graphics card issue, but pieces of messages popping out here and there, the recovery mode menu suddenly reappearing, etc. Please give this bug appropriately high priority, because it prevents servers from coming up after power failures. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 19 21:34:16 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Precision WorkStation T5400 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/vg_ssd-root ro quiet splash mtrr_gran_size=2g mtrr_chunk_size=2g resume=/dev/sdc3 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago) dmi.bios.date: 04/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0RW203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/30/2012:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T5400 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1635023 Title: yakkkety boot is erratic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635023/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags added: yakkety -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Just go this upgrading from 16.04 to 16.10. I had to dismiss 51 (!!!) identical dialogues about this failure during the upgrade before it finally quit entirely. It seems to have finished, though, and my system is up to date and stable so far. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes
Me too after upgrade from 16.04 to 16.10. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1620806 Title: gedit edit window is transparent when using Ambiance and Radiance themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1620806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1634977] [NEW] gedit crashes with enabled gedit-latex-plugin
Public bug reported: running ubuntu 16.10, uptodate. installed gedit-latex-plugin and enabled that in the settings menu. after that gedit crashes on startup. only removing the gedit-latex-plugin package helps. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gedit 3.22.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 19 19:12:23 2016 InstallationDate: Installed on 2013-09-28 (1117 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) SourcePackage: gedit UpgradeStatus: Upgraded to yakkety on 2016-09-27 (22 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Affects: gedit-latex-plugin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Also affects: gedit-latex-plugin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1634977 Title: gedit crashes with enabled gedit-latex-plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1634977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'
This bug affects me as well. It was an upgrade from 16.04 to 16.10. It is not possible to open the recents tab in nautilus. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1633162 Title: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1633162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1634767] Re: Shotwell 0.22.0 Ubuntu 16.10 trash process not working as expected
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Package changed: linux (Ubuntu) => shotwell (Ubuntu) ** Changed in: shotwell (Ubuntu) Importance: Medium => Undecided ** Changed in: shotwell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1634767 Title: Shotwell 0.22.0 Ubuntu 16.10 trash process not working as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1634767/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1634767] [NEW] Shotwell 0.22.0 Ubuntu 16.10 trash process not working as expected
You have been subscribed to a public bug: Using "Delete" or "Empty Rubbish Bin" with the "remove and trash" option in Shotwell 0.22.0 rubbish bin, files do not appear in system rubbish bin as expected in Ubuntu 16.10. However, the aforementioned files do appear in the system rubbish bin when viewed in Ubuntu 14.04 so Shotwell 0.22.0 in Ubuntu 16.10 seems to have performed correctly. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: magnus 2288 F...m pulseaudio /dev/snd/controlC0: magnus 2288 F pulseaudio DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=44b7dea2-a8b4-4188-b45e-8d90cd697dc7 InstallationDate: Installed on 2016-10-16 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0951:1665 Kingston Technology Digital DataTraveler SE9 64GB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E402MA Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed root=/dev/mmcblk0p2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402MA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402MA 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.:bvrE402MA.204:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnE402MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E402MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: 0.22.0 apport-collected shotwell yakkety -- Shotwell 0.22.0 Ubuntu 16.10 trash process not working as expected https://bugs.launchpad.net/bugs/1634767 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1634939] [NEW] Copy progress popover should close on completion
Public bug reported: When copying folders/files and the popover progress window opens it pops up in all opened instances of Nautilus. You also need to close the popover on every single window or close every window to get it to disappear. This also applies to the progress-bar in launcher. Expected behavior: copy popover should close after successfully performing the copy operation. Ubuntu 16.10 Nautilus 1:3.20.3-1ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Instances of completed copy operations" https://bugs.launchpad.net/bugs/1634939/+attachment/4763810/+files/Sk%C3%A4rmbild%20fr%C3%A5n%202016-10-19%2016-41-20.png ** Description changed: When copying folders/files and the popover progress window opens it pops up in all opened instances of Nautilus. You also need to close the popover on every single window or close every window to get it to - disappear. This aöso applies to the progress-bar in launcher. + disappear. This also applies to the progress-bar in launcher. Expected behavior: copy popover should close after successfully performing the copy operation. Ubuntu 16.10 Nautilus 1:3.20.3-1ubuntu3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1634939 Title: Copy progress popover should close on completion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1634939/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626935] Re: [Yakkety] desktop in black background on extended HDMI display
yeah I moved it to mesa until I've verified with the older version, and it's still happening even with -intel + mesa 11.2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1626935 Title: [Yakkety] desktop in black background on extended HDMI display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1626935/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gedit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1620806 Title: gedit edit window is transparent when using Ambiance and Radiance themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1620806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1620806 Title: gedit edit window is transparent when using Ambiance and Radiance themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1620806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626935] Re: [Yakkety] desktop in black background on extended HDMI display
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: compiz (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1626935 Title: [Yakkety] desktop in black background on extended HDMI display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1626935/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626935] Re: [Yakkety] desktop in black background on extended HDMI display
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 Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1626935 Title: [Yakkety] desktop in black background on extended HDMI display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1626935/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626935] Re: [Yakkety] desktop in black background on extended HDMI display
Well I used to maintain compiz so have a rough idea. The desktops is just a window from nautilus that is composited by compiz. The bug probably lays between those. Not Mesa. ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1626935 Title: [Yakkety] desktop in black background on extended HDMI display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1626935/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626935] Re: [Yakkety] desktop in black background on extended HDMI display
Someone who knows better how the background is drawn on unity/compiz should probably comment what changed. With -intel X driver it's still the same, so defaulting to modeset X driver didn't cause this. ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1626935 Title: [Yakkety] desktop in black background on extended HDMI display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1626935/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1634855] [NEW] Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.
Public bug reported: Hi, the net of my PC is configured via systemd-networkd + systemd-resolved. And last two weeks I faced with the problem when my net is down. "journalctl -xe" helped to detect this issue: окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers for interface enp3s0, ignoring: Argument list too long окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting. окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers for interface enp3s0, ignoring: Argument list too long When I type "systemctl restart systemd-networkd", nothing happens, net is still down. When I type "systemctl restart systemd-resolved", it's all starting to work fine, as usual. A little bit of googling gave me this bug in systemd bugtracker: https://github.com/systemd/systemd/issues/2228 and this PR: https://github.com/systemd/systemd/pull/3224 Looks like this issue was fixed in systemd-230. So can you backport this patch to systemd package? I can patch it and test it myself, actually, but it would be really nice if there will be no need to. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu11 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 Date: Wed Oct 19 13:58:42 2016 InstallationDate: Installed on 2016-09-29 (19 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1634855 Title: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1634855/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318168] Re: su: Failed to create session: No such file or directory
** Package changed: ejabberd (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1318168 Title: su: Failed to create session: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1318168/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318168] [NEW] su: Failed to create session: No such file or directory
You have been subscribed to a public bug: I am using the command "su" quite often without any problems. The following "su" is just a senseless example, but it will demonstrate the problem quite well. In this example I want to make an echo as sshd user (could be any other user like www-data, rabbitmq, or others as well): su sshd -s /bin/sh -c echo Doing this worked find, but beginning with Ubuntu 14.04, I get strange log entries in /var/log/auth.log like: May 10 14:21:18 abel su[22315]: Successful su for sshd by root May 10 14:21:18 abel su[22315]: + /dev/pts/2 root:sshd May 10 14:21:18 abel su[22315]: pam_unix(su:session): session opened for user sshd by root(uid=0) May 10 14:21:18 abel su[22315]: pam_systemd(su:session): Failed to create session: No such file or directory May 10 14:21:18 abel su[22315]: pam_unix(su:session): session closed for user sshd Especially the 4th line with "Failed to create session: No such file or directory" didn't appear on earlier system. With Ubuntu 13.10 it looked like this: May 10 14:22:30 davy su[18202]: Successful su for sshd by root May 10 14:22:30 davy su[18202]: + /dev/pts/1 root:sshd May 10 14:22:30 davy su[18202]: pam_unix(su:session): session opened for user sshd by root(uid=0) May 10 14:22:30 davy su[18202]: pam_unix(su:session): session closed for user sshd the /etc/passwd for user sshd is the same on 13.10 and 14.04: sshd:x:103:65534::/var/run/sshd:/usr/sbin/nologin Changing shell to /bin/false or /bin/sh or alike doesn't help. The problem is, that certain monitoring or security systems don't this entry and are complaining all the time. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed -- su: Failed to create session: No such file or directory https://bugs.launchpad.net/bugs/1318168 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
