Bug#738687: systemd does not mount /tmp as tmpfs (even if RAMTMP=yes in rcS)

Hello, Am 12.02.2014 01:06, schrieb pa...@ucw.cz: > Dear Maintainer, > > even though I have RAMTMP=yes in /etc/default/rcS, recently (~2w ago?) > installed systemd will not mount /tmp as tmpfs. > > Of course, /etc/default/rcS is not a configuration file of systemd so I > wouldn't consider a bug

Bug#731530: rsyslog init script breaks after package upgrade

Am 06.12.2013 11:17, schrieb Chris Butler: > Package: rsyslog > Version: 5.8.11-3 > Severity: normal > > Dear Maintainer, > > Following a recent upgrade from squeeze to wheezy (although this would be > trigged by any package update it seems), we noticed that rsyslog was not > logging to the corre

Bug#731649: [Pkg-systemd-maintainers] Bug#731649: systemd: sleep key no longer suspends - just locks + blanks screen

Am 07.12.2013 21:17, schrieb Jonathan McDowell: > Package: systemd > Version: 204-5 > Severity: normal > > This could be a gnome-power-manager (3.8.2-1) or upower (0.9.23-2+b1) > issue, but it seems to have started at the point a GNOME upgrade pulled > in systemd for logind. > > Since this time m

Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Am 09.12.2013 10:44, schrieb Bart-Jan Vrielink: > Package: systemd > Version: 204-5 > Severity: normal > > Dear Maintainer, > > When running under systemd, syslog.socket will not start. Because of this, > rsyslog does not start via the init.d script. Rsyslogd works when invoked > directly, and

Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Am 09.12.2013 11:45, schrieb Bart-Jan Vrielink: > > -Original message- >> From:Michael Biebl mailto:em...@michaelbiebl.de> > >> Sent: Monday 9th December 2013 11:34 >> To: Bart-Jan Vrielink mailto:bart...@vrielink.net> >; >> 731...@bugs.debian.org >> Subj

Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

Am 09.12.2013 12:55, schrieb Bart-Jan Vrielink: >> Is rsyslog properly enabled? >> # sudo systemctl status rsyslog.service >> # ls -la /etc/systemd/system/syslog.service > > bartjan@fenchurch:~$ sudo systemctl status rsyslog.service > [sudo] password for bartjan: > rsyslog.service - System Loggin

Bug#731887: systemd: Lid close on laptop doesn't suspend

Am 10.12.2013 21:51, schrieb John Hughes: > Package: systemd > Version: 204-5 > Severity: normal > > Dear Maintainer, > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > Closed laptop lid > >* What was the outcome of this action? > > Nothing > >

Bug#731887: systemd: Lid close on laptop doesn't suspend

Am 11.12.2013 09:48, schrieb John Hughes: > On 12/10/2013 11:37 PM, Michael Biebl wrote: >> Please post the output of systemd-inhibit --list before you do such a >> lid-close. > > # systemd-inhibit --list > Who: john (UID 1000/john, PID 3736/gnome-settings-) >

Bug#725714: udev firmware loading does not work in the Debian installer

Am 13.12.2013 00:12, schrieb Andreas Cadhalpun: > The Debian installer needs a way to load the firmware during > installation, otherwise the netinst.iso is pretty useless for WLAN > devices with non-free firmware. > Since a majority of the WLAN devices need non-free firmware, just > dropping this f

Bug#725714: udev firmware loading does not work in the Debian installer

Am 13.12.2013 00:26, schrieb Michael Biebl: > Am 13.12.2013 00:12, schrieb Andreas Cadhalpun: >> The Debian installer needs a way to load the firmware during >> installation, otherwise the netinst.iso is pretty useless for WLAN >> devices with non-free firmware. >> S

Bug#725714: udev firmware loading does not work in the Debian installer

Am 13.12.2013 00:34, schrieb Michael Biebl: > According to codesearch.d.n, hw-detect is the only tool using > /run/udev/firmware-missing. I'm inclined to re-assign this bug to > hw-detect and let the hw-detect maintainers decided how to handle this. > If something like the isenkr

Bug#732165: systemd service is disabled after the switch to dh-systemd

Package: avahi-daemon Version: 0.6.31-3 Severity: serious The switch from static symlinks to dh-systemd seems to not be handled properly in 0.6.31-3. After the upgrade the service is no longer started at boot under systemd, thus marking as RC (to prevent testing migration) $ systemctl status avah

Bug#732195: [Pkg-utopia-maintainers] Bug#732195: udisks2: KDE usb key insertion notification fails to mount usk disks

tags 732195 - patch thanks Am 15.12.2013 15:32, schrieb Eric Valette: > Package: udisks2 > Version: 2.1.1-1 > Severity: important > Tags: patch > > I recently discovered after installing udisk2 that all my kde setup (various > machines) fails to mount usb keys. After googling a bit, this is due t

