[Bug 1730410] Re: Window full-screen size when Firefox starts
This is indeed a mutter "feature". Use 'gsettings set org.gnome.mutter auto-maximize false' to turn it off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730410 Title: Window full-screen size when Firefox starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/1730410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771914] Re: release-upgrade-motd can't update message via apt proxy
This is still broken when you use something like apt-cacher-ng -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771914 Title: release-upgrade-motd can't update message via apt proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1771914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423672] Re: ext4 turned read-only during logrotate daily run
No, it isn't gone after all, it just happened again: Jun 13 15:20:37 oberon kernel: [117379.592167] EXT4-fs error (device dm-1): ext4_mb_generate_buddy:756: group 1, block bitmap and bg descriptor inconsistent: 19382 vs 19381 free clusters Jun 13 15:20:37 oberon kernel: [117379.592903] Aborting journal on device dm-1-8. Jun 13 15:20:37 oberon kernel: [117379.593659] EXT4-fs (dm-1): Remounting filesystem read-only $ uname -a Linux oberon 3.13.0-54-generic #91-Ubuntu SMP Tue May 26 19:15:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423672 Title: ext4 turned read-only during logrotate daily run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423672] Re: ext4 turned read-only during logrotate daily run
Indeed I haven't seen this error in a few weeks, the last time was maybe around six-eight weeks ago. But we all know how absence of evidence isn't evidence of absence :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423672 Title: ext4 turned read-only during logrotate daily run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423672] Re: ext4 turned read-only during logrotate daily run
FWIW, I've seen this happen, too, basically since I upgraded to Trusty, I believe. Only ever happens on VMs, never on physical machines. All my virtual disks use Virtio, cache mode 'none' (yeah, I know), I/O mode 'native', with raw LVM volumes as backend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423672 Title: ext4 turned read-only during logrotate daily run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296276] Re: Unlocking with greeter fails to properly renew kerberos tickets with pam-krb5
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296276 Title: Unlocking with greeter fails to properly renew kerberos tickets with pam-krb5 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1296276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249777] Re: libsss-sudo generated nsswitch.conf leads to error messages upon sudo invocation
Hi Timo, please notice the timestamp of the comment in which I said that sudo didn't change. I didn't run Trusty back then. It was just to point out that the error did not occur in Raring, but sudo hadn't changed, so it could not have introduced the error. But I can also confirm that the error still occurs with 14.04: antares : May 3 13:30:18 : oliver : problem with defaults entries ; TTY=pts/22 ; PWD=/home/oliver ; $ apt-cache policy sudo sudo: Installed: 1.8.9p5-1ubuntu1 That version indeed has the fix from RH BZ. But I've only now seen the patch that was attached to the bug. If you look at my debug trace above, it says that sss_error is 32570 (which probably isn't the error code for ENOENT). Then take a look at the diff from RH BZ again. In the last line, they didn't change the -1 to 0 as they did a few lines above that, so if sss_error is neither ENOENT nor 0, they return -1, which sudo doesn't understand. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249777 Title: libsss-sudo generated nsswitch.conf leads to error messages upon sudo invocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1249777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249777] Re: libsss-sudo generated nsswitch.conf leads to error messages upon sudo invocation
nope, spoke to soon. I just tested a build with the second debug_return_int(-1) changed to debug_return_int(0) and the error still occurs. No idea then, sorry :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249777 Title: libsss-sudo generated nsswitch.conf leads to error messages upon sudo invocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1249777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296276] Re: Unlocking with greeter fails to properly renew kerberos tickets with pam-krb5
Sorry for the delay, I wanted to wait with the testing until my ticket lifetime ran out. Anyway, I can confirm that using lightdm 1.10.1-0ubuntu1 causes the ticket cache to be automatically refreshed upon unlocking the screen, and there is no need to run kinit manually anymore. Again, I'm using sssd as backend. Tested both within the ticket lifetime as well as after the tickets expired. I cannot verify if the leaking of the root-owned ticket cache is fixed, as that didn't happen at all with sssd to begin with. Because of that I'm hesitant to change the tag to verification-done already. Maybe Brian will chime in as well to confirm that part. Otherwise I'll change the tag in a few days. Thanks for the quick response! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296276 Title: Unlocking with greeter fails to properly renew kerberos tickets with pam-krb5 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1296276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296276] Re: Unlocking with greeter fails to properly renew kerberos tickets with pam-krb5
FWIW, I encountered a similar problem, using sssd instead of pam-krb5, though. I can also confirm that the packages from the PPA make lightdm correctly refresh Kerberos credentials and thus fix the issue I had. It would be very welcome indeed if that fix made it into the trusty repository proper. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296276 Title: Unlocking with greeter fails to properly renew kerberos tickets with pam-krb5 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1296276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1118434] Re: lvm - freez any lvm command after lvremove
** Bug watch added: Debian Bug tracker #659762 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659762 ** Also affects: lvm2 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659762 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1118434 Title: lvm - freez any lvm command after lvremove To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/1118434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1118434] Re: lvm - freez any lvm command after lvremove
This problem was also present in Debian. I linked the corresponding bug report. It's also now fixed in Debian stable. Unstable had the fix since summer, from which it got into Saucy, so 13.10 should not be affected (haven't yet verified that, but the fix is in lvm2 2.02.98-05 and 13.10 has 2.02.98-06, so it's a good bet). The Debian bug report also has a few workarounds for those still stuck on earlier releases. And I guess the fix should probably be backported to 12.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1118434 Title: lvm - freez any lvm command after lvremove To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/1118434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249777] Re: libsss-sudo generated nsswitch.conf leads to error messages upon sudo invocation
I know that the sudo package did not change _at all_ since Raring, where the problem didn't show up. sssd on the other hand changed quite a lot. It affects both local and LDAP users. I don't have any sudo config in LDAP, which is probably the problem. What I believe happens is that either or both of sudo and sssd do not correctly cope with the situation of the sudo configuration not being available in the sssd backing store. Sudo asks sssd for the cn=defaults entry from LDAP, sssd looks for it, doesn't find anything and returns an error. Sudo sees the error and complains. I can come up with three possible solutions: 1) patch sudo to not log a message when sssd returns an error. = probably not the best solution, since we may miss real errors, too. 2) patch sssd to not return an error when the configuration isn't found. = probably slightly better than (1), but we still might miss real errors (I think). BTW, the offending code starts here: https://git.fedorahosted.org/cgit/sssd.git/tree/src/sss_client/sudo/sss_sudo.c#n109 3) patch the sssd package to not alter the nsswitch.conf. = this is probably the best solution. I think the people that store the sudo config in LDAP are quite the minority. I also think that those people know that they need to modify their nsswitch.conf for their configuration to work. Goes a bit against the spirit of Ubuntu, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249777 Title: libsss-sudo generated nsswitch.conf leads to error messages upon sudo invocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1249777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249772] [NEW] sssd packages install the same logrotate file twice with different names
Public bug reported: Hello, I upgraded from Raring to Saucy yesterday. This morning I found that logrotate complains about duplicate entries: /etc/cron.daily/logrotate: error: sssd-common:1 duplicate log entry for /var/log/sssd/krb5_child.log Indeed /etc/logrotate.d contains two files that belong to sssd packages: $ dpkg -S /etc/logrotate.d/sssd* sssd: /etc/logrotate.d/sssd sssd-common: /etc/logrotate.d/sssd-common Both files are identical, so one of them is superflouos: $ diff /etc/logrotate.d/sssd* $ ** Affects: sssd (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/1249772 Title: sssd packages install the same logrotate file twice with different names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1249772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249777] [NEW] libsss-sudo generated nsswitch.conf leads to error messages upon sudo invocation
Public bug reported: Hello, the postinst script for libsss-sudo adds the following line to /etc/nsswitch.conf: sudoers:files sss On my LDAP+krb5 setup, this leads to the following error message when either LDAP or local users invoke sudo: Nov 9 17:34:41 charon sudo: oliver : problem with defaults entries ; TTY=pts/0 ; PWD=/etc ; The sudo invocation succeeds nonetheless, so this is mainly an annoying cosmetic issue, since a mail is sent to root everytime someone runs sudo. Running a debug trace on sudo shows the following: Nov 9 17:34:41 sudo[3297] - update_defaults @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/defaults.c:528 := true Nov 9 17:34:41 sudo[3297] - sudo_file_setdefs @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/parse.c:146 := 0 Nov 9 17:34:41 sudo[3297] - sudo_sss_open @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:243 Nov 9 17:34:41 sudo[3297] - sudo_sss_open @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:298 := 0 Nov 9 17:34:41 sudo[3297] - sudo_sss_parse @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:319 Nov 9 17:34:41 sudo[3297] - sudo_sss_parse @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:320 := 0 Nov 9 17:34:41 sudo[3297] - sudo_sss_setdefs @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:331 Nov 9 17:34:41 sudo[3297] Looking for cn=defaults Nov 9 17:34:41 sudo[3297] handle-fn_send_recv_defaults: != 0, sss_error=32570 Nov 9 17:34:41 sudo[3297] - sudo_sss_setdefs @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/sssd.c:343 := -1 Nov 9 17:34:41 sudo[3297] - log_error @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:473 Nov 9 17:34:41 sudo[3297] - vlog_error @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:421 Nov 9 17:34:41 sudo[3297] - set_perms @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/set_perms.c:116 Nov 9 17:34:41 sudo[3297] set_perms: PERM_ROOT: uid: [0, 0, 0] - [0, 0, 0] Nov 9 17:34:41 sudo[3297] - sudo_grlist_addref @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/pwutil.c:770 Nov 9 17:34:41 sudo[3297] - sudo_grlist_addref @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/pwutil.c:772 Nov 9 17:34:41 sudo[3297] - set_perms @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/set_perms.c:350 := true Nov 9 17:34:41 sudo[3297] - new_logline @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:746 Nov 9 17:34:41 sudo[3297] - new_logline @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:867 := problem with defaults entries ; TTY=pts/0 ; PWD=/etc ; Nov 9 17:34:41 sudo[3297] - send_mail @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:524 Nov 9 17:34:41 sudo[3297] - do_syslog @ /build/buildd/sudo-1.8.6p3/plugins/sudoers/logging.c:138 I have found a similar report in Redhat's Bugzilla, but I'm not entirely sure if it's the same problem. There are slight differences in the debug trace: https://bugzilla.redhat.com/show_bug.cgi?id=879633 Removing the sss statement from the sudoers line in nsswitch.conf works around the problem. ** Affects: sssd (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/1249777 Title: libsss-sudo generated nsswitch.conf leads to error messages upon sudo invocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1249777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249772] Re: sssd packages install the same logrotate file twice with different names
** Description changed: Hello, I upgraded from Raring to Saucy yesterday. This morning I found that logrotate complains about duplicate entries: /etc/cron.daily/logrotate: error: sssd-common:1 duplicate log entry for /var/log/sssd/krb5_child.log Indeed /etc/logrotate.d contains two files that belong to sssd packages: $ dpkg -S /etc/logrotate.d/sssd* sssd: /etc/logrotate.d/sssd sssd-common: /etc/logrotate.d/sssd-common - Both files are identical, so one of them is superflouos: + Both files are identical, so one of them is superfluous: $ diff /etc/logrotate.d/sssd* $ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249772 Title: sssd packages install the same logrotate file twice with different names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1249772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1224087] Re: [Fujitsu Esprimo Mobile D9500] No auto-mute with Intel HD Audio
Alright, I'm thoroughly confused now. When I boot the Quantal live CD, the problem is gone, the speakers get muted as they should be. However, I still can't get it to work when I downgrade the kernel to the same version used on the CD. I even tried downgrading ALSA and Pulseaudio as well to no avail. I don't remember touching any config files that belong to the sound subsystems, but that's the only explanation I can come up with at the moment. I'll probably try re-installing the damn thing and hope it goes away. Thanks anyway for the support! ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224087 Title: [Fujitsu Esprimo Mobile D9500] No auto-mute with Intel HD Audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1224087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1224087] [NEW] [Fujitsu Esprimo Mobile D9500] No auto-mute with Intel HD Audio
Public bug reported: Hello, since upgrading to Ubuntu 13.04, I noticed that the line-out channel does not get muted anymore when I plug my headphones in. To isolate the bug, I installed the kernel packages from Quantal (linux- image 3.5.0-28), rebooted and tried to reproduce the problem. I was unable to do so, so I am pretty confident that the bug is somewhere in the kernel, probably the snd-hda-intel driver module. I also checked to see if the bug was fixed in the current mainline kernel using the Mainline Kernel PPA. As of Kernel 3.11, the bug still persists. Please let me know if you need any more information. Steps to reproduce: 1/ Cold boot the system 2/ play audio = result: audio can be heard on the speakers 3/ plug in headphones 4/ play audio = result: audio gets played on _both_ headphones and speakers Thank you! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oliver 2339 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Wed Sep 11 21:37:37 2013 HibernationDevice: RESUME=UUID=a13d7533-1e8c-4f5d-8685-0e94dc34ef57 MachineType: FUJITSU SIEMENS ESPRIMO Mobile D9500 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=/dev/mapper/vg0-root ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-30-generic N/A linux-backports-modules-3.8.0-30-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-05-01 (133 days ago) dmi.bios.date: 04/22/2008 dmi.bios.vendor: Phoenix dmi.bios.version: 1.06 - 046 - 1566 dmi.board.name: Z11D dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnPhoenix:bvr1.06-046-1566:bd04/22/2008:svnFUJITSUSIEMENS:pnESPRIMOMobileD9500:pvr1.0:rvnFUJITSUSIEMENS:rnZ11D:rvr1.0:cvnFUJITSUSIEMENS:ct10:cvr1.0: dmi.product.name: ESPRIMO Mobile D9500 dmi.product.version: 1.0 dmi.sys.vendor: FUJITSU SIEMENS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224087 Title: [Fujitsu Esprimo Mobile D9500] No auto-mute with Intel HD Audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1224087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180526] Re: [Fujitsu Esprimo E5916] No automute w/ Intel HD Audio after suspend
Hello, I opened a new bug for the Esprimo Mobile D9500, it is bug #1224087. I think a backport for Raring won't be necessary, seeing that I'm currently the only one affected by this and Saucy will be out soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180526 Title: [Fujitsu Esprimo E5916] No automute w/ Intel HD Audio after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1224087] Re: [Fujitsu Esprimo Mobile D9500] No auto-mute with Intel HD Audio
Yeah, I already did, as I mentioned in the original description. With 3.11, the bug is still there. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224087 Title: [Fujitsu Esprimo Mobile D9500] No auto-mute with Intel HD Audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1224087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1224087] Re: [Fujitsu Esprimo Mobile D9500] No auto-mute with Intel HD Audio
** Description changed: Hello, since upgrading to Ubuntu 13.04, I noticed that the line-out channel - does not get muted anymore when I plug my headphones in. + does not get muted anymore when I plug my headphones into the headphone + jack on the laptop. + + When plugging the headphones into the jack located on the port + replicator, the line-out channel _does_ get muted. (The port replicator + was not connected when I gathered the attached diagnostic data). To isolate the bug, I installed the kernel packages from Quantal (linux- image 3.5.0-28), rebooted and tried to reproduce the problem. I was unable to do so, so I am pretty confident that the bug is somewhere in the kernel, probably the snd-hda-intel driver module. I also checked to see if the bug was fixed in the current mainline kernel using the Mainline Kernel PPA. As of Kernel 3.11, the bug still persists. Please let me know if you need any more information. Steps to reproduce: 1/ Cold boot the system 2/ play audio = result: audio can be heard on the speakers 3/ plug in headphones 4/ play audio = result: audio gets played on _both_ headphones and speakers Thank you! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: oliver 2339 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: oliver 2339 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Wed Sep 11 21:37:37 2013 HibernationDevice: RESUME=UUID=a13d7533-1e8c-4f5d-8685-0e94dc34ef57 MachineType: FUJITSU SIEMENS ESPRIMO Mobile D9500 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=/dev/mapper/vg0-root ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.8.0-30-generic N/A - linux-backports-modules-3.8.0-30-generic N/A - linux-firmware1.113 + linux-restricted-modules-3.8.0-30-generic N/A + linux-backports-modules-3.8.0-30-generic N/A + linux-firmware1.113 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-05-01 (133 days ago) dmi.bios.date: 04/22/2008 dmi.bios.vendor: Phoenix dmi.bios.version: 1.06 - 046 - 1566 dmi.board.name: Z11D dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnPhoenix:bvr1.06-046-1566:bd04/22/2008:svnFUJITSUSIEMENS:pnESPRIMOMobileD9500:pvr1.0:rvnFUJITSUSIEMENS:rnZ11D:rvr1.0:cvnFUJITSUSIEMENS:ct10:cvr1.0: dmi.product.name: ESPRIMO Mobile D9500 dmi.product.version: 1.0 dmi.sys.vendor: FUJITSU SIEMENS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224087 Title: [Fujitsu Esprimo Mobile D9500] No auto-mute with Intel HD Audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1224087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180526] Re: [Fujitsu Esprimo E5916] No automute w/ Intel HD Audio after suspend
** Summary changed: - [Fujitsu Esprimo Mobile D9500] No automute w/ Intel HD Audio after suspend + [Fujitsu Esprimo E5916] No automute w/ Intel HD Audio after suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180526 Title: [Fujitsu Esprimo E5916] No automute w/ Intel HD Audio after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180526] Re: [13.04] No automute w/ Intel HD Audio after suspend
The model is a Fujitsu(-Siemens) Esprimo Mobile D9500. I haven't yet tested whether 3.11 fixes the problem, though. Please hang on, I'll get back to you before the weekend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180526 Title: [13.04] No automute w/ Intel HD Audio after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180526] Re: [Fujitsu Esprimo Mobile D9500] No automute w/ Intel HD Audio after suspend
Sorry, seems like I'm not fully awake yet. I originally encountered this bug on my Fujitsu Esprimo E5916, but it happens on the Esprimo Mobile as well. The attachments in this bug are all from the E5916, which also has a new BIOS available. Still, I'm going to test 3.11 first before I fiddle with the BIOS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180526 Title: [Fujitsu Esprimo Mobile D9500] No automute w/ Intel HD Audio after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180526] Re: [Fujitsu Esprimo Mobile D9500] No automute w/ Intel HD Audio after suspend
The results are in: Esprimo E5916: * fixed by Linux 3.11 (from the mainline PPA) * BIOS upgrade wasn't necessary Esprimo Mobile D9500: * still occurs with Linux 3.11 * even with BIOS upgrade Given that the log files and other attachments in this bug are all from the E5916, do you want me to open another bug for the D9500? This bug could then be marked as 'kernel-fixed-upstream' and closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180526 Title: [Fujitsu Esprimo Mobile D9500] No automute w/ Intel HD Audio after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175317] Re: incorrect path in apparmor profile prevents sssd from working
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175317 Title: incorrect path in apparmor profile prevents sssd from working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1175317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175317] Re: incorrect path in apparmor profile prevents sssd from working
I confirm that 1.9.4-0ubuntu4.2 fixes the issue. Thanks all! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175317 Title: incorrect path in apparmor profile prevents sssd from working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1175317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067386] Re: dm thin facility incomplete - thin-provisioning-tools not packaged
The thin-provisiong-tools package has landed in Sid a few days ago: http://packages.debian.org/sid/thin-provisioning-tools. Can it still be included in Saucy so that the feature may be stabilized for 14.04 LTS? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067386 Title: dm thin facility incomplete - thin-provisioning-tools not packaged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1067386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175317] Re: incorrect path in apparmor profile prevents sssd from working
Hello,
I'm sorry, but the -proposed package does not work.
The apparmor profile now says
/usr/lib/@{multiarch}/sssd/sssd/* rix,
but the correct statement is this, as mentioned above in my original
report:
/usr/lib/@{multiarch}/sssd/* rix,
ie. only one sssd in the path.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175317
Title:
incorrect path in apparmor profile prevents sssd from working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1175317/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180526] Re: [13.04] No automute w/ Intel HD Audio after suspend
By accident, I found another data point for this bug: Normally, I have the headphones unplugged when I switch my PC on, and the bug manifests itself as described above. However, if the headphones are plugged in when I switch the PC on, it works like this: - the headphones work normally - if the headphones are unplugged, then there is no sound at all ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180526 Title: [13.04] No automute w/ Intel HD Audio after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180526] Re: [13.04] No automute w/ Intel HD Audio after suspend
** Description changed: Hello, since upgrading to Ubuntu 13.04, I noticed that the line-out channel does not get muted anymore when I plug my headphones in. This only occurs _after_ I suspended and resumed the system, however. Plugging headphones in before I suspend properly mutes line-out, as expected. To isolate the bug, I installed the kernel packages from Quantal (linux- image 3.5.0-28), rebooted and tried to reproduce the problem. I was unable to do so, so I am pretty confident that the bug is somewhere in the kernel, probably the snd-hda-intel driver module. - Please let me know if I you need any more information. + Please let me know if you need any more information. Steps to reproduce: 1/ Have line-out connected to speakers 2/ Cold boot the system 3/ suspend 4/ resume 5/ play audio = result: audio can be heard on the speakers 6/ plug in headphones 7/ play audio = result: audio gets played on _both_ headphones and speakers Thank you! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.30 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: oliver 2489 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: oliver 2489 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed May 15 21:45:24 2013 HibernationDevice: RESUME=UUID=19edb29f-c4bf-4af0-9f0d-0521dc9b89e4 IwConfig: - eth0 no wireless extensions. - - lono wireless extensions. - - virbr0no wireless extensions. + eth0 no wireless extensions. + + lono wireless extensions. + + virbr0no wireless extensions. MachineType: FUJITSU SIEMENS ESPRIMO E MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic root=/dev/mapper/vg0-lv_root ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.8.0-19-generic N/A - linux-backports-modules-3.8.0-19-generic N/A - linux-firmware1.106 + linux-restricted-modules-3.8.0-19-generic N/A + linux-backports-modules-3.8.0-19-generic N/A + linux-firmware1.106 RfKill: - + SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-05-07 (8 days ago) dmi.bios.date: 09/18/2006 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.02.2348.A2 dmi.board.name: D2348-A2 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2348-A2 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: ESPE dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.02.2348.A2:bd09/18/2006:svnFUJITSUSIEMENS:pnESPRIMOE:pvr:rvnFUJITSUSIEMENS:rnD2348-A2:rvrS26361-D2348-A2:cvnFUJITSUSIEMENS:ct6:cvrESPE: dmi.product.name: ESPRIMO E dmi.sys.vendor: FUJITSU SIEMENS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180526 Title: [13.04] No automute w/ Intel HD Audio after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180526] [NEW] [13.04] No automute w/ Intel HD Audio after suspend
Public bug reported: Hello, since upgrading to Ubuntu 13.04, I noticed that the line-out channel does not get muted anymore when I plug my headphones in. This only occurs _after_ I suspended and resumed the system, however. Plugging headphones in before I suspend properly mutes line-out, as expected. To isolate the bug, I installed the kernel packages from Quantal (linux- image 3.5.0-28), rebooted and tried to reproduce the problem. I was unable to do so, so I am pretty confident that the bug is somewhere in the kernel, probably the snd-hda-intel driver module. Please let me know if you need any more information. Steps to reproduce: 1/ Have line-out connected to speakers 2/ Cold boot the system 3/ suspend 4/ resume 5/ play audio = result: audio can be heard on the speakers 6/ plug in headphones 7/ play audio = result: audio gets played on _both_ headphones and speakers Thank you! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.30 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oliver 2489 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed May 15 21:45:24 2013 HibernationDevice: RESUME=UUID=19edb29f-c4bf-4af0-9f0d-0521dc9b89e4 IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: FUJITSU SIEMENS ESPRIMO E MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic root=/dev/mapper/vg0-lv_root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-05-07 (8 days ago) dmi.bios.date: 09/18/2006 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.02.2348.A2 dmi.board.name: D2348-A2 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2348-A2 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: ESPE dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.02.2348.A2:bd09/18/2006:svnFUJITSUSIEMENS:pnESPRIMOE:pvr:rvnFUJITSUSIEMENS:rnD2348-A2:rvrS26361-D2348-A2:cvnFUJITSUSIEMENS:ct6:cvrESPE: dmi.product.name: ESPRIMO E dmi.sys.vendor: FUJITSU SIEMENS ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug raring third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180526 Title: [13.04] No automute w/ Intel HD Audio after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1179640] Re: Version number is misleading, confusing and not sane
If it helps any, here's a handy mapping table from Ubuntu to mainline kernel versions: http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html ** Changed in: linux (Ubuntu) Status: Confirmed = Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179640 Title: Version number is misleading, confusing and not sane To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1179640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175317] [NEW] incorrect path in apparmor profile prevents sssd from working
Public bug reported:
An incorrect path statement in sssd's apparmor profile prevents sssd
from forking its helper services. The corresponding log messages look
like this:
/var/log/syslog:
May 1 21:55:17 ares sssd: Starting up
May 1 21:55:18 ares kernel: [ 23.115299] type=1400 audit(1367438118.048:16):
apparmor=DENIED operation=exec parent=925 profile=/usr/sbin/sssd
name=/usr/lib/x86_64-linux-gnu/sssd/sssd_be pid=929 comm=sssd
requested_mask=x denied_mask=x fsuid=0 ouid=0
May 1 21:55:18 ares kernel: [ 23.152108] type=1400 audit(1367438118.088:17):
apparmor=DENIED operation=exec parent=925 profile=/usr/sbin/sssd
name=/usr/lib/x86_64-linux-gnu/sssd/sssd_be pid=930 comm=sssd
requested_mask=x denied_mask=x fsuid=0 ouid=0
May 1 21:55:24 ares kernel: [ 29.156118] type=1400 audit(1367438124.092:48):
apparmor=DENIED operation=exec parent=925 profile=/usr/sbin/sssd
name=/usr/lib/x86_64-linux-gnu/sssd/sssd_be pid=1293 comm=sssd
requested_mask=x denied_mask=x fsuid=0 ouid=0
/etc/apparmor.d/usr.sbin.sssd contains this line:
/usr/lib/sssd/sssd/* rix,
It has to be changed to look like this to make sssd work again:
/usr/lib/@{multiarch}/sssd/* rix,
The bug affects Ubuntu 13.04 (and probably Saucy) only.
** Affects: sssd (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/1175317
Title:
incorrect path in apparmor profile prevents sssd from working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1175317/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 934422] Re: latest thunderbird version not compatible available lightning version
FWIW, updated packages are currently in the 'proposed' repository, so if you need lightning urgently, you can either enable that (careful though, that will probably pull in a lot more updated packages, which might lead to unexpected side-effects ) or install the packages manually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/934422 Title: latest thunderbird version not compatible available lightning version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightning-extension/+bug/934422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 934422] Re: latest thunderbird version not compatible available lightning version
Wow, that was fast. The packages are available in -security now, so I guess this is fixed then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/934422 Title: latest thunderbird version not compatible available lightning version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightning-extension/+bug/934422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 934422] Re: latest thunderbird version not compatible available lightning version
** Changed in: lightning-extension (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/934422 Title: latest thunderbird version not compatible available lightning version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightning-extension/+bug/934422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604998] Re: open-vm-tools (CLI tools) recommends gui tools
Oh wow. That's because the GUI package has been merged with the CLI- only package as of Oneiric. And again, this change is in Ubuntu only, Debian still does The Right Thing(tm). What the hell? Can we pleased get this fixed for the next LTS? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/604998 Title: open-vm-tools (CLI tools) recommends gui tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/604998/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 604998] Re: open-vm-tools (CLI tools) recommends gui tools
Oh wow. That's because the GUI package has been merged with the CLI- only package as of Oneiric. And again, this change is in Ubuntu only, Debian still does The Right Thing(tm). What the hell? Can we pleased get this fixed for the next LTS? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/604998 Title: open-vm-tools (CLI tools) recommends gui tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/604998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 525154] Re: mountall for /var or other nfs mount races with rpc.statd
Hi, this is turning into a forum discussion real fast, and really has no place here. I suggest we take it someplace else. Ubuntu-devel, maybe? On 2011-07-19 12:17, Brian J. Murrell wrote: On 11-07-18 04:27 PM, Steve Langasek wrote: This appears to be bug #523484. To the best of my understanding, this describes a feature that is missing Uhm, not so much missing as broken. when using a separate /var (the ureadahead job will run but not do anything useful). It's not even that nice. What it will do is litter the boot with error messages I think litter is a bit strong. There's a single line that says that ureadahead terminated with status soandso. That's hardly littering. And that's about it with regard to the impact of that bug. I have never seen a system not boot due to it, and I have used (and am using) Lucid on bare-metal servers, virtual machines, desktops and road warrior laptops, all with a separate /var. which is annoying and distracting at best and a red herring when there are other upstart/mountall bugs, at worst. I'll agree that it is annoying, but any admin that sees the ureadahead message when a system shows other problems and goes 'oh, ureadahead croaked, that must be the cause of it all!' seriously needs to drop it right then and there and go stack shelves somewhere. This is certainly a bug, but not something that we are likely to backport to lucid even when a fix becomes available. So instead you let the above situation continue on ad infinitum, confusing new users? That's not what Steve said. I think you would be hard pressed to convince any of the Ubuntu developers that it has a major impact on the usability of Ubuntu that systems with a separate /var don't get the boot speed enhancement from ureadahead! I agree. Exactly my point and the point of mine (and others') frustration. You guys let a bug get out into the wild by not testing a use-case that is and/or should be very common in the server use space and now that it's out there, you are just letting it ride. Again, I agree that the message is annoying, and it would be nice if we could get rid of it. But I would describe it as 'cosmetic' at best, and hardly something to get frustrated about, much less fault the developers for not giving it highest priority. So is this seriously something to get so worked up about? Also, you know, Ubuntu makes alphas public for a reason. Regards, Oliver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/525154 Title: mountall for /var or other nfs mount races with rpc.statd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/525154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604998] Re: open-vm-tools (CLI tools) recommends gui tools
Thanks Clint! I don't know if anybody has noticed this yet, but this problem exists in Ubuntu only. The same package in Debian merely suggests: open-vm- toolbox. Oh, and the changelog gives the reason why: LP #391224. I guess we have conflicting interests here. Personally, I'd argue for dropping the recommends: back to a suggests: as well. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/604998 Title: open-vm-tools (CLI tools) recommends gui tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/604998/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 604998] Re: open-vm-tools (CLI tools) recommends gui tools
Thanks Clint! I don't know if anybody has noticed this yet, but this problem exists in Ubuntu only. The same package in Debian merely suggests: open-vm- toolbox. Oh, and the changelog gives the reason why: LP #391224. I guess we have conflicting interests here. Personally, I'd argue for dropping the recommends: back to a suggests: as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/604998 Title: open-vm-tools (CLI tools) recommends gui tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/604998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 700945] Re: backport of patch for error message undefined method `closed?' for Nil:NilClass required.
Hi, I successfully verified that the new package passes the test case. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/700945 Title: backport of patch for error message undefined method `closed?' for Nil:NilClass required. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 700945] Re: backport of patch for error message undefined method `closed?' for Nil:NilClass required.
Hi, I successfully verified that the new package passes the test case. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/700945 Title: backport of patch for error message undefined method `closed?' for Nil:NilClass required. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 700945] Re: backport of patch for error message undefined method `closed?' for Nil:NilClass required.
Hi Bryce, I was thinking along those lines, until I saw that the original package patches the source also. Since I did not want to bloat the patch unnecessarily, I went with patching the source as well instead of converting the source package to a quilt-based one. Thanks, Oliver -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/700945 Title: backport of patch for error message undefined method `closed?' for Nil:NilClass required. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 700945] Re: backport of patch for error message undefined method `closed?' for Nil:NilClass required.
Hi Bryce, I was thinking along those lines, until I saw that the original package patches the source also. Since I did not want to bloat the patch unnecessarily, I went with patching the source as well instead of converting the source package to a quilt-based one. Thanks, Oliver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/700945 Title: backport of patch for error message undefined method `closed?' for Nil:NilClass required. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 700945] Re: backport of patch for error message undefined method `closed?' for Nil:NilClass required.
Nominating for SRU, fulfills: (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages. Justification: The bug hides error messages, which makes diagnosing connection problems to a puppetmaster a real PITA. The fix is from upstream (Maverick's puppet package has a newer version which already contains the fix): http://projects.puppetlabs.com/projects/puppet/repository/revisions/ae0b0bf23e418e8c6665e9dc135148b78bdbd913 Regression potential: none. TEST CASE: (these instructions assume an already working puppet installation) 1) On a puppet client computer, stop the puppet service 2) Add a new line to your /etc/hosts file, containing an entry for the IP address of your puppetmaster, but with a wrong hostname, eg. like this: 1.2.3.4 foo.local 3) Add this line to your puppet client's /etc/puppet/puppet.conf file: server=foo.local 4) Run puppetd --test on the client Wrong output: info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': undefined method `closed?' for nil:NilClass err: /File[/var/lib/puppet/lib]: Failed to retrieve current state of resource: undefined method `closed?' for nil:NilClass Could not retrieve file metadata for puppet://foo.local/plugins: undefined method `closed?' for nil:NilClass err: Could not retrieve catalog from remote server: undefined method `closed?' for nil:NilClass warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Expected output: info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': hostname was not match with the server certificate err: /File[/var/lib/puppet/lib]: Failed to retrieve current state of resource: hostname was not match with the server certificate Could not retrieve file metadata for puppet://foo.local/plugins: hostname was not match with the server certificate err: Could not retrieve catalog from remote server: hostname was not match with the server certificate warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run ** Patch added: puppet_0.25.4-2ubuntu6.1.diff https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/700945/+attachment/1973794/+files/puppet_0.25.4-2ubuntu6.1.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/700945 Title: backport of patch for error message undefined method `closed?' for Nil:NilClass required. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 700945] Re: backport of patch for error message undefined method `closed?' for Nil:NilClass required.
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/700945 Title: backport of patch for error message undefined method `closed?' for Nil:NilClass required. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 700945] Re: backport of patch for error message undefined method `closed?' for Nil:NilClass required.
Nominating for SRU, fulfills: (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages. Justification: The bug hides error messages, which makes diagnosing connection problems to a puppetmaster a real PITA. The fix is from upstream (Maverick's puppet package has a newer version which already contains the fix): http://projects.puppetlabs.com/projects/puppet/repository/revisions/ae0b0bf23e418e8c6665e9dc135148b78bdbd913 Regression potential: none. TEST CASE: (these instructions assume an already working puppet installation) 1) On a puppet client computer, stop the puppet service 2) Add a new line to your /etc/hosts file, containing an entry for the IP address of your puppetmaster, but with a wrong hostname, eg. like this: 1.2.3.4 foo.local 3) Add this line to your puppet client's /etc/puppet/puppet.conf file: server=foo.local 4) Run puppetd --test on the client Wrong output: info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': undefined method `closed?' for nil:NilClass err: /File[/var/lib/puppet/lib]: Failed to retrieve current state of resource: undefined method `closed?' for nil:NilClass Could not retrieve file metadata for puppet://foo.local/plugins: undefined method `closed?' for nil:NilClass err: Could not retrieve catalog from remote server: undefined method `closed?' for nil:NilClass warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Expected output: info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': hostname was not match with the server certificate err: /File[/var/lib/puppet/lib]: Failed to retrieve current state of resource: hostname was not match with the server certificate Could not retrieve file metadata for puppet://foo.local/plugins: hostname was not match with the server certificate err: Could not retrieve catalog from remote server: hostname was not match with the server certificate warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run ** Patch added: puppet_0.25.4-2ubuntu6.1.diff https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/700945/+attachment/1973794/+files/puppet_0.25.4-2ubuntu6.1.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/700945 Title: backport of patch for error message undefined method `closed?' for Nil:NilClass required. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 700945] Re: backport of patch for error message undefined method `closed?' for Nil:NilClass required.
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/700945 Title: backport of patch for error message undefined method `closed?' for Nil:NilClass required. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719898] [NEW] logwatch does not report cron events
Public bug reported: Binary package hint: logwatch Hello, Debian/Ubuntu ships a cron service definition (in dist.conf/services/cron), which does not match any cron logfile entries due to a wrong OnlyService statement in said service definition. Currently, it looks like this: *OnlyService = (CROND|\/USR\/SBIN\/CRON|\/usr\/sbin\/cron) However, the logfile entries for cron look like this, so they don't match: Feb 16 09:11:11 deimos cron[641]: (CRON) INFO (pidfile fd = 3) Feb 16 09:11:11 deimos cron[654]: (CRON) STARTUP (fork ok) Feb 16 09:11:11 deimos cron[654]: (CRON) INFO (Running @reboot jobs) Feb 16 09:17:01 deimos CRON[923]: (root) CMD ( cd / run-parts --report /etc/cron.hourly) I suggest changing the OnlyService statement to this (patch attached): *OnlyService = (CRON|cron|CROND|\/USR\/SBIN\/CRON|\/usr\/sbin\/cron) This applies to all Ubuntu releases, from at least Lucid to Natty. Thanks! ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in ubuntu. https://bugs.launchpad.net/bugs/719898 Title: logwatch does not report cron events -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 719898] Re: logwatch does not report cron events
** Patch added: logwatch_cron.diff https://bugs.launchpad.net/bugs/719898/+attachment/1853357/+files/logwatch_cron.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in ubuntu. https://bugs.launchpad.net/bugs/719898 Title: logwatch does not report cron events -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 719898] [NEW] logwatch does not report cron events
Public bug reported: Binary package hint: logwatch Hello, Debian/Ubuntu ships a cron service definition (in dist.conf/services/cron), which does not match any cron logfile entries due to a wrong OnlyService statement in said service definition. Currently, it looks like this: *OnlyService = (CROND|\/USR\/SBIN\/CRON|\/usr\/sbin\/cron) However, the logfile entries for cron look like this, so they don't match: Feb 16 09:11:11 deimos cron[641]: (CRON) INFO (pidfile fd = 3) Feb 16 09:11:11 deimos cron[654]: (CRON) STARTUP (fork ok) Feb 16 09:11:11 deimos cron[654]: (CRON) INFO (Running @reboot jobs) Feb 16 09:17:01 deimos CRON[923]: (root) CMD ( cd / run-parts --report /etc/cron.hourly) I suggest changing the OnlyService statement to this (patch attached): *OnlyService = (CRON|cron|CROND|\/USR\/SBIN\/CRON|\/usr\/sbin\/cron) This applies to all Ubuntu releases, from at least Lucid to Natty. Thanks! ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719898 Title: logwatch does not report cron events -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719898] Re: logwatch does not report cron events
** Patch added: logwatch_cron.diff https://bugs.launchpad.net/bugs/719898/+attachment/1853357/+files/logwatch_cron.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719898 Title: logwatch does not report cron events -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
I have just verified that the new packages fix this bug for both Lucid and Maverick. I did not notice any regressions on either VM, nor on a physical system running Lucid. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
I have just verified that the new packages fix this bug for both Lucid and Maverick. I did not notice any regressions on either VM, nor on a physical system running Lucid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
Changelog entry of the fixed version: facter (1.5.7-2) unstable; urgency=low . [ Stig Sandbeck Mathisen ] * Fix upgrade from 1.3.5 to 1.5.1 requires puppet to be restarted, added a note in debian/NEWS about restarting puppet (Closes: #515726) * Add versioned dependency for ruby1.8 (Closes: #585867) * debian/control: bump standards version: no changes * debian/control: Remove unused build dependency on cdbs * Add versioned dependency for ruby1.8 (Closes: #585867) * Cherry-pick domain/fqdn fact fix from upstream (Closes: #515591) . [ Micah Anderson ] * debian/control: add Vcs-Git, Vcs-Browser, and Homepage fields * debian/NEWS: fix lintian syntax-error-in-debian-news-file * debian/facter.8: fix manpage-section-mismatch * cherry pick upstream virtualization support: . openvz fix [#4156] . add kvm support (Closes: #603001) . fix Linux-Vserver of virtual fact [#3397] . add xendomains fact -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
Corrected debdiff for Lucid, thanks to Clint for the advice! ** Patch added: debdiff for Lucid https://bugs.launchpad.net/ubuntu/+source/facter/+bug/708080/+attachment/1810807/+files/facter_1.5.6-2ubuntu2.1.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
** Patch added: debdiff for Maverick https://bugs.launchpad.net/ubuntu/+source/facter/+bug/708080/+attachment/1810808/+files/facter_1.5.7-1ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
Nominating for SRU, fulfills: (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages Justification: it fixes obviously wrong behaviour in regard to a package that is central to the Ubuntu Server product (KVM). The fix is from upstream and has been verified to exist in Natty. Regression potential: Existing puppet manifests which evaluate either the virtual or is_virtual fact will be impacted when run on KVM guests. However, the existence of such manifests is to be doubted, since they would be broken in such an environment anyway. Administrators that have worked around this bug may possibly notice a regression, though. ** Description changed: Binary package hint: facter On current Ubuntu releases (the latest LTS most notably), puppet's facter library does not recognize KVM virtual machines as virtual: $ facter | grep virtual is_virtual = false virtual = physical $ grep -i qemu /proc/cpuinfo model name: QEMU Virtual CPU version 0.12.3 This has already been fixed upstream in version 1.5.8. However, this version has not been packaged for any Ubuntu release yet (not even Natty). The upstream commit with the fix is here: https://github.com/puppetlabs/facter/commit/62b6773a63bb96273fbcb6f79bec524fb67df075 Please also see http://thread.gmane.org/gmane.linux.ubuntu.server/4917. Thanks! + + + TEST CASE: + Run facter | grep virtual in a KVM virtual machine. + + Buggy output: see above. + + Expected output: + $ facter | grep virtual + is_virtual = true + virtual = kvm -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
Changelog entry of the fixed version: facter (1.5.7-2) unstable; urgency=low . [ Stig Sandbeck Mathisen ] * Fix upgrade from 1.3.5 to 1.5.1 requires puppet to be restarted, added a note in debian/NEWS about restarting puppet (Closes: #515726) * Add versioned dependency for ruby1.8 (Closes: #585867) * debian/control: bump standards version: no changes * debian/control: Remove unused build dependency on cdbs * Add versioned dependency for ruby1.8 (Closes: #585867) * Cherry-pick domain/fqdn fact fix from upstream (Closes: #515591) . [ Micah Anderson ] * debian/control: add Vcs-Git, Vcs-Browser, and Homepage fields * debian/NEWS: fix lintian syntax-error-in-debian-news-file * debian/facter.8: fix manpage-section-mismatch * cherry pick upstream virtualization support: . openvz fix [#4156] . add kvm support (Closes: #603001) . fix Linux-Vserver of virtual fact [#3397] . add xendomains fact -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
Corrected debdiff for Lucid, thanks to Clint for the advice! ** Patch added: debdiff for Lucid https://bugs.launchpad.net/ubuntu/+source/facter/+bug/708080/+attachment/1810807/+files/facter_1.5.6-2ubuntu2.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
** Patch added: debdiff for Maverick https://bugs.launchpad.net/ubuntu/+source/facter/+bug/708080/+attachment/1810808/+files/facter_1.5.7-1ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
Nominating for SRU, fulfills: (1) have an obviously safe patch and (2) affect an application rather than critical infrastructure packages Justification: it fixes obviously wrong behaviour in regard to a package that is central to the Ubuntu Server product (KVM). The fix is from upstream and has been verified to exist in Natty. Regression potential: Existing puppet manifests which evaluate either the virtual or is_virtual fact will be impacted when run on KVM guests. However, the existence of such manifests is to be doubted, since they would be broken in such an environment anyway. Administrators that have worked around this bug may possibly notice a regression, though. ** Description changed: Binary package hint: facter On current Ubuntu releases (the latest LTS most notably), puppet's facter library does not recognize KVM virtual machines as virtual: $ facter | grep virtual is_virtual = false virtual = physical $ grep -i qemu /proc/cpuinfo model name: QEMU Virtual CPU version 0.12.3 This has already been fixed upstream in version 1.5.8. However, this version has not been packaged for any Ubuntu release yet (not even Natty). The upstream commit with the fix is here: https://github.com/puppetlabs/facter/commit/62b6773a63bb96273fbcb6f79bec524fb67df075 Please also see http://thread.gmane.org/gmane.linux.ubuntu.server/4917. Thanks! + + + TEST CASE: + Run facter | grep virtual in a KVM virtual machine. + + Buggy output: see above. + + Expected output: + $ facter | grep virtual + is_virtual = true + virtual = kvm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708080] [NEW] facter does not recognize KVM VMs as 'virtual'
Public bug reported: Binary package hint: facter On current Ubuntu releases (the latest LTS most notably), puppet's facter library does not recognize KVM virtual machines as virtual: $ facter | grep virtual is_virtual = false virtual = physical $ grep -i qemu /proc/cpuinfo model name : QEMU Virtual CPU version 0.12.3 This has already been fixed upstream in version 1.5.8. However, this version has not been packaged for any Ubuntu release yet (not even Natty). The upstream commit with the fix is here: https://github.com/puppetlabs/facter/commit/62b6773a63bb96273fbcb6f79bec524fb67df075 Please also see http://thread.gmane.org/gmane.linux.ubuntu.server/4917. Thanks! ** Affects: facter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
Hmpf, it's been fixed already in 1.5.7-3ubuntu1, by way of Debian. ** Changed in: facter (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
** Patch added: Debdiff for Lucid https://bugs.launchpad.net/ubuntu/+source/facter/+bug/708080/+attachment/1809188/+files/lp708080.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 708080] [NEW] facter does not recognize KVM VMs as 'virtual'
Public bug reported: Binary package hint: facter On current Ubuntu releases (the latest LTS most notably), puppet's facter library does not recognize KVM virtual machines as virtual: $ facter | grep virtual is_virtual = false virtual = physical $ grep -i qemu /proc/cpuinfo model name : QEMU Virtual CPU version 0.12.3 This has already been fixed upstream in version 1.5.8. However, this version has not been packaged for any Ubuntu release yet (not even Natty). The upstream commit with the fix is here: https://github.com/puppetlabs/facter/commit/62b6773a63bb96273fbcb6f79bec524fb67df075 Please also see http://thread.gmane.org/gmane.linux.ubuntu.server/4917. Thanks! ** Affects: facter (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/708080 Title: facter does not recognize KVM VMs as 'virtual' -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 628039] Re: open-vm-tools requires xorg but is supposed to be CLI only
*** This bug is a duplicate of bug 604998 *** https://bugs.launchpad.net/bugs/604998 ** This bug has been marked a duplicate of bug 604998 open-vm-tools (CLI tools) recommends gui tools * You can subscribe to bug 604998 by following this link: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/604998/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/628039 Title: open-vm-tools requires xorg but is supposed to be CLI only -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
Hmpf, it's been fixed already in 1.5.7-3ubuntu1, by way of Debian. ** Changed in: facter (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708080] Re: facter does not recognize KVM VMs as 'virtual'
** Patch added: Debdiff for Lucid https://bugs.launchpad.net/ubuntu/+source/facter/+bug/708080/+attachment/1809188/+files/lp708080.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708080 Title: facter does not recognize KVM VMs as 'virtual' -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606715] [NEW] Logfile defintions wrong after changes to logfile rotation in Ubuntu Lucid
Public bug reported:
Binary package hint: logwatch
Hi,
as mentioned in the release notes for Ubuntu 10.04
(https://wiki.ubuntu.com/LucidLynx/ReleaseNotes#Syslog%20upgrade), the
latest rotated logfile receives the extension .1, whereas in previous
releases it was .0.
Many of the logfile definitions in
/usr/share/logwatch/{default,dist}.conf/logfiles are wrong because of this:
default.conf:
$ grep '^LogFile.*.0$' *
daemon.conf:LogFile = daemon.log.0
kernel.conf:LogFile = kern.log.0
maillog.conf:LogFile = mail.log.0
secure.conf:LogFile = auth.log.0
syslog.conf:LogFile = syslog.0
dist.conf:
maillog.conf:LogFile = mail.log.0
messages.conf:LogFile = messages.0
Due to this, logwatch reports contain only half the truth.
I know this is easily fixed locally, but I am of the opinion that it
should work out of the box.
Thanks for listening!
** Affects: logwatch (Ubuntu)
Importance: Undecided
Status: New
--
Logfile defintions wrong after changes to logfile rotation in Ubuntu Lucid
https://bugs.launchpad.net/bugs/606715
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 606715] [NEW] Logfile defintions wrong after changes to logfile rotation in Ubuntu Lucid
Public bug reported:
Binary package hint: logwatch
Hi,
as mentioned in the release notes for Ubuntu 10.04
(https://wiki.ubuntu.com/LucidLynx/ReleaseNotes#Syslog%20upgrade), the
latest rotated logfile receives the extension .1, whereas in previous
releases it was .0.
Many of the logfile definitions in
/usr/share/logwatch/{default,dist}.conf/logfiles are wrong because of this:
default.conf:
$ grep '^LogFile.*.0$' *
daemon.conf:LogFile = daemon.log.0
kernel.conf:LogFile = kern.log.0
maillog.conf:LogFile = mail.log.0
secure.conf:LogFile = auth.log.0
syslog.conf:LogFile = syslog.0
dist.conf:
maillog.conf:LogFile = mail.log.0
messages.conf:LogFile = messages.0
Due to this, logwatch reports contain only half the truth.
I know this is easily fixed locally, but I am of the opinion that it
should work out of the box.
Thanks for listening!
** Affects: logwatch (Ubuntu)
Importance: Undecided
Status: New
--
Logfile defintions wrong after changes to logfile rotation in Ubuntu Lucid
https://bugs.launchpad.net/bugs/606715
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
[Bug 222944] Re: mailto links in Firefox 3.0b5 do not open up Thunderbird compose windows
Alright, so this works for me [tm] to fix this problem: Open firefox and enter about:config into the location bar. Set the filter to mailto. Locate the network.protocol-handler.app.mailto line, right-click and select reset. Close firefox. Open nautilus/thunar/whatever and go to your firefox profile directory (/home/user/.mozilla/firefox/some weird string/) There's a file called mimeTypes.rdf. Remove it (or rename it, if you're the cautious type). Start firefox again. Right-click anywhere and select Send Link A window should pop up that prompts you to choose your mailer application. Locate /usr/bin/thunderbird (or whatever is your preferred app). Click ok and the compose window should show up. For the curious: If you now take a look at the about:config page, you won't find the network.protocol-handler.app.mailto property anymore. It seems it is not used anymore in firefox 3, however having it still set after upgrading seems to seriously confuse firefox 3. -- mailto links in Firefox 3.0b5 do not open up Thunderbird compose windows https://bugs.launchpad.net/bugs/222944 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
Re: [Bug 222944] Re: mailto links in Firefox 3.0b5 do not open up Thunderbird compose windows
Hi Alexander, Alexander Sack wrote... What value do you have in that setting and what happens if you do the instructions above? what would you expect to happen? I think you misunderstood what I wrote. My previous entry was about how to fix this, not how to reproduce the problem. Still, to answer your questions: network.protocol-handler.app.mailto was set to /home/oliver/bin/mailto.sh. Then I ran the instructions that I outlined in my previous post. Afterwards, the network.protocol-handler.app.mailto line is gone from both the about:config page and the prefs.js file. However, mailto links now work. Cheers, Oliver -- mailto links in Firefox 3.0b5 do not open up Thunderbird compose windows https://bugs.launchpad.net/bugs/222944 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
[Bug 222944] Re: mailto links in Firefox 3.0b5 do not open up Thunderbird compose windows
I don't get it. Everytime I post a fix/workaround for a bug here on launchpad, the maintainer misunderstands what the problem is about and the bug report goes all to hell. Sorry, Chandra, for messing this up. So, do I really fail so miserably at making myself clear? Maybe I should just keep my workarounds to myself. -- mailto links in Firefox 3.0b5 do not open up Thunderbird compose windows https://bugs.launchpad.net/bugs/222944 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
[Bug 97175] Re: [xubuntu only]xfce4-session seems to reset xmodmap
Gauvain, after upgrading to Hardy, I confirm your fix works. Thanks a lot! :-) -- [xubuntu only]xfce4-session seems to reset xmodmap https://bugs.launchpad.net/bugs/97175 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
[Bug 97175] Re: [xubuntu only]xfce4-session seems to reset xmodmap
I hope it's ok now for me to close this bug. ** Changed in: xfce-mcs-plugins (Ubuntu) Status: Triaged = Fix Released -- [xubuntu only]xfce4-session seems to reset xmodmap https://bugs.launchpad.net/bugs/97175 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
[Bug 187861] Re: [xubuntu] password dialog reveals desktop when compositor is enabled
Hi! I'd love to, but Xfce does not use Compiz. The xfwm4 window manager has its own compositor built-in. In that settings dialog, I have every checkbox checked. Unchecking them does not help. I also just tried the intel driver instead of the i810 driver, but that also does not help. Thanks, Oliver -- [xubuntu] password dialog reveals desktop when compositor is enabled https://bugs.launchpad.net/bugs/187861 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 187861] [NEW] [xubuntu] password dialog reveals desktop when compositor is enabled
Public bug reported: Binary package hint: gnome-screensaver Xubuntu Gutsy gnome-screensaver 2.20.0-0ubuntu4.2 After upgrading to Xubuntu Gutsy (and thus switching from xscreensaver to gnome-screensaver) I found the following issue: Previously, on Feisty with xscreensaver, if the screen was locked and the user moved the mouse, the screensaver would stop and show the password dialog on top of the frozen screensaver image. With gnome-screensaver on Gutsy, if the screen is locked and the user moves the mouse, the screen clears and shows the complete desktop, open windows and all, with the password dialog on top. This only happens if the Compositor is enabled. After switching it off, the dialog box appears on a black background, as I expected it to. Curiously, if I enter a wrong password, the desktop is then replaced by a black background, even if the compositor is enabled. Feel free to ask for more information, screenshots etc. My video card is an Intel onboard Q965 chipset, using the i810 driver (kernel module X11). DRI uses the i965_dri driver. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- [xubuntu] password dialog reveals desktop when compositor is enabled https://bugs.launchpad.net/bugs/187861 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 35173] Re: [nvidia-glx-legacy] xorg freezes when using nvidia-legacy driver
Whoops, sorry for not replying earlier, I wasn't subscribed any longer. No, I was not using a TNT2, my card was a Geforce2 Pro GTS (NV15). I bought myself an intel-based system a year ago, though, so I can't offer any further help, sorry. -- [nvidia-glx-legacy] xorg freezes when using nvidia-legacy driver https://bugs.launchpad.net/bugs/35173 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48756] Re: initramfs does not handle whole-disk raid devices and partitionable arrays
This is more or less fixed now in feisty (the local-top/mdadm script needs a little sleep to wait for my block devices to appear). I'm closing this bug. ** Changed in: initramfs-tools (Ubuntu) Status: Unconfirmed = Fix Released -- initramfs does not handle whole-disk raid devices and partitionable arrays https://launchpad.net/bugs/48756 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102410] Re: Feisty Xubuntu LVM over RAID1 won't boot
Hi Joe, thanks for the clarification. Yes, it is the same bug. As Scott requested he'd like a new bug to work on this, so I'll point people over there to this bug. I'm assigning this to the udev package, although you could argue that mdadm or initramfs-tools might be appropriate as well. ** Changed in: udev (Ubuntu) Sourcepackagename: debian-installer = udev Status: Needs Info = Confirmed -- Feisty Xubuntu LVM over RAID1 won't boot https://bugs.launchpad.net/bugs/102410 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75681] Re: boot-time race condition initializing md
Did somebody already report a new bug on this? If not, there are still two other open bugs with the same issue, one of them new: bug #83231 and bug #102410 -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/75681 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102410] Re: Feisty Xubuntu LVM over RAID1 won't boot
Hi, thanks for your bug report. Could you perhaps explain in a little more detail what the system wouldn't boot means? ie. do you get any error messages, at which stage of the boot process does it stop etc. Also, be advised that feisty is currently pretty buggy wrt to booting from raid. Please see bug #75681 and check whether you see the same symptoms. Thanks. ** Changed in: debian-installer (Ubuntu) Status: Unconfirmed = Needs Info -- Feisty Xubuntu LVM over RAID1 won't boot https://bugs.launchpad.net/bugs/102410 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97175] Re: xfce4-session seems to reset xmodmap
Hi Jani, yes, this is on Feisty. I upgraded on Monday (which went fine except that I hit bug #75681, which took me the rest of the day to fix). I noticed the breakage yesterday, investigated a bit and then reported this bug. I'll be testing with a newly created user lest some of my configuration screws things up. I'll report back. Otherwise it's running great. I especially like how I can set mutt as my preferred mail app and have it work seamlessly. Even Thunar's send to mail recipient works as expected. Great work! -- xfce4-session seems to reset xmodmap https://launchpad.net/bugs/97175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97175] Re: xfce4-session seems to reset xmodmap
I just created a new user using useradd -m and performed the test described above. The result is the same, it does not work, so my configuration is probably not at fault. Please let me know if you need more information or if there is anything I can do to help fix this. At this point I don't really know what to look at. My current workaround btw. is to put the xmodmap statement into my .bashrc. Since I always have a shell open anyways, I'm ok with that. Thanks, Oliver -- xfce4-session seems to reset xmodmap https://launchpad.net/bugs/97175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97175] Re: xfce4-session seems to reset xmodmap
sorry, that doesn't help. I tried reverting xfwm4 and xfce4-mcs-manager as well, just for kicks, but it doesn't work either. So, it probably isn't a bug in xfce4-session, but somewhere else. -- xfce4-session seems to reset xmodmap https://launchpad.net/bugs/97175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97175] Re: xfce4-session seems to reset xmodmap
I know a little more now: I straced xfce4-session from the xinitrc. In the output, there was a suspicious call to xkbcomp. So I removed the executable bit from /usr/bin/xkbcomp, and voilà, my .Xmodmap works. I'll try reverting to a previous version of xkb-data and xkb-utils next. -- xfce4-session seems to reset xmodmap https://launchpad.net/bugs/97175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97175] Re: xfce4-session seems to reset xmodmap
ok, the current version of xkbutils is from August 2006, so it was present in Edgy already. And I can't downgrade xkb-data because of dependencies. I'm attaching the strace output for other people to look over. ** Attachment added: strace of xfce4-session started from /etc/xdg/xfce4/xinitrc http://librarian.launchpad.net/7036265/strace-lp97175 -- xfce4-session seems to reset xmodmap https://launchpad.net/bugs/97175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 75681] Re: boot-time race condition initializing md
One more comment: I have tested some other suggested workarround: - removing the mdrun script did not help (the first thing done by this script is to check the presence of the mdadm one and then to exit) I think you must have a newer version than the one I was looking at. He's right though. This bug broke my system after I upgraded to Feisty and I looked at the scripts, too. The check is there. The initramfs-tools version installed here is 0.85eubuntu6 - adding a timeout in /usr/share/initramfs-tools/init works fine for me: 5 seconds are not enough but 8 are OK ;) Hmm. Same here. I added a sleep 3 to the mdadm script and my system now consistently boots. Previously, I got an error message from mdadm that it couldn't find the devices that made up my RAID. Might adding udevsettle somewhere help in this regard? I thought it was meant for just such a purpose? -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97175] xfce4-session seems to reset xmodmap
Public bug reported: Binary package hint: xfce4-session After upgrading to Xubuntu feisty, my $HOME/.Xmodmap does not work anymore, ie. it does not take effect. After some searching I found the place that should read the .Xmodmap in Xubuntu, which is /etc/xdg/xfce4/xinitrc. Adding some strategically placed debug statements (xmodmap -pke /tmp/xmodmap-$stamp) to that script shows that my .Xmodmap actually _is_ read. However, bracketing the call to $xfcesm (ie. xfce4-session) in line 84 with above-mentioned debug statements shows that before xfce4-session is called, the xmodmap looks the way I want it to be, but afterwards (ie. after the session ends), it is reset to defaults. Running xmodmap by hand works as expected. Conclusion: either xfce4-session directly or something called by xfce4-session resets the xmodmap to defaults. Steps to reproduce: - create a ~/.Xmodmap: [ cut here ]-- keycode 0x71 = Mode_switch keycode 0x3A = m M mu [ cut here ]-- Run xmodmap ~/.Xmodmap and press AltGr + m... the µ character should appear. Log out and back in. Press AltGr + m again. Instead of the µ character, a simple m appears. ** Affects: xfce4-session (Ubuntu) Importance: Undecided Status: Unconfirmed -- xfce4-session seems to reset xmodmap https://launchpad.net/bugs/97175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 51136] Re: mail a report of upgraded packages to the root user
You, sir, are a god among men :-) I haven't upgraded to feisty yet, but once I have, I will use this feature for sure and report back. Thank you very much, it's much appreciated. Oliver -- mail a report of upgraded packages to the root user https://launchpad.net/bugs/51136 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62135] Re: Support for Intel 965 (GMA X3000) doesn't work
Hi Dan, everyone, FWIW, my .deb only breaks apt if you try to install the -dev package as well. To make that work, you need a -dev package with the same adjusted version string the other package has (plus a corrected Depends: line). Since I needed exactly that a few days ago (I needed ;-) to compile prboom+), I created that package: http://home.teleos- web.de/obrackmann/libgl1-mesa- dev_6.5.1~20060817-0ubuntu3+local1_i386.deb I successfully compiled prboom with it, and apt doesn't complain. It's the very same binary as before, I just unpacked the package and fixed the version strings, no recompilation or anything. Have fun :-) -- Support for Intel 965 (GMA X3000) doesn't work https://launchpad.net/bugs/62135 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41013] Re: menu item doesn't show up in menu
Hi Jani, it's there twice already: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397594 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405542 -- menu item doesn't show up in menu https://launchpad.net/bugs/41013 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62135] Re: Support for Intel 965 (GMA X3000) doesn't work
OK, I put it back up now. Before installing it, please make sure that libgl-mesa-dev isn't installed, as it seems to cause problems (see above). If it's then still causing problems, I'll remove it again. -- Support for Intel 965 (GMA X3000) doesn't work https://launchpad.net/bugs/62135 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62135] Re: Support for Intel 965 (GMA X3000) doesn't work
Hi! Sorry, I had to remove my package due to space constraints. It's back now: http://home.teleos-web.de/obrackmann/libgl1-mesa-dri_6.5.1~20060817-0ubuntu3+local1_i386.deb I changed the name of this package so it won't be updated unless a newer version is released by the ubuntu folks. -- Support for Intel 965 (GMA X3000) doesn't work https://launchpad.net/bugs/62135 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62135] Re: Support for Intel 965 (GMA X3000) doesn't work
Whoops, that is rather unexpected, as it doesn't do this on my system. Can't imagine why it would do that, except that maybe you're not on Edgy anymore but on Feisty already? Anyway, I'll better remove the package if it's causing trouble for people. Sorry for the inconvenience. -- Support for Intel 965 (GMA X3000) doesn't work https://launchpad.net/bugs/62135 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41013] Re: menu item doesn't show up in menu
Couldn't I just click on Also affects: Distribution... above and then select Debian? That way, I believe Malone would keep track of the bug in the Debian BTS, wouldn't it? I'm asking because I don't really know anything about the finer points of Launchpad. -- menu item doesn't show up in menu https://launchpad.net/bugs/41013 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 51136] Re: mail a report of upgraded packages to the root user
There is a nice shell script (/usr/sbin/apticron) in the apticron package which could be folded into unattended-upgrades. I still don't speak python, though :-( -- mail a report of upgraded packages to the root user https://launchpad.net/bugs/51136 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
