Bug#794969: udev: change in network device naming scheme unnecessarily and incorrectly renames WiMAX devices

On Sun, Aug 09, 2015 at 05:54:29PM +0200, Marco d'Itri wrote: > On Aug 08, "brian m. carlson" wrote: > > > Previously, my WiMAX device was named something like wmx0. Now, it > > appears it's been renamed to enx. First of all, the name > > has change

Bug#794969: udev: change in network device naming scheme unnecessarily and incorrectly renames WiMAX devices

ibudev1224-1 ii lsb-base4.1+Debian13+nmu1 ii procps 2:3.3.10-2 ii util-linux 2.26.2-9 udev recommends no packages. udev suggests no packages. -- debconf information excluded -- brian m. carlson / brian with sandals: Houston, Texas, US

Bug#790262: systemd: warns that service changes on disk instead of just reloading

ii util-linux 2.26.2-6 Versions of packages systemd recommends: ii dbus1.8.18-1 ii libpam-systemd 220-7 Versions of packages systemd suggests: pn systemd-ui -- Configuration Files: /etc/systemd/system.conf changed [not included] -- no debconf information -- brian m. carls

Bug#770644: systemd: can't start dbus if dbus is not running

crash. I don't know why it happened. All I know is that systemd stopped working on my server and my laptop, once each, randomly. I've provided you with everything I know about the problem. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoo

Bug#770644: systemd: can't start dbus if dbus is not running

later. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital sign

Bug#770644: systemd: can't start dbus if dbus is not running

On Sat, Mar 07, 2015 at 12:47:33AM +0100, Michael Biebl wrote: control: tags -1 moreinfo Am 22.11.2014 um 23:33 schrieb brian m. carlson: retitle 770644 systemd: systemd is completely unusable after a fatal signal # Justification: breaks the whole system, not suitable for release severity

Bug#779966: file-hierarchy(7): falsely states /bin, /sbin, /usr/sbin, and /lib are compatibility symlinks

-linux 2.25.2-5 Versions of packages systemd recommends: ii dbus1.8.16-1 ii libpam-systemd 215-12 Versions of packages systemd suggests: pn systemd-ui -- Configuration Files: /etc/systemd/system.conf changed [not included] -- no debconf information -- brian m. carlson /

Bug#770644: systemd: can't start dbus if dbus is not running

dev215-6 ii util-linux 2.25.2-3 Versions of packages systemd recommends: ii dbus1.8.10-1 ii libpam-systemd 215-6 Versions of packages systemd suggests: pn systemd-ui -- Configuration Files: /etc/systemd/system.conf changed [not included] -- no debconf information

Bug#762041: systemd: upgrading systemd results in /run/user/ being emptied

om a MATE terminal. Since I'm the only user of both machines (they're laptops), I never log in more than once on the same machine, unless you define "logging in" as entering the screensaver password, which I actually do very frequently. -- brian m. carlson / brian with sandals: H

Bug#762041: systemd: upgrading systemd results in /run/user/ being emptied

systemd/system.conf changed: [Manager] LogLevel=warning LogTarget=console -- no debconf information -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0

Bug#757302: systemd: should ignore files ending in .dpkg-tmp

commends: ii libpam-systemd 208-6 Versions of packages systemd suggests: pn systemd-ui -- Configuration Files: /etc/systemd/system.conf changed: [Manager] LogLevel=warning LogTarget=console -- no debconf information -- brian m. carlson / brian with sandals: Houston, Texas, US +1

Bug#755120: mate-power-manager,systemd: suspend happens twice

reason for this behavior change? It's not very reasonable to expect all existing desktop environments to support a new API when they worked perfectly well before that API existed. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~b

Bug#755120: mate-power-manager,systemd: suspend happens twice

On Wed, Aug 06, 2014 at 02:37:41PM +, Mike Gabriel wrote: > Hi Brian, > > On Mi 06 Aug 2014 00:28:40 CEST, brian m. carlson wrote: > > >On Tue, Aug 05, 2014 at 03:14:34PM +, Mike Gabriel wrote: > >>Is is possible that your machine has systemd _and_ consoleki

Bug#755120: mate-power-manager,systemd: suspend happens twice

On Tue, Aug 05, 2014 at 03:14:34PM +, Mike Gabriel wrote: > Is is possible that your machine has systemd _and_ consolekit installed? > That would explain the double-suspend-action. Yes. It's a dependency of mate-power-manager. -- brian m. carlson / brian with sandals: Houston, T

Bug#755120: mate-power-manager,systemd: suspend happens twice

Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion