[Bug 1207206] Re: rtkit-daemon warning policykit call failed did not receive a reply
If I try a fresh installed Ubuntu 13.04 it works perfectly users can login in without problem and disconect too. But if I do updates (without updating kernel) after reboot users can't login without waiting lot of minutes... I will try to check the bad update... ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207206 Title: rtkit-daemon warning policykit call failed did not receive a reply To manage notifications about this bug go to: https://bugs.launchpad.net/policykit/+bug/1207206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1207206] Re: rtkit-daemon warning policykit call failed did not receive a reply
After searching, I found that dbus was the problem. These 3 packages are upgraded after installation : dbus,dbus-x11,libdbus-1-3 from 1.6.8-1ubuntu6 to 1.6.8-1ubuntu6.1. I've pinned these three packages to their original version and do the upgrade... And It works, users can connect, so the problem comes form dbus ! (I'll change affects consequently). ** No longer affects: ubuntu ** Project changed: policykit = dbus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207206 Title: rtkit-daemon warning policykit call failed did not receive a reply To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1207206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205075] Re: mountall doesn't treat glusterfs correctly
I disagree this duplicate (I remove them) 'cause this problem is pretty different than bug #1103047. In my bug I've found that mountall generate bad mount commandline for glusterfs (see the Usage in mountall --verbose). This bug is a CRITICAL bug 'cause my servers doesn't start anymore ** This bug is no longer a duplicate of bug 1103047 mountall causes automatic mounting of gluster shares to fail -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205075 Title: mountall doesn't treat glusterfs correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1205075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103047] Re: mountall causes automatic mounting of gluster shares to fail
I create a bug (#1205075) about mountall that doesn't generate good mount commande line for glusterfs. My Bug was marked duplicate of this one. The final problem was the same, but the clues I found are pretty different. More, this bug has importance=low but for me it would be CRITICAL 'cause my server doesn't start anymore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103047 Title: mountall causes automatic mounting of gluster shares to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1103047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205075] [NEW] mountall doesn't treat glusterfs correctly
Public bug reported: I've two servers replicating data by Gluster every servers are clients too. The problem is that the glusterfs was never mounted at boot 'cause mountall doesn't call correct mount command and doesn't treat gluster filesystem as remote filesystem. Some informations : # lsb_realease -rd Description:Ubuntu 13.04 Release:13.04 # apt-cache policy mountall mountall: Installed : 2.48build1 Candidate : 2.48build1 Table de version : *** 2.48build1 0 500 http://fr.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status # mountall --version mountall 2.44 Entry in the fstab : 192.162.0.1:test-vol /srv/conf glusterfs defaults,_netdev 0 0 After boot, this entry wasn't mounted. But if I try : # mount -t glusterfs 192.162.0.1:test-vol /srv/test-vol It works perfectly I put a '--verbose' into /etc/init/mountall.conf file to see what happened. I obtain this : / est local /proc est virtual /sys est virtual /sys/fs/cgroup est virtual /sys/fs/fuse/connections est virtual /sys/kernel/debug est virtual /sys/kernel/security est virtual /dev est virtual /dev/pts est virtual /tmp est local /run est virtual /run/lock est virtual /run/shm est virtual /run/user est virtual /srv est local /var est local UUID=ac001a41-9a55-49d6-86c8-1e9e8df41054 est swap /mnt/shared-conf est local /srv/conf est nowait == Why not remote ? mounting event sent for /sys/fs/cgroup mounting event sent for /sys/fs/fuse/connections mounting event sent for /sys/kernel/debug mounting event sent for /sys/kernel/security mounting event sent for /run/lock mounting event sent for /run/shm mounting event sent for /run/user ... mounting event handled for /srv/conf montage de /srv/conf mounted event handled for /srv/conf local 5/5 remote 0/0 virtual 12/12 swap 1/1 ^ And no /srv/conf mounted... With this command I've found more information : # mountall --verbose ... Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT] or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT] Try `glusterfs --help' or `glusterfs --usage' for more information. mount /srv/conf [11156] s'est terminé normalement ... We can see that the call of mount was not correct (see Usage). If I go deeper : # mountall --verbose --debug ... run_mount: mtab /srv/conf spawn: mount -f -t fuse.glusterfs -o defaults,_netdev 10.130.163.253:volume-conf /srv/conf spawn: mount /srv/conf [11339] Usage: glusterfs [OPTION...] --volfile-server=SERVER [MOUNT-POINT] or: glusterfs [OPTION...] --volfile=VOLFILE [MOUNT-POINT] Try `glusterfs --help' or `glusterfs --usage' for more information. mount /srv/conf [11339] s'est terminé normalement ... When I try the mount mentioned above I've got the same behaviour (send Usage) 'cause fuse.glusterfs wasn't recognized. If I put glusterfs instead the mount works as expected. More, since mountall doesn't treat glusterfs as remote filesystem, it try to mount it even if local filsystems aren't mounted yet. For example, if /var wasn't cleanly unmounted, it will be checked at boot and mountall try to mount glusterfs during check. This cause some troubles because glusterfsd need acces to /var/log which is not mounted yet... ** Affects: mountall (Ubuntu) Importance: Undecided Status: New ** Tags: glusterfs mountall remote ** Description changed: I've two servers replicating data by Gluster every servers are clients too. The problem is that the glusterfs was never mounted at boot 'cause mountall doesn't call correct mount command and doesn't treat gluster filesystem as remote filesystem. Some informations : # lsb_realease -rd Description:Ubuntu 13.04 Release:13.04 # apt-cache policy mountall mountall: - Installed : 2.48build1 - Candidate : 2.48build1 - Table de version : - *** 2.48build1 0 - 500 http://fr.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages - 100 /var/lib/dpkg/status + Installed : 2.48build1 + Candidate : 2.48build1 + Table de version : + *** 2.48build1 0 + 500 http://fr.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages + 100 /var/lib/dpkg/status # mountall --version mountall 2.44 Entry in the fstab : 192.162.0.1:test-vol /srv/conf glusterfs defaults,_netdev 0 0 After boot, this entry wasn't mounted. But if I try : # mount -t glusterfs 192.162.0.1:test-vol /srv/test-vol It works perfectly I put a '--verbose' into /etc/init/mountall.conf file to see what happend. I obtain this : / est local /proc est virtual /sys est virtual /sys/fs/cgroup est virtual /sys/fs/fuse/connections est virtual /sys/kernel/debug est virtual /sys/kernel/security est virtual /dev est virtual /dev/pts est virtual /tmp est local /run est virtual /run/lock est virtual /run/shm est virtual /run/user est virtual /srv est local /var est local
Re: [Bug 995715] Re: X defaulting keyboard locale to US at login after upgrading distribution if a Logitech Unifying Receiver is plugged in
Probably but I'm not sure 'caus without xorg.conf keyboard map is wrong too. Currently I workarounded it with a 'display-setup-script=setxkbmap fr' in the lightdm.conf file. Regards Bruno. Le 26/01/2013 13:01, Stephan Diestelhorst a écrit : Is the underlzing issue, namely relying on HAL the same as #995380? -- Bruno MACADRE --- Ingénieur Systèmes et Réseau | Systems and Network Engineer Département Informatique | Department of computer science Responsable Réseau et Téléphonie | Telecom and Network Manager Université de Rouen | University of Rouen --- Coordonnées / Contact : Université de Rouen Faculté des Sciences et Techniques - Madrillet Avenue de l'Université - BP12 76801 St Etienne du Rouvray CEDEX FRANCE Tél : +33 (0)2-32-95-51-86 Fax : +33 (0)2-32-95-51-87 --- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995715 Title: X defaulting keyboard locale to US at login after upgrading distribution if a Logitech Unifying Receiver is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/995715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993827] Re: Logitech Wireless keyboard has bad layout on login screen
Nothing new... To believe that everyone who cares It is probably not important to have an AZERTY keyboard for developers as they are all QWERTY ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993827 Title: Logitech Wireless keyboard has bad layout on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/993827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993827] [NEW] Logitech Wireless keyboard has bad layout on login screen
Public bug reported: I've got a DELL E6410 laptop on a dock station with 2 screens plugged on it. I use a Logitech MX720 AZERTY keyboard and a Logitech M705 mouse (both wireless with the Logitech Unifying Receiver). I've just installed Ubuntu 12.04 (fresh install) and my problem is that my Wireless keyboard is always in QWERTY on the login screen (I've tried lightmd and gdm... same behaviour), my laptop keyboard is in AZERTY (like the wireless will must be). In the Xorg.0.log my keyboards are seen in layout 'fr' and variant 'oss' both... If I type my password with my laptop keyboard I'm logged in AZERTY but if I type my password on my wireless keyboard, I'm logged in QWERTY... ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 [modified: usr/share/X11/xorg.conf.d/11-evdev-quirks.conf] ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Thu May 3 10:46:26 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: Dell Inc. Latitude E6410 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=e1e4f61c-aba1-4811-8382-140c680f9eab ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UdevDb: Error: [Errno 2] Aucun fichier ou dossier de ce type UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0K42JR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd03/05/2010:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: xserver-xorg-input-evdev (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 evdev keyboard precise ubuntu wireless -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993827 Title: Logitech Wireless keyboard has bad layout on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/993827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993827] Re: Logitech Wireless keyboard has bad layout on login screen
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993827 Title: Logitech Wireless keyboard has bad layout on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/993827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963857] Re: lightdm sometimes fails to register wireless keyboard input
I think I have a similar problem. I have a Logitech MX720 keyboard (with Logitech Unifying Receiver) connected to a laptop (on a dock). When I try to enter my password in QWERTY lightdm I'm on the MX720 and AZERTY on the laptop. As soon as I connected no problem the two keyboards are AZERTY. This is a very restrictive problem since I have to keep the laptop open to input my password. I've just upgraded to Ubuntu 12.04 and this bug did not exist in 11.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963857 Title: lightdm sometimes fails to register wireless keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/963857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963857] Re: lightdm sometimes fails to register wireless keyboard input
Oups you must read When I try ton enter my password on lightdm my mx720 was QWERTY and my laptop keybord was AZERTY (the previous sentence means nothing at all). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963857 Title: lightdm sometimes fails to register wireless keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/963857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 295536] Re: cups-pdf fails bad status reported and no pdf created
Hi ! Like Eric says, it's a problem in the AppArmor configuration. His workaround works well but it remove the protection over cups-pdf. Like we see in the dmesg posted by marcobra it looks like a capabilities problem for /usr/lib/cups/backend/cups-pdf : --- [89144.961555] type=1503 audit(1226146931.033:19): operation=capable name=dac_read_search pid=13513 profile=/usr/lib/cups/backend/cups-pdf [89168.118889] type=1503 audit(1226146954.189:20): operation=capable name=dac_override pid=13725 profile=/usr/lib/cups/backend/cups-pdf --- If you don't want disable protection of cups-pdf in AppArmor, don't use the flags=(complain). Go to the /etc/apparmor.d/usr.sbin.cupsd and in the /usr/lib/cups/backend/cups-pdf section search for this lines : capability chown, capability fowner, capability fsetid, capability setgid, capability setuid, after this lines you just need to add this two new lines : capability dac_override, capability dac_read_search, It would be suficient. You juste need a /etc/init.d/apparmor reload and cups-pdf would works well !! Hope this helps, Bruno PS : Sorry for my english ;-) -- cups-pdf fails bad status reported and no pdf created https://bugs.launchpad.net/bugs/295536 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
