Bug#772182: systemd: Systemd tries to mount swap partition twice at the same time
Hi Martin, I installed your packages and rebooted my machine twice. Judging by the boot messages, I think it worked. There is no fail status. However, is there anyway to double check whether it used the fstab mount instead of the gpt auto generator? Ben On Wed, Jan 28, 2015 at 12:53 AM, Martin Pitt mp...@debian.org wrote: Hey Benjamin, Benjamin Xiao [2014-12-05 14:41 -0800]: Systemd tries to mount my swap partition twice at the same time. One of the mount attempts is triggered by systemd-fstab-generator and the other attempt is triggered by systemd-gpt-auto-generator. There is a race condition and one of them will fail with Device or resource busy in journalctl. Upstream has a proposed patch for this. I built a package for sid/jessie for this, would you be able to test it? You can either download the .debs and install them through dpkg -i from https://people.debian.org/~mpitt/tmp/systemd-772182/ or you add this as an apt source and upgrade with echo 'deb http://people.debian.org/~mpitt/tmp/systemd-772182/ /' /etc/apt/sources.list.d/mpitt-systemd.list apt update apt upgrade (This will complain about the packages not being verifiable as they aren't signed). Thanks! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Bug#772182: systemd: Systemd tries to mount swap partition twice at the same time
Okay I have a file called /run/systemd/generator/dev-disk-by\x2duuid-4da077e7\x2db024\x2d475d\x2d913d\x2d18fa1ac70a39.swap that says its generated by the fstab generator. The other files are non-swap mounts Seems like its working! On Wed, Jan 28, 2015 at 2:37 AM, Martin Pitt mp...@debian.org wrote: Benjamin Xiao [2015-01-28 1:51 -0800]: However, is there anyway to double check whether it used the fstab mount instead of the gpt auto generator? You can look at the generated unit in /run/systemd/generator/*.mount. The first line is a comment saying which generator produced it. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Bug#772181: gedit: Printing an unsaved document disables editing
Package: gedit Version: 3.14.0-2 Severity: normal Dear Maintainer, Printing an unsaved document (fresh document, no file on disk yet) in gedit disables editing of the document indefinitely. The print icon still displays in the tab and in the bottom left corner and never goes away, even after printing is finished. I can not edit, paste, or save the file in this state. The only way I can edit it again is to copy the contents to another document. Printing documents that are already saved to disk works just fine. -- Package-specific info: Active plugins: - 'docinfo' - 'time' - 'spell' - 'modelines' - 'filebrowser' No plugin installed in $HOME. Module versions: - glib 2.42.0 - gtk+ - gtksourceview - pygobject - enchant - iso-codes 3.57 -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gedit depends on: ii gedit-common 3.14.0-2 ii gir1.2-peas-1.01.12.1-2 ii gnome-icon-theme-symbolic 3.12.0-1 ii gsettings-desktop-schemas 3.14.1-1 ii iso-codes 3.57-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-13 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libenchant1c2a 1.6.0-10.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgirepository-1.0-1 1.42.0-2.2 ii libglib2.0-0 2.42.0-2 ii libgtk-3-0 3.14.4-2 ii libgtksourceview-3.0-1 3.14.1-1 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-01.36.8-2 ii libpeas-1.0-0 1.12.1-2 ii libx11-6 2:1.6.2-3 ii libxml22.9.1+dfsg1-4 ii python3-gi 3.14.0-1 ii python3-gi-cairo 3.14.0-1 pn python3:anynone Versions of packages gedit recommends: ii yelp3.14.1-1 ii zenity 3.14.0-1 Versions of packages gedit suggests: ii gedit-plugins 3.14.0-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764926:
Perhaps its getting stuck on apt-listchanges? My offline update got stuck on boot. I pressed Q a couple of times hoping it was just not displaying apt-listchanges but it didn't do anything. I restarted my computer, installed the updates via synaptic and noticed no interactive prompts from the individual packages. Ben
Bug#702241: gnome-packagekit: gpk-update-viewer does not update package index so falsely says is up to date.
On Mon, 28 Apr 2014 11:16:34 +0200 Federico Bruni fedel...@gmail.com wrote: Package: gnome-packagekit Version: 3.10.1-1 Followup-For: Bug #702241 I can confirm the same problem on Jessie. gnome-settings-daemon is running. packagekitd was running, as you can see here: $ ps aux | grep packagekit root 8267 0.0 0.0 316432 6372 ?Sl 10:43 0:00 /usr/lib/packagekit/packagekitd but now it's not running anymore. No idea of the reason. Also, you can see in the attached screenshot the default settings for org.gnome.settings-daemon.plugins.updates: notify-distro-upgrades is unchecked. I am running Gnome 3.14 in Debian Jessie and I get no desktop notifications about new package updates either. I don't even have org.gnome.settings-daemon.plugins.updates in my dconf editor. I do have APT::Periodic::Update-Package-Lists 1 set though.
Bug#702241: gnome-packagekit: gpk-update-viewer does not update package index so falsely says is up to date.
Thanks for the update Matthias. I will definitely check how things are once Gnome-Software comes out of unstable. And yes, I agree that this is definitely a release-blocker. Not being properly notified of security updates is a huge issue. Ben On Wed, Nov 5, 2014 at 2:06 PM, Matthias Klumpp matth...@tenstral.net wrote: 2014-11-05 22:44 GMT+01:00 Benjamin Xiao ben.r.x...@gmail.com: On Mon, 28 Apr 2014 11:16:34 +0200 Federico Bruni fedel...@gmail.com wrote: Package: gnome-packagekit Version: 3.10.1-1 Followup-For: Bug #702241 I can confirm the same problem on Jessie. gnome-settings-daemon is running. packagekitd was running, as you can see here: $ ps aux | grep packagekit root 8267 0.0 0.0 316432 6372 ?Sl 10:43 0:00 /usr/lib/packagekit/packagekitd but now it's not running anymore. No idea of the reason. Also, you can see in the attached screenshot the default settings for org.gnome.settings-daemon.plugins.updates: notify-distro-upgrades is unchecked. I am running Gnome 3.14 in Debian Jessie and I get no desktop notifications about new package updates either. I don't even have org.gnome.settings-daemon.plugins.updates in my dconf editor. I do have APT::Periodic::Update-Package-Lists 1 set though. With GNOME 3.14 the code for performing those tasks has been moved to GNOME-Software, which is in unstable at time. This situation is a terrible mess now, not only for other desktops but also for GNOME. We are working on a solution for that, so we can release Jessie with update-notifications. (I would consider having this working a release-blocker, but the release-team has the final word on this) Regards, Matthias -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/
Bug#765551:
Okay, I've done a little debugging and it seems to be a bug in the Intel UXA drivers. I switched to SNA and all three monitors work fine now. I added the following lines to a new file in /etc/X11/xorg.conf.d/20-intel.conf: Section Device Identifier Intel Graphics Driver intel Option AccelMethod sna EndSection -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765513:
I can confirm that this bug happens with an up to date Debian jessie install. Running from command line works fine. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765551: All 3 monitors show a black screen on GDM start when OneLink Pro dock is connected to Lenovo X1 Carbon
Package: gdm3 Version: 3.13.92-1 I have a Lenovo X1 Carbon Type 20A8 laptop with a OneLink Pro dock. I have two external monitors, one connected to the mini-DisplayPort on the laptop itself and another connected to the DVI port on the dock. Under Ubuntu 14.04, I am able to drive all 3 displays (laptop built-in display and the two external monitors) just fine. Under Debian the behavior is quite weird: *If I have the dock plugged in before boot, all 3 screens are black once GDM launches into the login screen. *If I have the dock plugged in after boot and all 3 displays are enabled in the GNOME Display settings, then everything turns black, but I can see the mouse cursor moving around. *If I plug in one of the monitors to the mini-DisplayPort, disable the laptop built-in display, and THEN plug in the dock, I can drive the two external screens fine. Expected behavior: I should be able to drive all 3 displays just fine and unplug each external monitor and have it dynamically readjust. The Xorg log looked okay to my untrained eye. I am unsure of which logs to attach. Please let me know which ones you guys need to debug this and I will be happy to get it to you ASAP. I am using an up to date Debian testing with kernel 3.16-2-amd64 and libc6 2.19-11 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
