[no subject]
Good Day, I am Mr. Alfred Cheuk Yu Chow, the Director for Credit & Marketing Chong Hing Bank, Hong Kong, Chong Hing Bank Center, 24 Des Voeux Road Central, Hong Kong. I have a business proposal of $ 38,980,369.00. All confirmable documents to back up the claims will be made available to you prior to your acceptance and as soon as I receive your return mail. Best Regards, Alfred Chow. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
[no subject]
I am Mr.Sheng Li Hung I have a very profitable business proposition for you___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#885318: (no subject)
Subject: Re: systemd kills X or freezes it when logging out from last opened tty Followup-For: Bug #885318 Package: systemd Version: 236-1 The Xorg.0.log.old (of my debian Sid vm) I joined is a fresh one; logged just after X "crash". ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#882027: (no subject)
Am 19.11.2017 um 16:11 schrieb Torsten Boese: > Hi Michael, > > thanks for the quick response. My goal is not to use a specific daemon, my > goal is to have a working suspend mode - if it's pam or systemd or whatever > is not important for me. But in my opinion it's useful to use the system > standards. I have not changed any settings regarding suspend or power > management, I'm just using the xfce buttons. So perhaps other have similar > issues. > > What can I do to get it working? No idea. But I fail to see why this bug was filed against systemd in the first place? Apparently your Xserver is *not* using systemd-logind. Why do you think it is systemd causing your resume failures? -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#882027: (no subject)
Hi Michael, thanks for the quick response. My goal is not to use a specific daemon, my goal is to have a working suspend mode - if it's pam or systemd or whatever is not important for me. But in my opinion it's useful to use the system standards. I have not changed any settings regarding suspend or power management, I'm just using the xfce buttons. So perhaps other have similar issues. What can I do to get it working? Regards Torsten ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
[no subject]
Je suis ABOUD Guy Salim, le vérificateur en chef des opérations financières de GLOBAL SECURITY FUND-BENIN ( Une Compagnie de Gardiennage des Fonds). J'ai besoin de votre consentement. Une somme flottante de 1.250.000€ appartenant à un client décédé dont le nom n'a pas été identifié et noté dans nos archives non réclamés et des fichiers dans notre base de données. Comme l'un des principaux dirigeants de la compagnie, je suis obligé de vous informer que je suis à la recherche de quelqu'un avec qui nous pouvons remettre ce fonds. Je vous demande d'accepter d'être le plus proche parent et revendiquer les ressources (1.250.000€ ). Je souhaite que ces fonds soient transférés à votre compte en banque en tant que proche parent du défunt. J'ai besoin de votre aide. Pour être honnête, je vous promets que vous ne courrez aucun risque parce que ma position au sein de cette compagnie me permet de couvrir tous les risques et en plus; je suis la seule personne qui puisse superviser l'opération. J'ai fait toutes les vérifications sur cet accord pour que son application soit propre et se fasse rapidement, il n'y a donc aucun risque. Je vous demande de considérer cette lettre avec assez de sérieux et discrétion possible. Si éventuellement, vous êtes d'accord avec ma proposition veuillez me confirmer votre coordonnée complète à savoir: Nom:.. Prénoms:. Pays:.. Ville:... Adresse complète:. N°Téléphone:... Profession:. Cordialement, ABOUD Guy Salim ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#858211: (no subject)
Just to confirm, things seem OK with the following in system.conf: DefaultTimeoutStartSec=3s DefaultTimeoutStopSec=15s Everything including graphical desktop login comes up and down with no issues. I think it'd be slightly better to keep the longer timeout, but allow the console operator to interrupt it. Hopefully, I got the Control headers right to make this a wishlist. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#847448: (no subject)
Am 08.12.2016 um 12:46 schrieb Dennis Schridde: > bug #771980 is probably also related. I don't think so. This bug report was about the adm ACL. -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#847448: (no subject)
bug #771980 is probably also related. signature.asc Description: This is a digitally signed message part. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
[no subject]
hello ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
[no subject]
MY BELOVED ONE, PLEASE I NEED YOU TO HELP ME. I WILL GIVE YOU DETAILS WHEN I GET RESPONSE FROM YOU. SINCERELY, LAGOLI WARLORD. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
[no subject]
___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#824898: (no subject)
reopen 824898 reopen 824947 thanks # Sorry, closed by mistake. Reopening. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#809903: (no subject)
Control: tags -1 + moreinfo Hello Ian, your bug report doesn't contain anything. Can you please elaborate what your problem is. Thanks, Michael -- 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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#809903: (no subject)
Processing control commands: > tags -1 + moreinfo Bug #809903 [systemd] (no subject) Added tag(s) moreinfo. -- 809903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
[no subject]
___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#802897: (no subject)
Seems strange, because if I enter wrong passphrase, I am prompted for it once more without any problems. -- Yours sincerely, Jayson Willson ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#801563: (no subject)
Yes, I confirm. With timeout=1min everything goes fine, but with timeout=2min the situation I have described in the beginning happens again. I've heard about 1.30min systemd timeout for all units. Could it be because of this timeout? -- Yours sincerely, Jayson Willson ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#761909: (no subject)
Benedict Broy [2014-11-23 23:45 +0100]: > Hi, I have exactly the same problem. In my case, network-manager is > responsible for shutting down the network connection. Please let's keep this bug about interfaces configured with ifupdown. NM is an entirely different mechanism, and unlike ifupdown systemd isn't directly involved in that. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#788050: (no subject)
Dear maintainer, Konsole output axel@kruemel:~$ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.1.0-2-amd64 root=/dev/mapper/OS_1-root ro axel@kruemel:~$ Therefore I think, that I am not using the splash option. Plymouth is not installed. Maybe the fstab is helpful: Konsole output axel@kruemel:~$ cat /etc/fstab # /etc/fstab: static file system information. # # proc /proc proc defaults 0 0 /dev/mapper/OS_1-root/ ext3errors=remount-ro 0 1 /dev/md0 /boot ext3defaults 0 2 /dev/mapper/data_1-home /files1 ext3defaults 0 2 /dev/mapper/data_2-files /files2 ext3defaults 0 2 /dev/mapper/data_1-files /home ext3defaults 0 2 /dev/mapper/OS_1-opt /optext3defaults 0 2 /dev/mapper/OS_1-tmp /tmpext3defaults 0 2 /dev/mapper/OS_1-usr /usrext3defaults 0 2 /dev/mapper/OS_1-var /varext3defaults 0 2 /dev/mapper/data_1-swap noneswapsw 0 0 /dev/scd0/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0 /media/floppy0 autorw,user,noauto 0 0 ## usbfs is the USBUSERS group in fstab file: # none /proc/bus/usb usbfs devgid=126,devmode=664 0 0 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#788303: (no subject)
I'm also having this problem. I have this problem in jessie VM running on jessie host (KVM). Somehow, swap filesystem cannot be unmounted and there is no timeout. BR, -Risto Subject: Re: systemd: Hangs indefinitely on 90% of reboot attempts Followup-For: Bug #788303 Package: systemd Version: 215-17+deb8u1 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-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 Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-6 ii libc6 2.19-18 ii libcap2 1:2.24-8 ii libcap2-bin 1:2.24-8 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-17+deb8u1 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev215-17+deb8u1 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus1.8.18-0+deb8u1 ii libpam-systemd 215-17+deb8u1 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/logind.conf changed: [Login] HandleSuspendKey=ignore HandleHibernateKey=ignore HandleLidSwitch=ignore -- no debconf information ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#765577: (no subject)
Control: tag -1 pending
Hey Faidon,
Faidon Liambotis [2015-04-22 15:25 +0300]:
-new_rule_pattern=$(echo ^SUBSYSTEM==\net\, ACTION==\add\$match | sed
-re 's/([\?\*])/\\\1/g')
+new_rule_pattern=$(echo ^SUBSYSTEM==\net\, ACTION==\add\$match | sed
-re 's/([\?\*\{\}])/\\\1/g')
Thanks for spotting this! I tested this now with Marco's test script,
and it still works fine. Committed to master now:
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=3d02f64154
(to experimental too).
I have to say... constructing regexps in shell is tricky and the
whole escaping-with-sed logic feels like a hack. I think a literal
grep (i.e. -F) would be better here, especially since I don't see
the point of an exact match (even if the file was modified by the
sysadmin, the right thing would to not write a new rule anyway).
This is probably something to be considered post-jessie.
Yeah, the whole generator is a horrible thing.. For the future I
actually want to propose a bolder change:
https://lists.debian.org/debian-devel/2015/05/msg00170.html
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#765577: (no subject)
Processing control commands: tag -1 pending Bug #765577 [udev-udeb] netboot install writes duplicates to 70-persistent-net.rules Bug #777126 [udev-udeb] udev: duplicate eth? entries Added tag(s) pending. Added tag(s) pending. -- 765577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765577 777126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#786418: (no subject)
related lintian feature request... warn against usage of spaces, i.e. 'Type = notify' in systemd unit files http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786421 Cheers, Patrick ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#765577: (no subject)
reopen 765577 !
found 765577 215-14
thanks
On Mon, Mar 30, 2015 at 06:06:47AM +0200, Marco d'Itri wrote:
I see that we have independently devised the same fix, I am attaching
a test case and a more refined version of your patch.
I tried Jessie RC3 today and immediately found that the fix is,
unfortunately, buggy. Your patch constructs a regexp and takes care to
escape metacharacters ? and * with a sed but does not escape { and
} that are also metacharacters in the extended set of POSIX regexps.
These are always found in the string-to-be-matched here with
'ATTR{dev_id}==0x0' and 'ATTR{type}==1', so the if always fails.
This was likely not caught by your test case (and was harder to debug
and figure out!) because GNU grep's -E mode handles { as both a literal
and a metacharacter heuristically for historic reasons (consult grep's
manpage for that) but busybox grep does not:
$ echo 'foo{bar}' test
$ egrep 'foo{bar}' test
foo{bar}
$ busybox egrep 'foo{bar}' test
egrep: bad regex 'foo{bar}'
$ egrep 'fo{1,2}' test
foo{bar}
$ busybox egrep 'fo{1,2}' test
foo{bar}
Note that this is NOT a bug in busybox; foo{bar} is indeed an invalid
extended POSIX regexp and busybox is right to complain and error out.
The very minimal last-minute fix below did the trick for me but I have
to say... constructing regexps in shell is tricky and the whole
escaping-with-sed logic feels like a hack. I think a literal grep (i.e.
-F) would be better here, especially since I don't see the point of an
exact match (even if the file was modified by the sysadmin, the right
thing would to not write a new rule anyway). This is probably something
to be considered post-jessie.
Thanks,
Faidon
diff --git a/debian/extra/write_net_rules b/debian/extra/write_net_rules
index 38a3ca0..fedc0f1 100644
--- a/debian/extra/write_net_rules
+++ b/debian/extra/write_net_rules
@@ -118,7 +118,7 @@ basename=${INTERFACE%%[0-9]*}
match=$match, KERNEL==\$basename*\
# build a regular expression that matches the new rule that we want to write
-new_rule_pattern=$(echo ^SUBSYSTEM==\net\, ACTION==\add\$match | sed -re
's/([\?\*])/\\\1/g')
+new_rule_pattern=$(echo ^SUBSYSTEM==\net\, ACTION==\add\$match | sed -re
's/([\?\*\{\}])/\\\1/g')
# Double check if the new rule has already been written. This happens if
# multiple add events are generated before the script returns and udevd
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#765577: (no subject)
Processing commands for cont...@bugs.debian.org:
reopen 765577 !
Bug #765577 {Done: Martin Pitt mp...@debian.org} [udev-udeb] netboot install
writes duplicates to 70-persistent-net.rules
Bug #777126 {Done: Martin Pitt mp...@debian.org} [udev-udeb] udev: duplicate
eth? entries
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
Changed Bug submitter to 'Faidon Liambotis parav...@debian.org' from 'Petter
Reinholdtsen p...@hungry.com'
No longer marked as fixed in versions systemd/219-6 and systemd/215-14.
No longer marked as fixed in versions systemd/219-6 and systemd/215-14.
found 765577 215-14
Bug #765577 [udev-udeb] netboot install writes duplicates to
70-persistent-net.rules
Bug #777126 [udev-udeb] udev: duplicate eth? entries
Marked as found in versions systemd/215-14.
Marked as found in versions systemd/215-14.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
765577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765577
777126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#765577: (no subject)
On Mar 18, Faidon Liambotis parav...@debian.org wrote:
Well, the root cause IMO is that 75-persistent-net-generator.rules is
inherently susceptible to races. It's my understanding that it's valid
for events to be triggered multiple times -- there are multiple places
in d-i that udevadm trigger is called, including start-udev (as
shipped by udev-udeb) which would trigger another set of add events
beyond the original hotplug one.
I do not think that this is valid in the sense that the kernel could
generate multiple add events, but removing all misuses of udevadm
trigger requires some work and may not even be possible at this time.
I see that we have independently devised the same fix, I am attaching
a test case and a more refined version of your patch.
--
ciao,
Marco
#!/bin/sh -e
rm -f /etc/udev/rules.d/70-persistent-net.rules
rmmod e1000e || true
modprobe e1000e
sleep 1
rm -f /etc/udev/rules.d/70-persistent-net.rules
iteration=0
while : ; do
iteration=$((iteration + 1))
if ! echo add /sys/class/net/eth0/uevent; then
echo Failed at iteration $iteration!
exit
fi
# do not send too many events to udev because they will all be queued
# and eventually processed
if [ $iteration -eq 2500 ]; then
echo Aborting at iteration $iteration!
exit
fi
done
--- /lib/udev/write_net_rules.orig 2015-03-30 05:18:43.228147201 +0200
+++ /lib/udev/write_net_rules 2015-03-30 06:00:39.181085432 +0200
@@ -117,6 +117,18 @@
basename=${INTERFACE%%[0-9]*}
match=$match, KERNEL==\$basename*\
+# build a regular expression that matches the new rule that we want to write
+new_rule_pattern=$(echo ^SUBSYSTEM==\net\, ACTION==\add\$match | sed -re 's/([\?\*])/\\\1/g')
+
+# Double check if the new rule has already been written. This happens if
+# multiple add events are generated before the script returns and udevd
+# renames the interfaces. See #765577 for details.
+if egrep -q $new_rule_pattern \
+$RO_RULES_FILE $([ -e $RULES_FILE ] echo $RULES_FILE); then
+ unlock_rules_file
+ exit 0
+fi
+
if [ $INTERFACE_NAME ]; then
# external tools may request a custom name
COMMENT=$COMMENT (custom name provided by external tool)
pgp0CXb73md6m.pgp
Description: PGP signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#732209: (no subject)
Content-Type: multipart/mixed; boundary1764408977== MIME-Version: 1.0 From: Miklos Quartus in...@miklos.info To: Debian Bug Tracking System 732...@bugs.debian.org Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied Message-ID: 20141230213601.24606.52599.reportbug@localhost X-Mailer: reportbug 6.6.1 Date: Tue, 30 Dec 2014 22:36:01 +0100 This is a multi-part MIME message sent by reportbug. --===1764408977== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Package: libpam-systemd Version: 215-8 Followup-For: Bug #732209 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear GNOME Maintainer, Here's some progress on the bug I am still experiencing in Jessie. I found that this bug can only be reproduced in a GNOME session if the root terminal window is in focus. So to the steps to reproduce the bug - if you have not managed to so far - - slightly changes as below. 1. Get a root terminal window running and make sure it's in focus (in a GNOME session hit the Super key, type 'root ..' in the search bar and hit Enter to the run the app. 2. Run the 'Files' file manager app (not the PCManFM or other) or the 'dconf Editor' app (hit the Super key, type the app name) and once the window is active, do some one simple action (i.e. click on a menu item). 3. Close the application window. 4. Watch the file permission changes - /run/user/1000/dconf/user which effectively locks up your GNOME session. At the moment I don't have any patch or further information as to what might be the root cause leading up to this issue. I am using the latest up-to-date Jessie from official Debian repositories. It is also worth mentioning that I am using the GNOME minimalist installation, I have the 'core-only' as described on https://wiki.debian.org/Gnome . (i.e. I don't have the gnome-desktop-environment package installed, I have the extra stuff :-/). This way I am perfectly happy user of Debian and GNOME. gnome-session: 3.14.0-2 gnome-shell: 3.14.2-3 gnome-core: 1:3.14+3 gnome-desktop-environment: not installed gnome-desktop: not installed Inform me of any progress. Kind regards, - -- Miklos - -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam-systemd depends on: ii dbus 1.8.12-3 ii libc6 2.19-13 ii libcap21:2.24-6 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii multiarch-support 2.19-13 ii systemd215-8 ii systemd-sysv 215-8 libpam-systemd recommends no packages. libpam-systemd suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUoxqyAAoJECII8s4/zqDTrKIIALGo5P7P5xsgGweHcxBQr4Zu e6HOiR2Sc91xudDP+Tty/iXAciG01fRi1vrcc6rlAgTa44/+RC5UJTY5Ar8IL7xC G5w7ChYd+y9gWlMHzLAi/eiC37UFW5HQzp1bsvTWI8y9p5l/lWyP7/56eiKIzNEj +6kLK99EJ92qXscC45SFggiT8871d7y9wW52HbFZHoMzsJfPAel57fMDiupvxZut ndO8mSkUDCD8xn6fpks2Vu2PYhP7NO/w6ip2XYHz/axyj51Wz4y2lQnAFgAS6Twk ubzDQeH0ub6iu7ILkoDImuLlCRAYOR09H7ufCOWDhHDJcybpk3fs+qKxVMf6lyA= =4tzM -END PGP SIGNATURE- --===1764408977== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=gnome-shell-errormsg.txt Dec 30 22:13:12 localhost gnome-session[21484]: (gnome-settings-daemon:21555): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. --===1764408977==-- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
[no subject]
هل تحتاج إلى قرض للاستخدام الشخصي أو الأعمال؟ إذا كانت الإجابة بنعم، والبريد الإلكتروني لنا كمية ومدة، وذلك بفضل.___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
(no subject)
-- Somos Wells Fargo Finance Company, tenemos compañía en todo el mundo, como Estados Unidos, Reino Unido, Asia continente, Europa. Ofrecemos préstamo @ tasa de interés del 3% a partir de una serie de mínimo de 10.000,00 euros, dólares y libras a un máximo de 500,000,000.00euro, dólares y libras. ¿necesita un préstamo de Navidad urgentes amablemente aplicar ahora. Nombre completo: país: Cantidad necesaria: duración: número de teléfono móvil nos lleva días sólo 4working que le conceda este préstamo sin ninguna cuota ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#746279: (no subject)
Michael can you use adm group instead of systemd-journal? adm is traditionaly used to allow people to read logs. i've open an upstream bug regarding that. https://bugzilla.redhat.com/show_bug.cgi?id=1047729 -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#746279: Info received ((no subject))
On 06/19/2014 10:45 PM, Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian systemd Maintainers pkg-systemd-maintainers@lists.alioth.debian.org If you wish to submit further information on this problem, please send it to 746...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