Bug#732195: [Pkg-utopia-maintainers] Bug#732195: Bug#732195: udisks2: KDE usb key insertion notification fails to mount usk disks

Am 15.12.2013 15:49, schrieb Eric Valette: > On 15/12/2013 15:46, Michael Biebl wrote: >> tags 732195 - patch >> thanks >> >> Am 15.12.2013 15:32, schrieb Eric Valette: >>> Package: udisks2 >>> Version: 2.1.1-1 >>> Severity: important >>

Bug#732195: [Pkg-utopia-maintainers] Bug#732195: Bug#732195: udisks2: KDE usb key insertion notification fails to mount usk disks

Am 15.12.2013 16:02, schrieb Eric Valette: > On 15/12/2013 16:00, Michael Biebl wrote: >> Am 15.12.2013 15:49, schrieb Eric Valette: >>> On 15/12/2013 15:46, Michael Biebl wrote: >>>>> pn policykit-1 >> >> Install policykit-1 and you should be all se

Bug#732195: [Pkg-utopia-maintainers] Bug#732195: Fwd: Re: Bug#732195: Bug#732195: udisks2: KDE usb key insertion notification fails to mount usk disks

Am 15.12.2013 22:24, schrieb Eric Valette: > >> There you have your problem: >> You use policykit-1 from experimental which uses systemd-logind as >> backend but you don't have a logind session registered. >> >> An educated guess is, that you don't have libpam-systemd installed >> (which is instal

Bug#732195: [Pkg-utopia-maintainers] Bug#732195: Fwd: Re: Bug#732195: Bug#732195: udisks2: KDE usb key insertion notification fails to mount usk disks

Am 15.12.2013 22:24, schrieb Eric Valette: > > Which package recommends it? As I have the problem on all my machines I > assume, I got no recommends at all. So please add the recommends before > closing There is nothing to fix. If people disable (or don't install) recommends, they should know wha

Bug#615196: [Pkg-xfce-devel] Bug#615196: Please stop using hal

Am 23.07.2013 07:10, schrieb Yves-Alexis Perez: > On mar., 2013-07-23 at 04:00 +0200, Michael Biebl wrote: >> I see, only squeeze remains. Would it be possible to remove it from the >> archive, so thunar-vfs can be dropped? >> > See above. thunar-vfs and squeeze have bee

Bug#615196: [Pkg-xfce-devel] Bug#615196: Please stop using hal

Am 16.10.2013 15:58, schrieb Michael Biebl: > Ping? What's the status on getting squeeze updated? > If squeeze is not updated, would you be ok with removing it from the > archive? It's not like it couldn't be re-introduced whenever it is fixed. Just a side note: afaics the

Bug#726454: gnome-shell: Reads files on (gvfs-show) mountpoints after unlock

severity 726454 minor thanks Am 16.10.2013 16:16, schrieb Julian Andres Klode: > On Wed, Oct 16, 2013 at 01:35:33PM +0200, Michael Biebl wrote: >> >> It seems to somehow gets stuck on your system. As said, maybe running it >> in debug mode will give more info. >> &g

Bug#726558: pu: package policykit-1/0.105-3+deb7u1

45b..1644c95 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +policykit-1 (0.105-3+deb7u1) stable; urgency=low + + * Fix CVE-2013-4288: race condition in pkcheck. (Closes: #723717) + + -- Michael Biebl Wed, 16 Oct 2013 18:35:01 +0200 + policykit-1 (0.105-3) unstable; urgency=low

Bug#726563: gnome-session-flashback: please, make gnome-screensaver a recommends instead of a depends

Am 16.10.2013 18:56, schrieb Rogério Brito: > Package: gnome-session-flashback > Version: 3.6.2-2 > Severity: wishlist > > > Hi. > > I installed gnome-session-flashback and I would like to thank you people for > keeping it alive (depending on my free time, I may even lend a hand with the > maint

Bug#726575: RequiredComponents=[...]; nautilus-classic; in gnome-flashback.session.desktop

Am 16.10.2013 21:54, schrieb Fabian Greffrath: > package: gnome-session-flashback > version: 3.6.2-1 > severity: minor > > Hi there, > > I have seen that for the first upload to unstable of the > gnome-session-flashback package, you disabled the > 00_dont-require-nautilus-classic.patch patch. >

Bug#721962: goto-common: Drop unused hwinfo dependency

+0200 @@ -1,3 +1,10 @@ +goto-common (3.1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Drop unused dependency on hwinfo (Closes: #721962) + + -- Michael Biebl Thu, 17 Oct 2013 04:58:36 +0200 + goto-common (3.1-1) unstable; urgency=low * Converted to debian packaging 3.0 diff -Nru

Bug#726575: RequiredComponents=[...]; nautilus-classic; in gnome-flashback.session.desktop

retitle 726575 gnome-session-flashback needs a versioned depdendency on nautilus >= 3.8 severity 726575 important thanks Am 17.10.2013 06:25, schrieb Fabian Greffrath: > Am Mittwoch, den 16.10.2013, 22:12 +0200 schrieb Michael Biebl: >> /usr/share/applications/nautilus-classic.de

Bug#689858: Bug#715555: gnome package has icedove and xul-ext-adblock-plus incompatibility

to Suggests. Icedove and Iceweasel receive major updates via stable-security causing them to get out of sync and making xul-ext-adblock-plus and thus the gnome metapackage uninstallable. Closes: #71 -- Michael Biebl Thu, 26 Sep 2013 11:54:31 +0200 This was already addressed in

Bug#726625: gnome-shell: media-keys plugin not working; JS ERROR

Am 17.10.2013 14:01, schrieb Leo Antunes: > Package: gnome-shell > Version: 3.8.4-4 > Severity: important > > Dear Maintainer, > > None of the keybindings associated with the media-keys plugin are > working and the plugin itself seems to be crashing with the following > error: > > --

Bug#726631: vinagre: Please add spice support

Am 17.10.2013 14:34, schrieb Dani Chaves: > Package: vinagre > Version: 3.8.3-1 > Severity: wishlist > > The package 'libspice-client-gtk-3.0-dev' should be added to Build-Depends. > That package is only available on i386 and amd64. So if we enable spice support, this b-dep needs to be arch-qual

Bug#726647: gedit: right-click context menu is rendered in a monospace font

Am 17.10.2013 19:01, schrieb Fabian Greffrath: > Package: gedit > Version: 3.8.3-3+b1 > Severity: minor > > Hi, > > i wonder why the right-click context menu is rendered in a monospace font that > doesnt match the visual appearance of the other Gnome applications. The context menu seems to use t

Bug#726763: gnome-settings-daemon: no suspend on close lid, action not configurable, key missing

Am 18.10.2013 21:40, schrieb Johannes Rohr: > Package: gnome-settings-daemon > Version: 3.8.5-2 > Severity: normal > > Gnome-settings-daemon 3.8.5 does not suspend the laptop when I close the lid > while running on battery > > The respective action is not configurable in gnome-control-center. >

Bug#726996: /lib/systemd/systemd-timedated: /etc/localtime should be a symbolic link to a timezone data file in /usr/share/zoneinfo/

forcemerge 726256 726996 thanks Am 21.10.2013 13:12, schrieb Laurent Bigonville: > Package: systemd > Version: 204-5 > Severity: normal > File: /lib/systemd/systemd-timedated > > Hi, > > On my system, timedated is complaining about: > > systemd-timedated[17739]: /etc/localtime should be a symbo

Bug#727009: FTBFS on kfreebsd-i386: FAIL: test-pangocairo-threads

Source: pango1.0 Version: 1.36.0-1 Severity: serious User: debian-...@lists.debian.org pango1.0 FTBFS on kfreebsd-i386 when executing the test-suite: /«PKGBUILDDIR»/./test-driver: line 95: 41714 Trace/breakpoint trap "$@" > $log_file 2>&1 FAIL: test-pangocairo-threads Full build log at [1]

Bug#727016: Systemd upgrade restored deleted configuration file

Hi, Am 21.10.2013 15:36, schrieb John Williams: > I deleted the file: > /etc/systemd/system/getty.target.wants/getty@tty1.service > (I replaced it by my own login service file with a different name) > and a recent upgrade to systemd restored the missing file. I hope you didn't place a real file

Bug#727016: Systemd upgrade restored deleted configuration file

[please always CC the bug report, quoting your reply in full] Am 21.10.2013 17:07, schrieb John Williams: > On Mon, 21 Oct 2013 16:43:33 +0200 > Michael Biebl wrote: > >> We'd have to mangle the conffiles manually to achieve that, but I'm a >> bit worried about

Bug#727057: [Pkg-utopia-maintainers] Bug#727057: network-manager: Fails to install if netdev group already exists

Am 21.10.2013 23:51, schrieb Andrew Ruthven: > Package: network-manager > Version: 0.9.8.0-5 > Severity: normal > > Dear Maintainer, > > While upgrade my Sid box, network-manager failed to install cause the postinst > exited as the netdev group already exists, causing the addgroup command > to fa

Bug#727057: [Pkg-utopia-maintainers] Bug#727057: network-manager: Fails to install if netdev group already exists

Am 22.10.2013 00:24, schrieb Andrew Ruthven: > On Tue, 2013-10-22 at 00:05 +0200, Michael Biebl wrote: >> This getent check is not necessary: >> # addgroup --system netdev >> addgroup: The group `netdev' already exists as a system group. Exiting. >> # echo $? >

Bug#727089: zeitgeist-daemon.bash_completion: No such file or directory

On Tue, Oct 22, 2013 at 11:14:43AM +0200, Laurent Bigonville wrote: > This is due to a conffile (/etc/bash_completion.d/zeitgeist-daemon) not > being removed on upgrade. Removing the obsolete conffile /etc/bash_completion.d/zeitgeist-daemon is not sufficient for me. I'm still getting the error aft

Bug#727089: zeitgeist-daemon.bash_completion: No such file or directory

Am 22.10.2013 13:56, schrieb Michael Biebl: > On Tue, Oct 22, 2013 at 11:14:43AM +0200, Laurent Bigonville wrote: >> This is due to a conffile (/etc/bash_completion.d/zeitgeist-daemon) not >> being removed on upgrade. > > Removing the obsolete conffile /etc/bash_completion.d/

Bug#727126: Please update to upstream version 0.1.8

Source: libestr Version: 0.1.5-2 Severity: wishlist Hi, I'd like to update rsyslog to version 7.4.5. This requires libestr 0.1.8 [1]. Would be great if you can update libestr accordingly. A corresponding backports upload would be appreciated as well. Regards, Michael [1] http://www.rsyslog.com

Bug#723512: rsyslog link with -L/usr/lib

tags 723512 + moreinfo thanks Am 17.09.2013 12:53, schrieb YunQiang Su: > Package: rsyslog > Version: 7.4.4-1 > X-Debbugs-CC: wzss...@gmail.com > > This package has one or more -L/usr/lib in its build system, > which will make it ftbfs if there is libraries under /usr/lib, > while is not the defa

Bug#727127: libpeas: FTBFS on several architectures were it built in the past (regression)

Am 22.10.2013 15:52, schrieb Niels Thykier: > Package: libpeas > Version: 1.8.1-2 > Severity: serious > > Hi, > > Your package FTBFS on ia64, powerpc and sparc, but it built on these > architectures in the past. This FTBTS blocks testing migration. There weren't any source code related changes

Bug#727157: FTBFS on various architectures

Source: llvm-toolchain-3.3 Version: 1:3.3-10 Severity: serious llvm 3.3 FTBFS on various architectures, most notably i386. Full build logs can be found at https://buildd.debian.org/status/package.php?p=llvm-toolchain-3.3 -- System Information: Debian Release: jessie/sid APT prefers unstabl

Bug#706457: looks like notifications are causing the issue

severity 706457 important tags 706457 + moreinfo unreproducible thanks Am 14.10.2013 12:24, schrieb Michael Biebl: > Am 03.05.2013 14:04, schrieb Praveen A: > > Aside from that: can you reproduce the problem on and up-to-date sid > system? Did you get the hangs with gnome-shell

Bug#727201: [Pkg-utopia-maintainers] Bug#727201: gnome-disk: Error creating partition

reassign 727201 udisks2 found 727201 2.1.1-1 thanks Am 23.10.2013 12:56, schrieb Adnan Hodzic: > Package: gnome-disk-utility > Version: 3.10.0-1 > Severity: normal > File: gnome-disk > > Hello, > > When I try to create partitions or remove them (doesn't matter which > filesystem), I get a follow

Bug#724731: g_get_user_runtime_dir () bug

Am 23.10.2013 13:01, schrieb Simon McVittie: > On 23/10/13 08:07, Gabriel Mainberger wrote: >> user@machine:~/Work$ gcc `pkg-config --cflags --libs glib-2.0` -o run run.c >> >> user@machine:~/Work$ ./run >> /run/user/0 > > What's your $XDG_RUNTIME_DIR environment variable? > > If it's /run/user/0

Bug#727174: pango1.0 FTBFS with glib2.0 (>= 2.37.2), G_TEST_SRCDIR undefined

severity 727174 important thanks Am 23.10.2013 03:10, schrieb Steve Langasek: > Hi folks, > > The pango1.0 package in unstable fails to build from source with the version > of glib2.0 in experimental, because with newer glib2.0 pango makes use of a > new API called "g_test_get_filename" which rel

Bug#727209: Switch to .xz tarballs in debian/watch

Source: librest Version: 0.7.12-1 Severity: normal Upstream [1] no longer produces any .bz2 tarballs, but only .xz tarballs. Please update debian/watch accordingly -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Arch

Bug#727210: Please update Homepage: URL

Source: librest Version: 0.7.12-1 Severity: minor librest use the rather generic Homepage: http://www.gnome.org/ Since there is a dedicated website https://wiki.gnome.org/Librest I would suggest using that as Homepage -- System Information: Debian Release: jessie/sid APT prefers unstable AP

Bug#727605: Add support for systemd inhibit API

Package: xfce4-power-manager Version: 1.2.0-2 Severity: normal Tags: patch User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-logind Hi, when systemd-logind is active it will by default react to power events and execute the actions configured in /etc/systemd/logind.conf. A

Bug#727558: Upgrading gdm3 + gnome-shell from 3.4 to 3.8 is impossible

ll is not configured yet. > > dpkg: error processing gdm3 (--configure): > dependency problems - leaving unconfigured > Errors were encountered while processing: > gdm3 I've seen similar issues when testing dist-upgrades from wheezy to sid. The change in gdm3 (3.8.4-3) fixed

Bug#723936: [Pkg-systemd-maintainers] Bug#723936: Bug#723936: Bug#723936: systemd: fails to upgrade - same behavior

Am 27.10.2013 22:52, schrieb Michael Stapelberg: > I pushed this change: > http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=75051b6 Be careful with this check, this should be rather something like if [ -d /run/systemd/system/ ] && dpkg --compare-versions "$2" lt 204-1 ;

Bug#728151: libimobiledevice4: fails upgrade

Please just disable hal support and drop /usr/share/hal/fdi/information/20thirdparty/31-apple-mobile-device.fdi hal is completely broken nowadays and it doesn't make sense pretending this file is useful. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed

Bug#734398: Update Suggests for obsolete transitional package hpijs

Package: ghostscript Version: 9.05~dfsg-8+b1 Severity: normal The hpijs package has been superseded by printer-driver-hpijs and is now a transitional package which simply depends on printer-driver-hpijs. The ghostscript package should be updated accordingly and suggest printer-driver-hpijs instea

Bug#734398: Acknowledgement (Update Suggests for obsolete transitional package hpijs)

Looks like the "hpijs" transitional package has been removed in unstable/testing and only exists in wheezy. [1] http://packages.debian.org/search?keywords=hpijs -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Descrip

Bug#734514: Suggests no longer existing libicu48

Package: libqtcore4 Version: 4:4.8.5+git192-g085f851+dfsg-2 Severity: important libicu had a transition [1] and the libicu48 library package no longer exists. It seems to be superseded by libicu52 Please update the Suggests accordingly. Since this is a Suggests, I assume libqtcore dlopen's the l

Bug#734514: Acknowledgement (Suggests no longer existing libicu48)

Seems QtCore is already doing the right thing and loading libicu52 from what I can see from a strace: open("/usr/lib/x86_64-linux-gnu/libicui18n.so.52", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib/x86_64-linux-gnu/libicuuc.so.52", O_RDONLY|O_CLOEXEC) = 3 open("/usr/lib/x86_64-linux-gnu/libicudata.so.52

Bug#734548: unable to start bluetooth service during boot

reassign 734548 bluetooth forcemerge 729808 734548 affects 729808 + systemd thanks Am 08.01.2014 04:34, schrieb Pirate Praveen: > package: systemd > version: 204-5 > severity: important > > bluetooth service fails to start during boot. Manually starting it after > boot is working. Attaching journ

Bug#734779: [Pkg-utopia-maintainers] Bug#734779: applet dropdown does not show VPN connected when it is

reassign 734779 gnome-shell thanks Am 09.01.2014 20:03, schrieb Brent S. Elmer Ph.D.: > Here is a screen shot showing what I mean. that screenshot shows gnome-shell, so re-assigning. Please provide the version of gnome-shell you are using. -- Why is it that all of the instruments seeking intelli

Bug#734548: unable to start bluetooth service during boot

Am 09.01.2014 20:56, schrieb Pirate Praveen: > On Wednesday 08 January 2014 03:55 PM, Michael Biebl wrote: >> reassign 734548 bluetooth >> forcemerge 729808 734548 >> affects 729808 + systemd >> thanks >> >> Am 08.01.2014 04:34, schrieb Pirate Praveen:

Bug#734548: [Pkg-systemd-maintainers] Bug#734548: unable to start bluetooth service during boot

Am 08.01.2014 04:34, schrieb Pirate Praveen: > package: systemd > version: 204-5 > severity: important > > bluetooth service fails to start during boot. Manually starting it after > boot is working. Attaching journalctl -xb output. > > bluetooth service is turned on, > > $ sudo chkconfig --list

Bug#734548: [Pkg-systemd-maintainers] Bug#734548: unable to start bluetooth service during boot

Am 10.01.2014 20:09, schrieb Michael Biebl: > Am 08.01.2014 04:34, schrieb Pirate Praveen: >> package: systemd >> version: 204-5 >> severity: important >> >> bluetooth service fails to start during boot. Manually starting it after >> boot is w

Bug#730829: systemd fails to activate logical volumes after a power failure

Am 22.12.2013 02:27, schrieb Michael Biebl: > Am 29.11.2013 23:08, schrieb Praveen A: >> package: systemd >> version: 204-5 >> severity: critical >> >> Even when a simple fsck is enough to fix the issue. Currently it drops >> you into a shell where you have

Bug#735002: /usr/lib/sysctl.d/50-default.conf: Disables SysRq key

Am 11.01.2014 19:34, schrieb Bob Proulx: > Package: systemd > Version: 204-6 > Severity: normal > File: /usr/lib/sysctl.d/50-default.conf > > The /usr/lib/sysctl.d/50-default.conf disables the functionality of > the SysRq key. Please restore the default Debian kernel setting of > this value which

Bug#734951: [Pkg-systemd-maintainers] Bug#734951: Bug#734951: systemd: somehow starts LSB stuff in the wrong order

Am 11.01.2014 20:25, schrieb Christoph Anton Mitterer: > > btw: journalctl(1) seems to be out of date... at least -x is missing > there... Are you really running the unstable version then? This is from the journalctl man page: -x, --catalog Augment log lines with explanation te

Bug#735023: please relax Dependency on gdm3

Am 11.01.2014 23:55, schrieb Robert Millan: > Package: gnome-shell > Version: 3.8.4-5 > Tags: patch > > Hi, > > This package Depends on gdm3, I assume because it interacts with it in > intimate ways (switch user button?). > > However, it seems that even if gdm3 might be a better choice for GNOME

Bug#734460: [Pkg-utopia-maintainers] Bug#734460: network-manager: Issues related to systemd when upgrading from << 0.9.8.8-2

Am 07.01.2014 13:12, schrieb Laurent Bigonville: > Package: network-manager > Version: 0.9.8.8-2 > Severity: serious > > Hi, > > I'm opening this bug so this is not getting lost. > > When upgrading from the previous versions the following events might > occurs when the user is running systemd: >

Bug#734548: [Pkg-systemd-maintainers] Bug#734548: unable to start bluetooth service during boot

Am 11.01.2014 05:32, schrieb Pirate Praveen: > On Saturday 11 January 2014 12:49 AM, Michael Biebl wrote: >> Am 10.01.2014 20:09, schrieb Michael Biebl: >>> Am 08.01.2014 04:34, schrieb Pirate Praveen: >>>> package: systemd >>>> version: 204-5 >>&g

Bug#734460: [Pkg-utopia-maintainers] Bug#734460: Bug#734460: network-manager: Issues related to systemd when upgrading from << 0.9.8.8-2

Am 12.01.2014 13:11, schrieb Laurent Bigonville: > Le Sun, 12 Jan 2014 02:18:32 +0100, > Michael Biebl a écrit : > >> Am 07.01.2014 13:12, schrieb Laurent Bigonville: >>> Package: network-manager >>> Version: 0.9.8.8-2 >>> Severity: serious >>>

Bug#734460: [Pkg-utopia-maintainers] Bug#734460: Bug#734460: network-manager: Issues related to systemd when upgrading from << 0.9.8.8-2

Am 12.01.2014 13:53, schrieb Michael Biebl: > This somehow smells like the same bug as [1] or at least related, i.e. > systemd getting confused when we mess around with the symlinks. > (In case of rsyslog we basically go the other direction: the symlinks > are no longer sh

Bug#733122: fatal error: Typelib file for namespace 'GnomeBluetoothApplet' (any version) not found

Am 29.12.2013 02:21, schrieb Robert Millan: > tags 733122 patch > thanks > > Here's a patch. > > On Thu, Dec 26, 2013 at 12:32:22AM +0100, Robert Millan wrote: >> Package: gnome-shell-common >> Version: 3.8.4-5 >> Severity: grave >> >> gnome-shell aborts on GNU/kFreeBSD because of Linux-specific

Bug#733122: fatal error: Typelib file for namespace 'GnomeBluetoothApplet' (any version) not found

Am 12.01.2014 17:47, schrieb Michael Biebl: > In summary, the patch is not quite ready yet imho. Hm, looking more closely, instead of moving the files around, it might be better to use a try {} catch {} statement like we do for NM. Robert, can you try the following patch: --- a/js/ui/panel

Bug#735183: FTBFS on all architectures: test-suite failures

Source: libthai Version: 0.1.20-2 Severity: serious libthai FTBFS on all architectures. See https://buildd.debian.org/status/package.php?p=libthai -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (

Bug#735275: [Pkg-systemd-maintainers] Bug#735275: libudev1: Keep libudev.so.0 as a link to libudev.so.1

Am 14.01.2014 14:03, schrieb Michael Biebl: > Am 14.01.2014 11:44, schrieb Martin Pitt: >> Simon Pepping [2014-01-14 11:33 +0100]: >>> A number of applications depend on libudev.so.0, e.g. Google Chrome. >>> These applications solve the problem by creating a link libu

Bug#717613: systemd-udevd failes to execute /lib/udev/socket:@/org/freedesktop/hal/udev_event

Am 15.01.2014 21:33, schrieb Ilario Gelmetti: > Package: hal > Version: 0.5.14-8 > Followup-For: Bug #717613 > > Dear Maintainer, > happens also to me, on Debian Testing amd64. No need to confirm. This is a known issue and won't be fixed. Uninstall hal, it's no longer needed, obsolete and dead.

Bug#735583: systemd - Always succesful cryptdisks-early.service and cryptdisks.service

Hi Bastian, Am 16.01.2014 17:38, schrieb Bastian Blank: > systemd ships it's own cryptdisks-early.service and cryptdisks.service. > They do nothing and always succeed. This breaks lvm2, as it expects > this services to do something useful. .. > This services does not fit in the cryptsetup.targe

Bug#735750: /usr/bin/hal-disable-polling: hal-disable-polling: buffer overflow detected

Am 17.01.2014 12:40, schrieb Krisztian Korcz: > Package: hal > Version: 0.5.14-8 > Severity: normal > File: /usr/bin/hal-disable-polling Please uninstall hal. It's dead any won't see any further updates/fixes. -- Why is it that all of the instruments seeking intelligent life in the universe a

Bug#728823: Fails to start: Running without the SUID sandbox!

Package: chromium Version: 30.0.1599.101-2 Severity: grave File: /usr/bin/chromium After the latest upgrade, trying to start chromium results in $ chromium [19832:19832:1105/225629:FATAL:browser_main_loop.cc(160)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/Linu

Bug#728823: Acknowledgement (Fails to start: Running without the SUID sandbox!)

Not sure if it is related: http://anonscm.debian.org/gitweb/?p=pkg-chromium/pkg-chromium.git;a=commitdiff;h=be3c5943dd7f25a4bdc8b825475f270dad8519c9 +chromium: setuid-binary usr/lib/chromium/chrome-sandbox 4755 root/root There is no such file on my system. Something is definitely broken. -- Why

Bug#715060: piuparts errors: unowned files left after de-installation

Am 07.11.2013 08:23, schrieb Michael Stapelberg: >> In addition to this dh_systemd/ish manage stuff in /etc/systemd, >> creating missing directories if neccessary - which is wrong imho since >> these directories are also owned by other packages. So the management of >> these directories should be

Bug#729134: [Pkg-systemd-maintainers] Bug#729134: libpam-systemd wreaks havoc

Am 11.11.2013 23:31, schrieb Michael Stapelberg: > Hi Julien, > > Julien Puydt writes: >> I was having issues with my computer lately: >> - I wasn't able to mount USB keys anymore in thunar ; >> - I wasn't able to shutdown/restart/hibernate anymore in xfce ; >> - even when logged out, lightdm did

Bug#729134: [Pkg-systemd-maintainers] Bug#729134: libpam-systemd wreaks havoc

Am 12.11.2013 00:06, schrieb Yves-Alexis Perez: > On Mon, 2013-11-11 at 23:54 +0100, Michael Biebl wrote: >> The XFCE/lightdm maintainers need to decide if they want to use >> systemd-logind or stick with the obsolete CK. >> If the former, they'll need to do the switch

Bug#729252: udev: firmware can not be loaded because filesystem not yt mounted

Am 10.11.2013 20:31, schrieb Sebastian Niehaus: > Package: udev > Version: 175-7.2 > Severity: normal > > Dear Maintainer, > > > > for my DVB-S device i had to download some firmware. According to > https://wiki.debian.org/Firmware > I put it to /usr/local/lib/firmware > > However, since /usr

Bug#729347: typo in debian/control: s/Uploader/Uploaders/

Source: obnam Version: 1.5-1 Severity: minor Tags: patch debian/control has a typo. The field listing the uploaders is called 'Uploaders:' , not 'Uploader:' Assuming Gaudenz is still meant to be listed as Uploader you'll find a trivial patch attached. Regards, Michael -- System Information: De

Bug#729808: systemd-sysv: breaks bluetooth

reassign 729808 bluetooth severity 729808 important retitle 729808 bluetooth.service needs to be enabled user pkg-systemd-maintain...@lists.alioth.debian.org usertags systemd-units thanks Am 17.11.2013 18:12, schrieb Andreas Cadhalpun: > It seems that systemd does not start bluetoothd. Please fix

Bug#729805: systemd: fails to show startup messages with systemd.show_status=1

Please paste the complete kernel command line: cat /proc/cmdline -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature

Bug#729983: Allow to attach comments to backups / generations

Package: obnam Version: 1.5-1 Severity: wishlist It would be handy if one could add comments / descriptions when creating a new backup generation, say like obnam backup --description="This backup was triggered via cron" Or make it possible to attach comments via a separate command afterwards, lik

Bug#729566: [Pkg-systemd-maintainers] Bug#729566: Bug#729566: systemd: new upstream release 208

Am 27.11.2013 23:10, schrieb Michael Stapelberg: > Also, here is one more bug which I am neglecting currently due to lack > of time: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729134 > There is a related upstream discussion here: > http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/

Bug#717386: pending

Am 28.11.2013 02:12, schrieb Michael Biebl: > Am 27.11.2013 21:32, schrieb Michael Stapelberg: >> control: tags 717386 + pending >> control: tags 724668 + pending >> >> Hi, >> >> I pushed two commits to the systemd repository to address these two bugs: >

Bug#717386: pending

Am 27.11.2013 21:32, schrieb Michael Stapelberg: > control: tags 717386 + pending > control: tags 724668 + pending > > Hi, > > I pushed two commits to the systemd repository to address these two bugs: > http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=c4c50e0 > http://an

Bug#729676: systemd: service command has wrong exit code for unknown service

Hi Stephen, Am 20.11.2013 08:41, schrieb Stephen Gran: > This one time, at band camp, Michael Biebl said: >> Am 15.11.2013 17:18, schrieb Stephen Gran: >>> Package: systemd >>> Version: 44-11 >>> Severity: normal >>> >>> Hi, >>> >

Bug#717386: Bug#724668: Bug#717386: pending

Am 28.11.2013 02:12, schrieb Michael Biebl: > - /var/log/journal is not removed on purge, so purging the > systemd-journal group in postinst/purge can lead to breakage should you > later re-install the package. > Either remove all files related to a that group before removing the >

Bug#717386: pending

Am 28.11.2013 02:13, schrieb Michael Biebl: > Am 28.11.2013 02:12, schrieb Michael Biebl: >> Am 27.11.2013 21:32, schrieb Michael Stapelberg: >>> control: tags 717386 + pending >>> control: tags 724668 + pending >>> >>> Hi, >>> >>>

Bug#729566: [Pkg-systemd-maintainers] Bug#729566: Bug#729566: systemd: new upstream release 208

Am 28.11.2013 13:53, schrieb Alessandro Ghedini: > On mer, nov 27, 2013 at 11:10:07 +0100, Michael Stapelberg wrote: >> Also, here is one more bug which I am neglecting currently due to lack >> of time: >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729134 >> There is a related upstream discus

Bug#717386: pending

Am 28.11.2013 22:22, schrieb Michael Stapelberg: > Hi Michael, > > thanks for all your comments. > > Michael Biebl writes: >> You should probably run setfacl with -R, so the ACLs are set >> recursively, which might be necessary if files already exist. > Good poi

Bug#718190: [Pkg-systemd-maintainers] Bug#718190: systemd don't activate non-essential lvm over luks volumes

Am 01.12.2013 16:37, schrieb Franz Schrober: > Thanks a lot for your lvm2 builds and bug report. It reduced the time to fix > the problem here to an hour instead of hours/days. > > I am really shocked about the uncooperative way of handling the problem by the > lvm2 maintainers. Yeah, this is ver

Bug#751594: [Pkg-utopia-maintainers] Bug#751594: Bug#751594: network-manager: dnsmasq incompatible with network manager and systemd

Am 16.06.2014 17:29, schrieb Mathieu Trudel-Lapierre: > On Sat, Jun 14, 2014 at 4:30 PM, Vincent Bernat wrote: > [...] >> So, NetworkManager checks if somebody is listening to the right DBus >> address. With Debian and systemd, since dnsmasq is DBus enabled, it will >> be started at this point. Ot

Bug#751624: [systemd]: emergency shell takes several minutes to start

Am 15.06.2014 00:50, schrieb Michael Gold: > On Sat, Jun 14, 2014 at 23:44:42 +0200, Michael Biebl wrote: >> Am 14.06.2014 22:41, schrieb Michael Gold: >>> * after printing "Welcome to emergency mode!", it took a minute or two >>>before a password prom

Bug#751878: FTBFS from source on i386 but successfully built in the past

Source: sqlite3 Version: 3.8.5-1 Severity: serious The current version of sqlite3 FTBFS on i386. See https://buildd.debian.org/status/package.php?p=sqlite3&suite=sid -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') A

Bug#751892: udev: external media belong to disk group

Am 17.06.2014 17:04, schrieb Yann Amar: > Package: udev > Version: 204-10 > Severity: normal > > Dear Maintainer, > > since some Debian specific rules (91-permissions.rules?) have been dropped > from > udev, external media (USB, firewire, SD-card) belong to disk group: > > user@debian:~$ ls -l

Bug#731851: modemmanager: Please update to latest 1.2 release candidate

Am 18.06.2014 00:41, schrieb Vincent Bernat: I suppose libqmi needs to > be updated first? Correct -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature

<    2   3   4   5   6   7   8   9   10   11   >