[Bug 1449089] Re: Regression: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 segfaults on Radeon HD 7470/8470
After more research, this turns out to be a bizarre interaction of various things. The culprit is the intersection of this version of compiz and running older kernel versions. As soon as we updated to linux-image-3.13.0-49-generic, the problem went away. So I think it's still the case that something in the latest compiz update, at least on that one specific radeon card, is tickling a bug that was present at least as recently as 3.13.0-44, but went away some time between then and the current version. (I do see some radeon-specific notes in the changelog for the package, for the -45, -46, and -47 releases). (For unrelated reasons, a site-specific script to prune old kernel versions had the side effect, in Trusty, of removing linux-image- generic, due to changed dependencies between trusty and precise. As a result, machines didn't take kernel updates in a timely manner, which is why this bug got noticed, and the failure mode did coincide with the machines taking the latest compiz.) So feel free to close this, unless there's any further info you want. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449089 Title: Regression: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 segfaults on Radeon HD 7470/8470 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1449089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449089] [NEW] Regression: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 segfaults on Radeon HD 7470/8470
Public bug reported: After taking the 20150313 update of Compiz, compiz segfaults on Dell Optiplex 7010 workstations with a Radeon HD 7470/8470 graphics card. I'm going to get try and get more debugging information, but there was not a stack trace in the kernel.log, only a single segfault mention in /var/log/syslog. ** Affects: compiz (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/1449089 Title: Regression: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 segfaults on Radeon HD 7470/8470 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1449089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449089] Re: Regression: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 segfaults on Radeon HD 7470/8470
Unfortunately we disable apport on our public workstations. I will try to reproduce it on a workstation with apport enabled and retrieve a crash file, if there is one. We do not use fglrx; we use the stock radeon (this is on 14.04.2, without the HWE stack), and the problem occurs on machines with kernel versions ranging from 3.13.0-32 to 3.13.0-46. The common denominator is the specific Radeon card, and the 20150313 update of compiz. I'll paste the syslog line shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449089 Title: Regression: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 segfaults on Radeon HD 7470/8470 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1449089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303603] Re: bad-distribution-in-changes-file unstable
OK, the actual problem is that the ubuntu vendor profile (/usr/share/lintian/vendors/ubuntu/main/data/changes-file/known-dists) does not include unstable. That's a bug, it should include it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303603 Title: bad-distribution-in-changes-file unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1303603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355845] [NEW] partman/unmount_active is not preseedable
Public bug reported: The partman/unmount_active question is not preseedable. This is a problem. Due to some other d-i bug introduced in trusty, the mountmedia command is extremely ... insistent, and when we re-install machines in an unattended mode, it finds /dev/sda1 (a /boot partition) and insists on mounting it on /media, even when anna/retriever is set to net-retriever. This causes partman to complain about mounted partitions. I should be able to pre-seed this question, but I can't, because it forces the seen flag to false. It is a bit presumptuous of d-i to think that it knows my installation environment better than I do: these are unattended machines installed over the network, and any mounted partitions should get overwritten. I do understand the desire not to accidentally scribble over installation media, but at the same time, consider letting sysadmins who know what they're doing preseed answers to questions here. If you're concerned, introduce another debconf key partman/disable_all_safety_checks or something that defaults to false. For another example of people getting bitten by this problem, see: http://ubuntuforums.org/showthread.php?t=2215103p=12977473#post12977473 ** Affects: partman-base (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/1355845 Title: partman/unmount_active is not preseedable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1355845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355845] Re: partman/unmount_active is not preseedable
And before someone bothers to point out that partman/filter_mounted is preseedable, that doesn't help. All that does is tell partman not to filter out mounted partitions. So if I set that to false, partman doesn't display the warning, but will attempt to create a partition on a mounted filesystem, which doesn't work. There is absolutely no way to tell partman No, really, there should not be any local block devices mounted. short of forcing things in an early_command, which is a fairly large hammer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355845 Title: partman/unmount_active is not preseedable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1355845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332729] Re: Broken symlink: /etc/apache2/conf-available/drupal7.conf
I also see this in Trusty. Any chance of an SRU? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332729 Title: Broken symlink: /etc/apache2/conf-available/drupal7.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drupal7/+bug/1332729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303603] Re: bad-distribution-in-changes-file unstable
I'm also seeing this on Trusty. The text for bad-distribution-in- changes-file explicitly says that unstable is fine to use, and indeed unstable is in /usr/share/lintian/data/changes-file/known-dists, so there's definitely something wrong here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303603 Title: bad-distribution-in-changes-file unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1303603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1306991] Re: pip stops with ImportError for request-Modul
I am also encountering this in 14.04. I do not have a local copy of the 'requests' package (or in fact any packages other than python-usb). python-pip simply appears to be broken out of the box on 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1306991 Title: pip stops with ImportError for request-Modul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1306991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1339727] [NEW] lightdm xauthority path is wrong
Public bug reported:
The default apparmor 'X' abstraction permits access to
/{,var/}run/lightdm/authority/[0-9]*, ostensibly for the xauthority
file. Except on Trusty, that's not where the xauthority file is. It is
instead in /run/lightdm/$USER, and named xauthority. I have had to
udpated my apparmor configuration, lest apparmor convince Evince of
being a filthy script kiddie, out to corrupt my xauth file.
Please consider adding the following to the 'X' abstraction:
owner /{,var/}run/lightdm/*/xauthority r,
Relevant info:
apparmor:
Installed: 2.8.95~2430-0ubuntu5
Candidate: 2.8.95~2430-0ubuntu5
Version table:
*** 2.8.95~2430-0ubuntu5 0
500 http://mirrors.mit.edu/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
** Affects: apparmor (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/1339727
Title:
lightdm xauthority path is wrong
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1339727/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1062531] Re: apparmor prevents evince from accessing /run/user/
For anyone, like me, who is naive enough to think that it's possible to set XDG_CACHE_HOME or DCONF_PROFILE to values other than the default, note that this fix _only_ allows access to the user profile. If you rename your user profile, you cannot use any apparmor-enabled application that uses dconf. I know there's nothing to be done about this, but I'm leaving this comment here lest anyone else encounter this situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1062531 Title: apparmor prevents evince from accessing /run/user/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1062531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338163] [NEW] unity lock screen provides no way to force-logout a user
Public bug reported: Let me start by saying that I realize that unity's screen locker is not the same thing as gnome-screensaver. That having been said, there are major regressions in functionality with the advent of Trusty. Virtually every site that uses Linux in any sort of public computing areas makes use (or used to, at least) of gnome-screensaver's logout-delay and logout-enabled functionality, which would, after the screen had been locked for a pre-determined amount of time, present a Log Out button that would end the user's session, optionally running a custom command to do so. This is vital, lest people walk away from their workstations, rendering them unusable by others until they are rebooted. unity's lock screen mode provides no way to do this. Right up until the final beta, it was possible to swap out unity's lockscreen mode for gnome-screensaver, but that was removed as well. I wouldn't mind if it was possible to configure the alternate use of a screensaver, but Unity goes out of its way to ensure you can't do this. If there's some magic way to do this, by adding an applet to the panel when in lockscreen mode, or by invoking some D-Bus black magic, I'd be happy to hear about it. But really, removing this level of functionality while simultaneously preventing any workarounds, is a real problem. Steps to reproduce: 1) Log in to a unity session. 2) Lock the screen. 3) Observe that org.gnome.desktop.screensaver gsettings keys are not honored. 4) Examine the com.canonical.unity* schemas and observe there is no way to enable this behavior. ** Affects: unity (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/1338163 Title: unity lock screen provides no way to force-logout a user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1338163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262022] Re: incorrect multi-arch related meta information.
I'm also running into this on Trusty. What needs to happen to get someone to look at the bzr branches and merge request linked in this bug? ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262022 Title: incorrect multi-arch related meta information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1262022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249515] Re: regression with session-cleanup-script triggering without actual logins
I'm also seeing this in Trusty (lightdm 1.10.1-0ubuntu1). At our site, we have a custom greeter using the GIR bindings, and calling .cancel_authentication() causes the session-cleanup script to run. As this is designed to, you know, clean up after a session, it is not idempotent and is not designed to be run without the corresponding session-setup script having run. Obviously we can workaround this, but seeing as how this was a pretty serious regression, is there any hope of this getting fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249515 Title: regression with session-cleanup-script triggering without actual logins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1249515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995543] Re: [precise] .gvfs fuse mount is not functional after logout and subsequent login
Regarding comment #4, I don't think it's ecryptfs that's causing it, because I'm seeing it periodically on an AFS home directory. This suggests that's more likely to be the usual culprit of All UI designers assume that $HOME is on a filesystem that supports sockets and FIFOs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995543 Title: [precise] .gvfs fuse mount is not functional after logout and subsequent login To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/995543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332131] [NEW] avahi-cups-reload Upstart job leads to weird race conditions
Public bug reported: I'll start out by saying that I cannot _consistently_ reproduce this (it is, after all, a race condition), however the fix is trivial and a no- op, so I'm filing the bug anyway. I ran into the following situation on Ubuntu 14.04: After booting, it was often the case that CUPS would not be running. CUPS started just fine if started by hand, and there were no obvious causes of this in the syslog. However, the times when CUPS was not running, I noticed the boot process seemed to be a bit more sluggish than usual. I eventually tracked this down to the avahi-cups-reload job, which unconditionally kicks CUPS once avahi has been started, with no regard for whether CUPS is actually running. As soon as I moved that Upstart job out of the way, the problems vanished. My particular issue stems from the fact that our site also has another init script that attempts to ensure CUPS is running (and restarts it if not), and much of the time, this was happening while avahi-cups-reload was attempting to reload CUPS. This resulted in CUPS eventually failing to restart (because the post-start script in the CUPS job determined CUPS wasn't running, and exited 0.), which Upstart interpreted as success, and therefore assumed that CUPS was in fact running. I realize this is quite a specific problem, and may well be unique to our site, but is there any reason why the the avahi-cups-reload job cannot change its condition from: start on started avahi-daemon to start on (started avahi-daemon and started cups) which also seems to fix the problem for me, by at least ensuring things start in an orderly manner. (There may well be a subtle Upstart bug here too, but this seems like an easy fix.) See also, Launchpad #1251735, where someone else appears to be experiencing a variant of this issue, and is also requesting the same fix. Relevant info: avahi-daemon: Installed: 0.6.31-4ubuntu1 Candidate: 0.6.31-4ubuntu1 Version table: *** 0.6.31-4ubuntu1 0 500 http://mirrors.mit.edu/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status cups-daemon: Installed: 1.7.2-0ubuntu1 Candidate: 1.7.2-0ubuntu1 Version table: *** 1.7.2-0ubuntu1 0 500 http://mirrors.mit.edu/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status upstart: Installed: 1.12.1-0ubuntu4 Candidate: 1.12.1-0ubuntu4 Version table: *** 1.12.1-0ubuntu4 0 500 http://mirrors.mit.edu/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: avahi (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/1332131 Title: avahi-cups-reload Upstart job leads to weird race conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1332131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1328677] [NEW] unity first-run stamp should not be in XDG_CACHE_HOME
Public bug reported: The unity first_run.stamp file should not be in XDG_CACHE_HOME. As it is a _cache_, it can be ephemeral. Rather, it should be in XDG_CONFIG_HOME. Once the keyboard shortcut list, for example, has been presented, I don't need to be told about it again, even if I need to purge my ~/.cache directory. This is a problem at our site, where XDG_CACHE_HOME is stored on a temporary filesystem, to cut down on the tremendous amount of useless network traffic between workstations and the user's file server. As a result, users now have to learn about Unity keyboard shortcuts on every single login. Relevant info: unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://mirrors.mit.edu/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://mirrors.mit.edu/ubuntu/ trusty/main amd64 Packages Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty ** Affects: unity (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/1328677 Title: unity first-run stamp should not be in XDG_CACHE_HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1328677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327384] [NEW] unity-panel-service --lockscreen-mode does not provide a way to disable Switch User
Public bug reported: Unity's screen locking mechanism does not respect any existing gsettings having to do with disabling the Switch User functionality, nor does it provide any way to do it natively. Ideally, it would respect org.gnome.desktop.lockdown, but I realize that's probably never going to happen. I was able to disable the Switch User functionality in the indicator menu by setting com.canonical.indicator.session user-show-menu false in gsettings, but the lockscreen mode of unity-panel-service does not respect this. gnome-screensaver provided a way to do this (org.gnome.desktop.lockdown disable-user-switching true), so this is a major regression for anyone attempting to use Ubuntu in a public computing environment. Steps to reproduce: 1) Start a unity session. 2) gsettings com.canonical.indicator.session user-show-menu false 3) Observe that Switch User disappears from the indicator menu. 4) Lock the screen. 5) Observe that Switch User is present on the indicator menu. 6) Be sad. Workstation Information: Package: unity Version: 7.2.1+14.04.20140513-0ubuntu2 Release:14.04 Codename: trusty ** Affects: unity (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/1327384 Title: unity-panel-service --lockscreen-mode does not provide a way to disable Switch User To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1327384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322260] Re: devscripts-el and emacs cannot be installed in same transaction
** Attachment added: script(1) of the transaction failure. https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1322260/+attachment/4117679/+files/typescript -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322260 Title: devscripts-el and emacs cannot be installed in same transaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1322260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322260] [NEW] devscripts-el and emacs cannot be installed in same transaction
Public bug reported: In Trusty, you cannot install devscripts-el and emacs in the same apt transaction, because devscripts-el's postinst will fail. If emacs is already installed prior to the transaction, it works fine. Steps to reproduce: 1) Install 14.04 (amd64) from the Desktop CD, accepting all the defaults. (This does not install emacs) 2) Run apt-get install devscripts-el 3) See the transaction fail (a typescript is attached) Some things to note: If you install emacsen-common (just emacsen-common, not emacs itself) first, you will see the following errors during the transaction: Preparing to unpack .../apel_10.8+0.20120427-6_all.deb ... ERROR: apel is broken - called emacs-package-install as a new-style add-on, but has no compat file. Preparing to unpack .../debian-el_35.8ubuntu2_all.deb ... ERROR: debian-el is broken - called emacs-package-install as a new-style add-on, but has no compat file. Preparing to unpack .../dpkg-dev-el_35.8ubuntu2_all.deb ... ERROR: dpkg-dev-el is broken - called emacs-package-install as a new-style add-on, but has no compat file. Preparing to unpack .../devscripts-el_35.8ubuntu2_all.deb ... ERROR: devscripts-el is broken - called emacs-package-install as a new-style add-on, but has no compat file. The transaction will still fail as it does above. Despite all the packages above being listed as broken, it's only devscripts-el that can't be installed in the same transaction. All combinations of (dpkg- dev-el, debian-el, apel) and emacs in the same transaction work fine, so it is clear that it's devscripts-el is to blame here. This also seems related to Debian Bug #734531. Additional info: (No matter how much I try, or what I set MaxReports to, I cannot convince apport to generate an error log for this failure.) $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 $ apt-cache policy devscripts-el emacs apel emacs24 emacsen-common devscripts-el: Installed: (none) Candidate: 35.8ubuntu2 Version table: 35.8ubuntu2 0 500 http://mirrors.mit.edu/ubuntu/ trusty/universe amd64 Packages emacs: Installed: (none) Candidate: 45.0ubuntu1 Version table: 45.0ubuntu1 0 500 http://mirrors.mit.edu/ubuntu/ trusty/main amd64 Packages apel: Installed: (none) Candidate: 10.8+0.20120427-6 Version table: 10.8+0.20120427-6 0 500 http://mirrors.mit.edu/ubuntu/ trusty/universe amd64 Packages emacs24: Installed: (none) Candidate: 24.3+1-2ubuntu1 Version table: 24.3+1-2ubuntu1 0 500 http://mirrors.mit.edu/ubuntu/ trusty/main amd64 Packages emacsen-common: Installed: (none) Candidate: 2.0.7 Version table: 2.0.7 0 500 http://mirrors.mit.edu/ubuntu/ trusty/main amd64 Packages ** Affects: apt (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/1322260 Title: devscripts-el and emacs cannot be installed in same transaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1322260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322260] Re: devscripts-el and emacs cannot be installed in same transaction
** Attachment added: script(1) of the failure, with emacsen-common installed before the transaction https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1322260/+attachment/4117680/+files/typescript.with-emacsen-common -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322260 Title: devscripts-el and emacs cannot be installed in same transaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1322260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322260] Re: devscripts-el and emacs cannot be installed in same transaction
** Attachment added: elisp compilation log from original transaction failure https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1322260/+attachment/4117681/+files/elc_gp0Amo.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322260 Title: devscripts-el and emacs cannot be installed in same transaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1322260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322260] Re: devscripts-el and emacs cannot be installed in same transaction
I have attached 3 files: typescript -- a log of the failure as generated by script(1) elc_gp0Amo.log -- the elisp compilation failure that occurred in the aforementioned transaction. typescript.with-emacsen-common -- a log of the failure as generated by script(1), with emacsen-common fully installed and configured prior to initiating the transaction. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322260 Title: devscripts-el and emacs cannot be installed in same transaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1322260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206387] Re: openafs-modules-dkms 1.6.1-1+ubuntu0.2: module FTBFS on 3.8.0
Running a 1.6.5 module against a 1.6.1 userspace seems like a worse idea than taking 1.6.5 as an SRU. Would you accept the backport if we provided additional userland test cases? I'm not interested in starting a debate about the HWE process, but from our perspective, the HWE stack broke a package in universe (albeit one with a small userbase compared to, say, Xorg). From our perspective, any working package is better than a broken package. Because of AFS' small userbase, this SRU should also have far less of an impact than one for, say, Xorg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206387 Title: openafs-modules-dkms 1.6.1-1+ubuntu0.2: module FTBFS on 3.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1206387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1206387] Re: openafs-modules-dkms 1.6.1-1+ubuntu0.2: module FTBFS on 3.8.0
On Dec 2, 2013, at 6:11 PM, Steve Langasek wrote: Only if you use the new point release media, or explicitly opt in to the new enablement stack, do you get the newer kernels. [...] If you have newer hardware that requires the newer enablement stack, it's better to have it available than not, even if that means some out-of-tree modules are not available. If you don't need the new enablement stack, then it's recommended that you use the LTS kernel. Not to get too off topic (and I tried to bring this up in UDS chats when rolling releases/HWE became a thing), but that really only works in homogenous environments, which are not really a thing in academia or other large non-enterprise environments. In our case (and I suspect Russ speaks for a similar environment), we replace our workstations on a rolling 3-year cycle (meaning we get new hardware whenever Dell feels like changing the chipset). So some machines require HWE, others don't. The other challenge is that to the average end user, it is not at all clear that using point release media means an HWE stack, but using original media and upgrading to the point release doesn't. We had a terrible time when the Quantal HWE came out, and whether or not they had working OpenAFS was determined by whether they installed from an ISO image or a net install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206387 Title: openafs-modules-dkms 1.6.1-1+ubuntu0.2: module FTBFS on 3.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1206387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873551] Re: dictionaries-common: debconf corruption
Also, lest this bug get closed when 11.10 is de-supported, I'll note that I can reproduce this with Precise and Quantal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873551 Title: dictionaries-common: debconf corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/873551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873551] Re: dictionaries-common: debconf corruption
I ran into this and believe I have found the root cause. In update-
default-ispell, this logic is wrong:
# Question is empty, but $class elements are installed. Two possibilities.
if ( -x /usr/bin/apt-extracttemplates ){
# apt-utils is installed. Other possibility is debconf database corruption.
Just because apt-utils is _installed_ doesn't mean the templates were parsed
correctly. For example, if dpkg-preconfigure doesn't like the shell that d-i
gives your late_command:
Preconfiguring packages ...
Unknown terminal: bterm
Check the TERM environment variable.
Also make sure that the terminal is defined in the terminfo database.
Alternatively, set the TERMCAP environment variable to the desired termcap
entry.
debconf: whiptail output the above errors, giving up!
So update-default-ispell should not conditionalize on the existence of
apt-extracttemplates to decide whether the database is corrupted or not.
Regardless, update-default-ispell failing in the postinst should not be
a fatal error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873551
Title:
dictionaries-common: debconf corruption
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/873551/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155764] [NEW] Lucid cannot upgrade to Precise if ibus-hangul is installed
Public bug reported: I think this is _related to_, but not necessarily the same as #1010131. Lucid (10.04.4, fully up to date) cannot upgrade to Precise if the ibus- hangul package is installed. Steps to reproduce: - Install 10.04.4 from an ISO (in this case ubuntu-10.04.4-desktop-amd64.iso). - Install ibus-hangul - Run do-release-upgrade and observe that it fails with the error: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: update-manager 1:0.134.11.1 ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21 Uname: Linux 2.6.32-38-generic x86_64 Architecture: amd64 Date: Fri Mar 15 12:50:30 2013 InstallationMedia: Ubuntu 10.04.4 LTS Lucid Lynx - Release amd64 (20120214.2) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade lucid ** Tags added: dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155764 Title: Lucid cannot upgrade to Precise if ibus-hangul is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1155764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015925] Re: openafs: Support quantal’s kernel 3.5
Can this get moved to production any time soon? I understand there's a desire to get openafs 1.6.2 out for security updates, but these are not mutually exclusive. I have a large community of users who can't access their shared file storage if they installed from a CD after Feb 14. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015925 Title: openafs: Support quantal’s kernel 3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1015925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1130419] Re: apt resolver doesn't do sensible things when satisfying a cross-dependency on a virtual package (steam, wine)
I was having a similar problem, in that installing ia32-libs wanted to remove the xorg quantal-lts packages. I just tested with apt 0.8.16~exp12ubuntu10.9 from proposed, and apt-get no longer wants to remove the quantal-lts xorg packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1130419 Title: apt resolver doesn't do sensible things when satisfying a cross- dependency on a virtual package (steam, wine) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1130419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015925] Re: openafs: Support quantal’s kernel 3.5
Using openafs-modules-dkm 1.6.1-1+ubuntu0.1 from precise-proposed, the module now builds correctly for 3.5.0-23-generic (and also for -26-generic, which happens to be in -proposed). openafs-modules-dkms: Installed: 1.6.1-1+ubuntu0.1 Candidate: 1.6.1-1+ubuntu0.1 Version table: *** 1.6.1-1+ubuntu0.1 0 500 http://archive.ubuntu.com/ubuntu/ precise-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 1.6.1-1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages ** 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/1015925 Title: openafs: Support quantal’s kernel 3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1015925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015925] Re: openafs: Support quantal’s kernel 3.5
I can also confirm there is no regression, as it works fine on 3.2.0-38-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015925 Title: openafs: Support quantal’s kernel 3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1015925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1115424] [NEW] latexmk recommends non-existent package, pulls in KDE on Quantal
Public bug reported: The latexmk recommends xpdf-reader | pdf-viewer, among other things. However, xpdf-reader has not existed since Lucid, so APT attempts to satisfy the virtual recommendation on pdf-viewer. In Precise, this was not a problem, because evince-gtk was the first choice for a PDF reader. However, in Quantal, the first choice for this is okular, which attempts pull in all of KDE with it. Please update latexmk to Recommend xpdf | pdf-viewer so that it actually tries an existing concrete package before the virtual one. Steps to reproduce: 1) Install Ubuntu Server 12.10 2) apt-get install latexmk (or texlive-full, which is how I noticed this); watch it pull in all of KDE. References: precise$ apt-get install pdf-viewer Reading package lists... Done Building dependency tree Reading state information... Done Package pdf-viewer is a virtual package provided by: evince-gtk 3.4.0-0ubuntu1.4 okular 4:4.8.5-0ubuntu0.1 evince 3.4.0-0ubuntu1.4 zathura 0.0.8.5-4 xpdf 3.02-21build1 viewpdf.app 1:0.2dfsg1-3.1build2 gv 1:3.7.3-1 epdfview 0.1.8-1build1 quantal$ apt-get install pdf-viewer Reading package lists... Building dependency tree... Reading state information... Package pdf-viewer is a virtual package provided by: okular 4:4.9.4-0ubuntu0.1 zathura 0.1.2-4 xpdf 3.03-9ubuntu5 viewpdf.app 1:0.2dfsg1-4 gv 1:3.7.3-1 evince-gtk 3.6.0-0ubuntu2 epdfview 0.1.8-3ubuntu1 evince 3.6.0-0ubuntu2 ** Affects: latexmk (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/1115424 Title: latexmk recommends non-existent package, pulls in KDE on Quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/latexmk/+bug/1115424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111537] [NEW] lightdm's post-stop sometimes fails
Public bug reported: In our somewhat complicated environment, I've managed to trigger a race condition in which shutting down or rebooting the machine from a (custom) lightdm greeter results in the machine popping up the low graphics mode warning, and never shutting down. The greeter is using the Python GIR bindings to call LightDM.shutdown() and LightDM.restart(), respectively, so I'm fairly certain it's not the greeter's fault. I finally tracked this down to the post-stop script in lightdm's upstart job, namely that initctl emit desktop-shutdown is sometimes returning non-zero. Because all Upstart jobs are run with set -e, lightdm fails, and Upstart then decides that X isn't working and pops up the low-graphics mode warning. Adding the usual || : idiom fixes this, e.g. post-stop script if [ $UPSTART_STOP_EVENTS = runlevel ]; then initctl emit desktop-shutdown || : fi end script I think this is the right thing to do anyway, because if lightdm is being stopped, and for whatever reason, the desktop-shutdown signal is not emitted, there's not a good way to recover from that anyway, so it shouldn't be a fatal failure. This is hard to reproduce (indeed, my steps to reproduce include Try this about 30 times until it fails. While on a single machine, this is not a big deal, distributed over 400 heavily used public machines, it's becoming a real problem), but the fix is easy and a no-op, so I would hope it would be considered anyway. ** Affects: lightdm (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/537 Title: lightdm's post-stop sometimes fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111537] Re: lightdm's post-stop sometimes fails
To clarify, this occurs on both Precise and Quantal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/537 Title: lightdm's post-stop sometimes fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 638211] Re: Thunderbird prefs file references /usr/lib/thunderbird which doesn't exist
As of Thunderbird 16, Thunderbird is apparently back to looking in /usr/lib/thunderbird/defaults/pref and ignoring /etc/thunderbird/pref. (At least, strace'ing can find no attempts by Thunderbird to look in /etc/thunderbird for anything). No mention of this is made in the changelog. This is incredibly annoying from a site configuration standpoint. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/638211 Title: Thunderbird prefs file references /usr/lib/thunderbird which doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/638211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 887879] Re: ubiquity crashed with ValueError in raw_decode(): No JSON object could be decoded
I encountered this earlier in the installation, from a 12.04.1 CD install, and the traceback was in /usr/lib/ubiquity/plugins/ubi- timezone.py, line 173. Based on this and some other bugs, it seems like working network is a hard requirement for Ubiquity, not just a for best results as described on the installation page. It's also possible that ubiquity's network detection code should be more robust. In my (and many academic environments), you get a crippled network connection, redirecting you to a registration page (similar to that found in hotels, free wifi hotspots, etc). So to a naive program, it may look like a real network connection, and all host queries will resolve (to the A record for the registration page), but anything that expects a working network will be disappointed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/887879 Title: ubiquity crashed with ValueError in raw_decode(): No JSON object could be decoded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/887879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046490] [NEW] Saving attachment displays error because of null path
Public bug reported: When attempting to save an attachment in Evolution 3.2.3-0ubuntu6 on a clean install, saving the attachment opens a GtkFileChooser initially browsing the path , which naturally displays an error saying The folder contents could not be displayed: Operation not supported. This is because the key Gconf key /apps/evolution/shell/file_chooser_folder is set to an empty value. If set to the user's homedir (e.g. file:///home/joeuser), or even a sane default (e.g. file:///), this error is not displayed. If the user dismisses the error, and navigates to a valid location in the GtkFileChooser and saves the file, then that location will be saved in the Gconf key and the error won't recur, but this is not good user experience. Steps to reproduce on a clean install of Ubuntu 12.04: 1) Launch Evolution. 2) Configure an e-mail account. 3) Navigate to a message with an attachment 4) Attempt to save the attachment 5) See the error. 6) Run gconftool-2 -s /apps/evolution/shell/file_chooser_folder -t string file://$HOME 7) Repeat steps 1-4, note that no error occurs. ** Affects: evolution (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/1046490 Title: Saving attachment displays error because of null path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1046490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 927168] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() fr
I had the same situation described in comment #12, and changing screen resolution, even down to 1024x768, didn't help much. It did reduce the flashing and black screen, but not enough to make it really usable. So I think that reducing screen resolution makes the problem less bad, not actually better. That having been said, with the latest (as of Aug 29) updates, the black screen and display artifact issues went away, and when Compiz crashes, Unity manages to restart itself after a short delay, so the machine isn't completely unusable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/927168 Title: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/927168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043530] Re: compiz crashed with SIGSEGV in TfpTexture::bindTexImage()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043530 Title: compiz crashed with SIGSEGV in TfpTexture::bindTexImage() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1043530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043530] Re: compiz crashed with SIGSEGV in TfpTexture::bindTexImage()
*** This bug is a duplicate of bug 1043505 *** https://bugs.launchpad.net/bugs/1043505 Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Would that I could, except the other bug is private. #764414 strikes again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043530 Title: compiz crashed with SIGSEGV in TfpTexture::bindTexImage() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1043530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1040780] Re: compiz crashed with SIGSEGV in TfpTexture::enable()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1040780 Title: compiz crashed with SIGSEGV in TfpTexture::enable() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1040780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 160311] Re: Resizing windows by grabbing window borders is difficult
The workaround in the first comment (editing the theme XML) works great. Is there any chance of seeing this in Quantal, or is Metacity considered dead in favor of Compiz as far as Canonical is concerned? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483506] Re: karmic: /afs should be ready before gdm starts
Is this still pending Debian Policy? We just got bitten by this in Precise and are debating whether to implement a workaround and which one to implement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/483506 Title: karmic: /afs should be ready before gdm starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/483506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483506] Re: karmic: /afs should be ready before gdm starts
Er, to be more specific, we're using LightDM, not gdm, but it's essentially the same bug: The login screen appears before the filesystem is ready. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/483506 Title: karmic: /afs should be ready before gdm starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/483506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 975793] Re: 'aptitude safe-upgrade -d -y' enters infinite loop
Can this make it into Qantal and/or get SRU'd for Precise? Or are we unlikely to see this fix until the next import from Debian for 13.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/975793 Title: 'aptitude safe-upgrade -d -y' enters infinite loop To manage notifications about this bug go to: https://bugs.launchpad.net/aptitude/+bug/975793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990490] Re: GIR interface is not following the documentation of the constructor
lightdm and its gir bindings in oneiric-proposed (1.0.6-0ubuntu1.7) work fine for me, both with the JavaScript test case above, and my project's own LightDM greeter written in Python. Can this please get pushed to production? ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990490 Title: GIR interface is not following the documentation of the constructor To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/990490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883112] [NEW] python-cups no longer depends on libcups2
Public bug reported: Somewhere between Natty and Oneiric, python-cups stopped depending on libcups2. This makes the package kind of useless, since all attempts to use it will result in ImportError: libcups.so.2: cannot open shared object file: No such file or directory. Installing libcups2 manually fixes this error. ** Affects: python-cups (Ubuntu) Importance: Undecided Status: New ** Project changed: launchpad = python-cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883112 Title: python-cups no longer depends on libcups2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-cups/+bug/883112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883112] Re: python-cups no longer depends on libcups2
On Natty: $ apt-cache policy python-cups python-cups: Installed: 1.9.54-0ubuntu1 Candidate: 1.9.54-0ubuntu1 Version table: *** 1.9.54-0ubuntu1 0 500 http://mirrors.mit.edu/ubuntu/ natty/main amd64 Packages 100 /var/lib/dpkg/status $ python Python 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53) [GCC 4.5.2] on linux2 Type help, copyright, credits or license for more information. import cups $ apt-cache show python-cups | grep Depends Depends: libc6 (= 2.4), libcups2 (= 1.4.0), python ( 2.8), python (= 2.6), python-support (= 0.90.0) On Oneiric: # apt-cache policy python-cups python-cups: Installed: 1.9.59-0ubuntu0.1 Candidate: 1.9.59-0ubuntu0.1 Version table: *** 1.9.59-0ubuntu0.1 0 500 http://localhost/ubuntu/ oneiric-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.9.58-0ubuntu1 0 500 http://localhost/ubuntu/ oneiric/main amd64 Packages # python Python 2.7.2+ (default, Oct 4 2011, 20:06:09) [GCC 4.6.1] on linux2 Type help, copyright, credits or license for more information. import cups Traceback (most recent call last): File stdin, line 1, in module ImportError: libcups.so.2: cannot open shared object file: No such file or directory # apt-cache show python-cups | grep Depends Depends: python2.7 | python2.6, python (= 2.6), python ( 2.8) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883112 Title: python-cups no longer depends on libcups2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-cups/+bug/883112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818933] Re: Dell 790 fails to reboot without either reboot=bios or acpi=off
reboot=pci does work, and is the workaround we're using. However, it's still a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818933 Title: Dell 790 fails to reboot without either reboot=bios or acpi=off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 826958] Re: lpd://user@host:/queue URLs no longer work
Glad to hear s-c-p has been fixed. However, since CUPS clobbers the URL anyway, I don't think it'll help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/826958 Title: lpd://user@host:/queue URLs no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/826958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 600390] Re: gdm doesn't display contents of /etc/nologin
The bug still occurs with gdm 3.0.4-0ubuntu8 in Oneiric. I'll note that _lightdm_ manages to get this right. ** Changed in: gdm (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/600390 Title: gdm doesn't display contents of /etc/nologin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/600390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 826958] [NEW] lpd://user@host:/queue URLs no longer work
Public bug reported: In Lucid, I could specify a printer with a URI of something like lpd://username@hostname/queuename. This no longer works in Natty (to the point that system-config-printer prevents you from typing the @, and the CUPS web interface just clobbers everything between the protocol and the hostname when reading the URI). This is in direct conflict with http://localhost:631/help/network.html which explicitly says that lpd://user@host/queue URLs are supposed to work. ** Affects: cups (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/826958 Title: lpd://user@host:/queue URLs no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/826958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804671] Re: linux-firmware missing realtek firmware files
Can this SRU move forward? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804671 Title: linux-firmware missing realtek firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/804671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818933] [NEW] Dell 790 fails to reboot without either reboot=bios or acpi=off
Public bug reported: This is pretty much the same thing as #488319 (which happened with a Dell 760) or #115011 (with a Dell 745). Basically, every time Dell comes out with a new workstation, rebooting simply doesn't work when ACPI is enabled. The symptom is that it will sit at [ 1234.56789 ] Restarting system forever until power-cycled. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-10-generic 2.6.38-10.46 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: openafs AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jdreed 2530 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xe156 irq 45' Mixer name : 'Realtek ALC269VB' Components : 'HDA:10ec0269,102804ad,00100100' Controls : 18 Simple ctrls : 12 Date: Sun Jul 31 13:16:55 2011 HibernationDevice: RESUME=UUID=f8c5cd2c-191b-4101-9733-9ffe805e14df IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. OptiPlex 790 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/athena/tcsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-10-generic root=/dev/mapper/athena-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-10-generic N/A linux-backports-modules-2.6.38-10-generic N/A linux-firmware 1.52 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0J3C2F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd04/11/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0J3C2F:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818933 Title: Dell 790 fails to reboot without either reboot=bios or acpi=off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818933] Re: Dell 790 fails to reboot without either reboot=bios or acpi=off
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818933 Title: Dell 790 fails to reboot without either reboot=bios or acpi=off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818933] Re: Dell 790 fails to reboot without either reboot=bios or acpi=off
Scratch that, they need acpi=off. reboot=bios doesn't help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818933 Title: Dell 790 fails to reboot without either reboot=bios or acpi=off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 670629] Re: EULA not shown for Microsoft Fonts
We encountered the same thing Bruno saw in comment #14. It was consistently reproducible on Natty when leaving tasksel blank (that is, only installing standard), but running a postinstall script that, among other things, pulls in fontconfig and ttf-msttcorefonts-installer in the same aptitude transaction (a metapackage which depends on both of those and a ton of other things. The problem is actually a poor interaction between those two packages. Two of my colleagues tracked it down: 1) Both packages are unpacked. Since it's part of ttf-mscorefonts-installer, /usr/share/fonts/truetype/msttcorefonts is created and exists. 2) fontconfig is configured first. fontconfig's postinst helpfully cleans up empty all subdirectories under /usr/share/fonts when it's upgrading from pre-2.4.0-1 (and since sorts earlier, it's triggered on a fresh install) 3) ttf-msttcorefonts-installer is now configured, and attempts to write the README to a nonexistent directory. Arguably, fontconfig's conditional is wrong and should use lt-nl, however msttcorefonts could also fix this by mkdir -p before writing the README file. Bugs will be filed for these issues, but I wanted to leave this comment here in case anyone encounters this in a Google search and wants to know what the hell is going on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/670629 Title: EULA not shown for Microsoft Fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/670629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 724604] Re: gnome-panel 2.32.1-0ubuntu6 forces Unity on gnome-classic session users
This is apparently fixed as of April 11, in that if I create a new local account and select Ubuntu Classic, I essentially get a Lucid panel. However, for accounts that used the previously-broken Ubuntu Classic, I still get appmenu, presumably because the gconf migration path is broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/724604 Title: gnome-panel 2.32.1-0ubuntu6 forces Unity on gnome-classic session users -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 436936] Re: gdm upstart job checks /proc/cmdline for single user mode, won't start on post-boot runlevel change
I tested the new gdm.conf, and confirm that a) GDM doesn't start in recovery mode b) GDM does start if I telinit 2 from a recovery mode shell However, (b) is not particularly helpful, because it still doesn't work if I choose the Resume option from the Recovery Menu. All the Resume option does is exit. From /usr/share/recovery-mode/recovery-menu: if [ $choice = resume ]; then exit fi So it's possible that once this is fixed, a bug should be opened against friendly-recovery to have it run telinit 2 instead of just exit -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. https://bugs.launchpad.net/bugs/436936 Title: gdm upstart job checks /proc/cmdline for single user mode, won't start on post-boot runlevel change -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 724604] Re: gnome-panel 2.32.1-0ubuntu6 forces Unity on gnome-classic session users
This bug is still present as of the latest updates (March 17), and UI freeze is in a week. Can anyone confirm whether this change was by design or not? Because if there's no way to opt-out of Unity on a per- session basis and use the classic (read: Lucid, Maverick) interface, then I have to update a lot of documentation and re-train 6000 or so users between now and April. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/724604 Title: gnome-panel 2.32.1-0ubuntu6 forces Unity on gnome-classic session users -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 724604] [NEW] gnome-panel 2.32.1-0ubuntu6 forces Unity on gnome-classic session users
Public bug reported: Binary package hint: gnome-panel The latest release of gnome-panel in Natty seems to have forced the Unity interface on me while ignoring my session type. When I specify Ubuntu Classic at the login screen, I expect to to see a traditional panel. Instead I get a Unity-style panel, including the Start Menu and the menubar/panel combination. Note: I believe this is a gnome-panel bug that originates from the changes in made in 2.32.1-0ubuntu6, not a gnome-session bug. ** Affects: gnome-panel (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/724604 Title: gnome-panel 2.32.1-0ubuntu6 forces Unity on gnome-classic session users -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 724604] Re: gnome-panel 2.32.1-0ubuntu6 forces Unity on gnome-classic session users
Relevant info: $ lsb_release -sd Ubuntu natty (development branch) $ apt-cache policy gnome-panel gnome-panel: Installed: 1:2.32.1-0ubuntu6 Candidate: 1:2.32.1-0ubuntu6 Version table: *** 1:2.32.1-0ubuntu6 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/724604 Title: gnome-panel 2.32.1-0ubuntu6 forces Unity on gnome-classic session users -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 436936] Re: gdm upstart job checks /proc/cmdline for single user mode, won't start on post-boot runlevel change
This bug is still present in Lucid. It is exacerbated by the fact that recovery mode offers a resume option which is supposed to return the machine to its normal state. However, since recovery mode is single user mode, gdm never starts. It would be great if this was finally fixed in Natty, especially since it's a one line fix. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. https://bugs.launchpad.net/bugs/436936 Title: gdm upstart job checks /proc/cmdline for single user mode, won't start on post-boot runlevel change -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 336932] Re: New windows cause panels to be raised above fullscreen applications (e.g. screensaver)
I see that this was declined for Lucid and Maverick. Should I bother nominating it for Natty? -- New windows cause panels to be raised above fullscreen applications (e.g. screensaver) https://bugs.launchpad.net/bugs/336932 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 638211] [NEW] Thunderbird no longer checks /usr/lib/thunderbird for default preferences
Public bug reported: Binary package hint: thunderbird Thunderbird 3.0.7+build1+nobinonly-0ubuntu0.10.04.1 fails to look in /usr/lib/thunderbird for configuration files. It now only looks in /usr/lib/thunderbird-3.0.7. This is in direct conflict with /etc/thunderbird/pref/thunderbird.js, which says: // You can, with this file and all files present in the // /etc/thunderbird/pref directory, override any preference that is // present in /usr/lib/thunderbird/defaults/pref directory. For our site configuration, we set a new value for general.config.filename, and store that file in /usr/lib/thunderbird. This worked fine in Jaunty and Karmic. However, under Lucid, this causes Thunderbird to unfortunately exit with Failed to read the configuration file, since it's looking for our config file in /usr/lib/thunderbird-3.0.7. If this is the new upstream behavior, that's fine, but then the comments in /etc/thunderbird/pref/thunderbird.js need to be updated to replace this. Additionally, it would be nice if there was some way to programmatically determine the name of that directory that was something other than dpkg-query and sed. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- Thunderbird no longer checks /usr/lib/thunderbird for default preferences https://bugs.launchpad.net/bugs/638211 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 538912] Re: xlinks shouldn't replace Firefox as /etc/alternatives/x-www-browser
I would claim that that means that Firefox is Ubuntu's default browser Indeed, Ubuntu claims this too. See https://help.ubuntu.com/community/WebBrowsers (Yes, I know it's community documentation, but it's help.ubuntu.com, not the wiki) ** Changed in: firefox (Ubuntu) Status: Opinion = Confirmed -- xlinks shouldn't replace Firefox as /etc/alternatives/x-www-browser https://bugs.launchpad.net/bugs/538912 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 484317] Re: GDM allows root logins
In response to #11, I confirm the bug is still present in Lucid. jdr...@adjective-animal:~$ apt-cache policy gdm gdm: Installed: 2.30.2.is.2.30.0-0ubuntu3 Candidate: 2.30.2.is.2.30.0-0ubuntu3 Version table: *** 2.30.2.is.2.30.0-0ubuntu3 0 500 http://ubuntu.media.mit.edu/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 2.30.0-0ubuntu5 0 500 http://ubuntu.media.mit.edu/ubuntu/ lucid/main Packages -- GDM allows root logins https://bugs.launchpad.net/bugs/484317 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 336932] Re: New windows cause panels to be raised above fullscreen applications (e.g. screensaver)
This bug is still present in Lucid. -- New windows cause panels to be raised above fullscreen applications (e.g. screensaver) https://bugs.launchpad.net/bugs/336932 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 600390] [NEW] gdm doesn't display contents of /etc/nologin
Public bug reported: Binary package hint: gdm When logins are disabled by the presence of /etc/nologin, GDM simply responds with Authentication failure after the username is entered. While what it says is technically true, this is a terrible user experience. Ideally, it should display the contents of /etc/nologin. Failing that, it should at least say Logins are disabled. The username list is disabled via gconf (/apps/gdm/simple- greeter/disable_user_list true), so I haven't tested the behavior if the username list is enabled. Steps to reproduce: 1) Create /etc/nologin 2) Type a username at the GDM login screen 3) Observe that it says Authentication failure Relevant info: # lsb_release -sd Ubuntu 10.04 LTS # apt-cache policy gdm gdm: Installed: 2.30.2.is.2.30.0-0ubuntu2 Candidate: 2.30.2.is.2.30.0-0ubuntu2 Version table: *** 2.30.2.is.2.30.0-0ubuntu2 0 500 http://mirrors.mit.edu/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 2.30.0-0ubuntu5 0 500 http://mirrors.mit.edu/ubuntu/ lucid/main Packages ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- gdm doesn't display contents of /etc/nologin https://bugs.launchpad.net/bugs/600390 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 387536] Re: Zenity should ignore markup with a flag
Any text with an ampersand will trigger the bug. $ zenity --info --text 'This has an in it' The following is printed to stderr: (zenity:21569): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1: Character ' ' is not valid at the start of an entity name; the character begins an entity; if this ampersand isn't supposed to be an entity, escape it as amp; And zenity displays its default All updates are complete dialog instead of the text. Ideally, it should be told to ignore Pango markup. Failing that, the man page should explicitly inform users that they need to escape anything that could be interpreted as Pango markup. ** Changed in: zenity (Ubuntu) Status: Incomplete = New -- Zenity should ignore markup with a flag https://bugs.launchpad.net/bugs/387536 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 387536] Re: Zenity should ignore markup with a flag
And before anyone asks, yes this is still present in Lucid. -- Zenity should ignore markup with a flag https://bugs.launchpad.net/bugs/387536 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 569212] [NEW] zephyr-clients manpages have incorrect paths
Public bug reported: Binary package hint: zephyr-clients The following manpages reference incorrect paths: zwgc(1), zctl(1), zmailnotify(1), xzwrite(1), and zhm(8) zwgc(1) claims that zwgc_resources and zwgc.desc are in /usr/athena/share/zephyr. They are now in /etc/zephyr. jdr...@infinite-loop:~$ dpkg -L zephyr-clients | egrep zwgc.desc|zwgc_resources /etc/zephyr/zwgc.desc /etc/zephyr/zwgc_resources zctl(1) claims that zephyr.vars is in /etc/athena. It is in /etc/zephyr jdr...@infinite-loop:~$ dpkg -L zephyr-clients | grep zephyr.vars /etc/zephyr/zephyr.vars zmailnotify(1) claims that zwgc.desc is in /usr/athena/lib/zephyr. As noted above, it's in /etc/zephyr xzwrite(1) claims that XZwrite and xzwrite.bitmap are in /usr/athena/lib/zephyr. They are in /etc/zephyr: jdr...@infinite-loop:~$ dpkg -L zephyr-clients | egrep XZwrite|xzwrite.bitmap /etc/zephyr/XZwrite /etc/zephyr/xzwrite.bitmap zhm(8) claims that zhm is in /etc/athena. It is in /usr/sbin: jdr...@infinite-loop:~$ dpkg -L zephyr-clients | grep zhm /usr/sbin/zhm Relevant Information: jdr...@infinite-loop:~$ lsb_release -sd Ubuntu 9.04 jdr...@infinite-loop:~$ apt-cache policy zephyr-clients zephyr-clients: Installed: 2.1.20070719.SNAPSHOT-3 Candidate: 2.1.20070719.SNAPSHOT-3 Version table: *** 2.1.20070719.SNAPSHOT-3 0 500 http://ubuntu.media.mit.edu jaunty/universe Packages 100 /var/lib/dpkg/status ** Affects: zephyr (Ubuntu) Importance: Undecided Status: New -- zephyr-clients manpages have incorrect paths https://bugs.launchpad.net/bugs/569212 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 569212] Re: zephyr-clients manpages have incorrect paths
This is reported upstream as https://zephyr.1ts.org/ticket/64. There isn't a corresponding Debian bug, but there probably should be. ** Bug watch added: zephyr.1ts.org/ #64 https://zephyr.1ts.org/ticket/64 -- zephyr-clients manpages have incorrect paths https://bugs.launchpad.net/bugs/569212 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
