My guess is that the Line 34 is related to my .bash_profile, which has
this on line 34:
if [ `uname -s` == Darwin ]
then
# On MacOS X, the $PATH is set in .MacOSX/environment.plist
export PATH=$PATH:/opt/local/bin
# Path to emacsclient.
export
On Jul 03, 2012, at 11:10 AM, Philippe Poilbarbe wrote:
/usr/sbin/lightdm-session is a script executed with /bin/sh (see shebang line
#!/bin/sh). It sources $HOME/.profile (and some others), not
$HOME/.bash_profile.
This does make it rather impossible to set up the environment both for the
** Changed in: feedparser (Ubuntu Quantal)
Assignee: (unassigned) = Barry Warsaw (barry)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1056820
Title:
feedparser ftbfs
Unfortunately, libxml2-2.9.0+dfsg1-2 from experimental does not build on
Quantal (see attached log). Also, libxml2 has a lot of reverse-depends
so the new version of that will need an FFe and I'd feel more confident
if we did a test rebuild of its rdeps to make sure the new version
doesn't break
** Attachment added: libxml2_2.9.0+dfsg1-2_amd64.build
https://bugs.launchpad.net/ubuntu/+source/feedparser/+bug/1056820/+attachment/3349050/+files/libxml2_2.9.0%2Bdfsg1-2_amd64.build
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Running the feedparser test suite seems like an all-around losing
proposition. Even upstream git head doesn't complete its testsuite
successfully for me on Python 2.7. :( Even upgrading to sid's 5.1.2
package produces tons of mysterious failures. We've been here before
with this package too.
These test failures seem to be caused by chardet... again. If you
install 5.1.2 into a (Python 2) virtualenv without chardet, all but one
of the tests passes. Run in an environment with python-chardet and the
test suite gets tons of failures. We hit similar problems with Python 3
and removed
Hahahahahahah. This traceback, while annoying does not cause the test
suite to fail. So removing python-chardet, python-libxml2, and python-
utidylib fixes the FTBFS with 5.1.2.
Traceback (most recent call last):
File /usr/lib/python2.7/SocketServer.py, line 295, in
_handle_request_noblock
Note that this means we can drop two of our patches, specifically
broken-tests.patch and CVE-2012-2921.patch, both of which have been
applied upstream by 5.1.2.
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-2921
--
You received this bug notification because you are a member of
From the NEWS file, differences since 5.1:
5.1.2 - May 3, 2012
* Minor changes to the documentation
* Strip potentially dangerous ENTITY declarations in encoded feeds
* feedparser will now try to continue parsing despite compression errors
* Fix issue 321 a little more (the
** No longer affects: libxml2 (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1056820
Title:
feedparser ftbfs in quantal, test suite failures
Status in “feedparser” package
** Changed in: unity (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/751858
Title:
Unity messes up geometry
Sorry, I wasn't clear. The background looks like the normal login
screen, and there are menu items, ubuntu logo, and login box in the
normal places, but just so small that they cannot be normal interacted
with.
--
You received this bug notification because you are a member of Desktop
Packages,
Seems fine on my Mac running natively with ATI hardware. Note that I do
have 3d acceleration turned on for the VMware host. Maybe this is
fallout from the X.org transition?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in
Public bug reported:
After today's Quantal update, the login screen is unusable. After a
reboot, I get what looks like it might be the normal login screen, and I
get the bongos, but then almost immediately the screen turns into the
old-style purple-and-orange background and all the fonts are
See also LP: #1039157
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1039097
Title:
super tiny font and incorrect background
Status in “lightdm” package in Ubuntu:
New
Bug
** Changed in: gwibber
Status: Triaged = In Progress
** Branch linked: lp:~barry/gwibber/py3
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/1042344
Title:
[FFE] Gwibber
On Sep 10, 2012, at 11:23 AM, Iain Lane wrote:
Is this actually ready now?
Sorry, no. We've decided to postpone this until 13.10. I removed the FFe
from the bug description, but I don't think I can unsubscribe ~ubuntu-release
** Summary changed:
- [FFE] Gwibber python 3 port
+ Gwibber
On Oct 06, 2012, at 09:20 AM, Andrea Corbellini wrote:
Hey there. Thanks for taking time reporting this bug. As you know,
Quantal and Unity have changed much since when you reported this bug.
Are you still experiencing the issue?
Nope. Ultimately the problem was due to the graphics kernel
There are quite a few reverse-depends. While from the description, it
doesn't seem like this new release would break any of those, we are
quite close to the release, so this is a risky sync. Does this fix
specific bugs in Ubuntu? Would it be better to upload this to quantal-
proposed or wait
On May 31, 2012, at 03:25 AM, hamish wrote:
your line numbers are off by +3 (going from 53:
/home/barry/.bash_profile: source: not found), but still no a == b
bashisms or unquoted enviro variables that I can see...
which version is this?
I'm still seeing this in quantal. From the top of my
Final freeze is now in effect.
https://wiki.ubuntu.com/FinalFreeze
Please prepare this update for SRU
https://wiki.ubuntu.com/StableReleaseUpdates
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-base in Ubuntu.
Quick follow up: a completely fresh Raring install from 64bit iso
downloaded 2 days ago stalls as described on the first reboot from
install. After that, 10 straight reboots and no stall. `sudo apt-get
dist-upgrade` and reboot 10 times, no stalls.
So for now, let's ignore the first stall after
A process of elimination, seems to indicate it's landscape related. By
going through my new machine setup https://wiki.ubuntu.com/BarryWarsaw
and doing multiple reboots with disk snapshotting, it seems like things
are fine until I install Landscape and register the machine with the
Landscape
Public bug reported:
I've just noticed this in recent Raring updates: gnome-terminal is now
eating control-space keystrikes (C-space).
This is a pretty important keybinding when running various editors such
as emacs -nw or jed in a terminal window. I've looked through the
keyboard shortcuts and
Actually, I don't think this is a regression in gnome-terminal since
running jed in an xterm exhibits the same problem.
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received
** Summary changed:
- gnome-terminal eats control-space
+ Unity (?) eats control-space
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1089355
Title:
Unity (?) eats
Public bug reported:
Running s-c with --measure-startup-time requires the gi.repository.GLib
module.
** Affects: software-center (Ubuntu)
Importance: High
Assignee: Barry Warsaw (barry)
Status: In Progress
** Changed in: software-center (Ubuntu)
Assignee: (unassigned
** Branch unlinked: lp:~barry/software-center/lp1110470
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1100408
Title:
Update Depends for new oneconf packaging
Status in
I like the idea of a compat package. Let me see if I can whip something
up.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
Status in
As Rachel observes in the bug description, just adding a PIL.pth file
won't be enough. I do not want to modify Pillow to use non-relative
imports.
What I think might work is a PILcompat.pth file and a PILcompat Python
package. Inside there would be files like Image.py that do
from PIL import
Well, something like the linked branch is the idea. It works for
`import Image` (Python 2 only of course), but if there are other modules
that typically get imported from the top-level namespace instead of as a
subpackage of PIL, they'll have to be added individually. I couldn't
figure out a
On Feb 06, 2013, at 02:04 PM, Matthias Klose wrote:
just Image doesn't seem to be enough. What about starting with the
modules listed in the PIL handbook?
http://pythonware.com/library/pil/handbook/ (Part II, Module Reference)
The Image Module
The ImageChops Module
The ImageColor Module
The
On Feb 08, 2013, at 12:25 PM, Alex Clark wrote:
Is fixing the broken imports an option?
Probably only with enough volunteers to fix upstream and/or provide patches to
the Debian and/or Ubuntu packages. It's always better to fix things as far
upstream as possible of course.
If not, then yeah
This bug has magically gone away. I'll mark it invalid.
** Changed in: gnome-terminal (Ubuntu)
Status: New = Invalid
** Changed in: ubuntu-meta (Ubuntu)
Status: New = Invalid
** Changed in: unity (Ubuntu)
Status: New = Invalid
--
You received this bug notification
** Changed in: software-center (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1100408
Title:
Update Depends for new oneconf
** Changed in: gwibber
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/1042344
Title:
Gwibber python 3 port
Status in Gwibber:
Fix
After chatting w/slangasek and jodh on IRC, they feel it could be an X
or lightdm bug. Possibly LP: #969489 related. I'm going to attach
some logs.
** Changed in: linux (Ubuntu)
Status: Incomplete = New
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
** Attachment added: log file while in stalled state
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1061149/+attachment/3452310/+files/x-0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
** Attachment added: Xorg log while in stalled state
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1061149/+attachment/3452307/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
** Attachment added: x-0-greeter.log
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1061149/+attachment/3452311/+files/x-0-greeter.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
** Attachment added: lightdm.log while in stalled state
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1061149/+attachment/3452308/+files/lightdm.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Hi Bryce, thanks very much for looking at this.
On Aug 30, 2011, at 01:56 AM, Bryce Harrington wrote:
Your xorg.conf only specifies glx, but that's loaded by default now.
You should be able to entirely delete your xorg.conf with no impact to
X. (In fact we ship without xorg.conf and recommend
On Aug 30, 2011, at 01:32 AM, Bryce Harrington wrote:
It sounds sort of like gnome-settings-daemon is not capturing the
settings properly, so your system is defaulting to 10 minutes. I notice
this in your dmesg which hints perhaps gsd is dying (coincidentally in
some power module):
barry micahg: how truly odd. bug 788514 has a task for python-debian, which
is marked fixed released, and i have a branch sitting here with the
necessary changes. i usually never manually flip the fix released
status, so i'm not sure what's going on. maybe i never
Public bug reported:
Hi Martin,
When you uploaded gtimelog 0.6.0, you changed its Depends to
gir1.2-pango-1.0 (= 1.29.3+git20110916) but only 1.29.3-0ubuntu3 is in
oneiric. I have a gtimelog 0.6.1 src package (with your upstream
fixes... thanks!) ready to go, but I'm not sure what to do about
Thanks Martin. I'll upload gtimelog 0.6.1, so that when pango gets
unfrozen, we'll actually have a working app. :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/855076
Title:
Okay, I've confirmed that gtimelog 0.7.0 (which sets gi as the default) crashes
with gir1.2-pango-1.0 1.29.3-0ubuntu3, but works fine with the ppa version,
modulo bug 849732 which is a separate issue.
I'll go ahead and release 0.7.0 and upload it so that when pango gets uploaded,
the new
Yep, affects Computer Janitor:
https://bugs.launchpad.net/ubuntu/+source/computer-janitor/+bug/806574
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/886359
Title:
Missing feature
/usr/bin/env is a perfectly good solution for *development* branches of
packages, but very definitely not for deployed production versions of
applications, for exactly the reasons described in this bug report.
Meaning: if you are developing a Python application, by all means use
/usr/bin/env in
Public bug reported:
Normally, you should be able to start multiple versions of Firefox with
a different profile, even with an existing firefox is running, using the
following command:
$ firefox -ProfileManager
(i.e. see firefox -h for details)
However this does not work when a firefox is
On Dec 08, 2011, at 08:28 PM, Chris Coulson wrote:
Hi :)
You also need to use -no-remote if there is already a running
instance. This is documented in the manpage:
-ProfileManager
Start the profilemanager. Use this to choose the profile you
would like to run firefox with.
As for python-debian, I'm inclined not to try a sync at this point in
the Oneiric cycle. 0.1.21 has some new features and API changes which
worry me a bit, and does not include the Ubuntu deltas to support lzma.
I'm going to give it a shot to just convert our package to dh_python2
and leave the
This has happened to me also in precise with Gnome Terminal. In
oneiric, I used to be able to get two 80-wide Terminals next to each
other with Ubuntu Mono 14 in a 1600x1200 screen. In precise, these
overlap now and I have to bump them down to UM 13, which isn't as
readable and also feels like
After chatting with Alex on IRC, this is definitely the same bug, so
screen shots probably aren't necessary. Unfortunately, neither of us
understand how to test out the workaround in comment #9 :/ Seems like
upstream doesn't think this is a regression.
--
You received this bug notification
Private bug reported:
Just logged in after an apt-get update.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libevolution 3.2.3-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
** Attachment added: lightdm-session
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/962270/+attachment/2961179/+files/lightdm-session
** Changed in: lightdm (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Desktop
Packages,
On Mar 29, 2012, at 07:02 PM, Sebastien Bacher wrote:
weird, that doesn't really make sense to me, l34 is XKB_IN_USE=yes,
how can that hit the error in the summary?
Exactly! :)
I can't explain it either.
-Barry
--
You received this bug notification because you are a member of Desktop
On Jan 11, 2012, at 09:12 PM, Zoubidoo wrote:
Fixed? Not for me:
$ computer-janitor find
ERROR:dbus.proxies:Introspect error on :1.368:/:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied:
Rejected send message, 1 matched rules; type=method_call, sender=:1.371
(uid=1000
Public bug reported:
When sitting at the login screen, I have to mute the audio because
otherwise when the machine boots I get the highly disruptive bongos.
However, if I then log in and re-enable the audio in my session, when I
log out, the audio is re-enabled on the login screen, and I'll get
Public bug reported:
I guess my .bash_profile isn't being executed with bash? I get this in
the first few lines of my .xsession-errors file:
/usr/sbin/lightdm-session: 34: [: Linux: unexpected operator
/usr/sbin/lightdm-session: 53: /home/barry/.bash_profile: source: not found
** Affects:
Setting back to New in compiz because the height problem still exists.
Fortunately, the other geometry problems have been solved.
** Changed in: compiz (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
It appears to be fixed in the latest update.
** Changed in: gwibber (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/983470
Title:
Text no
Public bug reported:
% head -n 1 /usr/bin/gwibber-accounts
#!/usr/bin/env python
This is destined to break. It is never a good idea for production code
to use /usr/bin/env. Instead, it should use #!/usr/bin/python just like
gwibber-service does.
** Affects: gwibber
Importance: Undecided
Note that it's okay for the *development* branch to use /usr/bin/env, in
fact, it's preferable so that it's easier to develop against alternative
Python's. Once deployed though, it must use /usr/bin/python.
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
% head -n 1 /usr/bin/gtk-builder-convert
#!/usr/bin/env python
While this is fine, preferable even for the development version of the
script, it is destined to break in the deployed production version of
the script. The header must use #!/usr/bin/python instead.
**
Public bug reported:
% head -n 1 /usr/bin/gdbus-codegen
#!/usr/bin/env python
While it's fine, preferable in fact for the development version of
gdbus-codegen to have #! /usr/bin/env python, it is not correct for the
deployed production version to use it. That's just asking for breakage.
Public bug reported:
% head -n 1 /usr/bin/invest-chart
#!/usr/bin/env python
While it's fine, preferable even for the development version of invest-
chart to use the above #! line, it is asking for trouble in the deployed
production version. When installed, invest-chart should use
This probably provides the best rationale for why I consider this a bug:
https://lists.debian.org/debian-python/2011/03/msg00013.html
Scott K also quotes Debian Python policy here:
https://lists.debian.org/debian-python/2011/03/msg00015.html
(which indicates that while not prohibited, D-P
By process of elimination (i.e. bisecting apt-get installs of all the
dist-upgrade upgrading packages), I've narrowed this down to the
following binary packages: libglib2.0-0 libglib2.0-bin libglib2.0-dev
all part of the glib2.0 source package, version 2.41.2-1. In all
likelihood it's the
This seems to be the best I can manage for a traceback. Note that I had
to manually hack /usr/lib/debug/usr/bin/mono-sgen-gdb.py to be Python 3
compatible (will file a separate bug on that).
There are still some undefined symbols, but I can't suss out which
packages are missing, and apport does
Public bug reported:
While trying to get gdb stacktrace information for the crash in LP:
#1344386 I ran into a problem with the script in summary. I had to
manually hack this file to get gdb to not produce SyntaxErrors. Mostly
it's just putting
from __future__ import print_function
at the top
This has only been a cosmetic bug for me for a long time. However, I
took the ping as an opportunity to try a few of the things in comment
#6. Changing managed=false to managed=true was the only change
necessary to fix the icon in Utopic. I consider this bug fixed.
** Changed in:
** Changed in: network-manager (Ubuntu)
Status: Fix Released = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/751939
Title:
Wired-only machine has empty volcano
I take that back. Setting managed=true breaks the networking.
Even though I get the proper icon and all the network connection
information appears to be correct (both as displayed by ifconfig and
through the NM u/i), I cannot ping or connect to any service outside my
LAN. Gateway and DNS
I'm patch piloting today so I'll give this a look.
** Changed in: emacs24 (Ubuntu)
Status: Confirmed = In Progress
** Changed in: emacs24 (Ubuntu)
Assignee: (unassigned) = Barry Warsaw (barry)
** Changed in: emacs24 (Ubuntu)
Importance: Undecided = High
** Changed in: emacs24
So far, looks pretty good (mostly just testing the build on vivid).
I'll soon have a vivid VM to test the installed debs.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1387323
Title:
Some testing on vivid looks good. This will likely get stuck in
proposed until imagemagick 8:6.8.9.9-2 gets promoted.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1387323
Title:
Public bug reported:
After upgrading to Vivid, Terminal no longer accepts any Alt menu
shortcuts.
To reproduce, start up Terminal and give it the focus. When you hit and
hold Alt, you'll see the application menu show up in the global menu
bar, but none of the menus or items have underlines, and
On Nov 11, 2014, at 09:22 AM, Iain Lane wrote:
Is Edit→Preferences→“Enable mnemonics” checked or unchecked?
It wasn't, and is now, and the menu bar underlines are back. Is this a new
option? (It wasn't anything I explicitly changed when upgrading from utopic
to vivid.)
Still one small nit:
On Nov 11, 2014, at 03:43 PM, Iain Lane wrote:
Don't think so - this version has a migration from GConf to GSettings
for settings storage so the value may have been lost for you there. If
so, that'd be a bug. I'll make a note to try this out.
That could be it. I'd need to set up a utopic vm to
Public bug reported:
Over in LP: #1391337 I reported a problem on vivid where Terminal wasn't
displaying its menu bar underlines when you hold down Alt. This was
perhaps caused by a problem in the switch from gconf to gsettings.
I've turned on Terminal-Preferences-General-Enable mnemonics
Now
Public bug reported:
I don't know whether this is a unity bug or elsewhere, but I'm noticing
this problem after upgrading from utopic to vivid.
On your desktop, go to System Settings - Brightness and Lock and set
the turn screen off time to 1 hour. Wait 10 minutes without using
your desktop,
apt-mark lightdm hold apt-get dist-upgrade reboot
Indeed, logins are fine.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
Hmm, as 1.13.0-0ubuntu1 just showed up in vivid, it broke my login in
the follow way. Note that I always try devel channel updates in a VM
with a snapshotted disk so I'm able to revert and do some further
investigating. Looking at the dist-upgrade packages, I suspect the
lightdm changes are
pay-service crashed, leaving a core file and the following in
.xsesssion.old. Not sure if this is related.
upstart: pay-service main process (6149) killed by ABRT signal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
For now I'll keep the hold on lightdm, but if Robert or someone else
wants to debug in real-time, ping me on irc.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error
Hi Gunnar.
On Nov 14, 2014, at 07:07 PM, Gunnar Hjalmarsson wrote:
It has always been using Bourne shell, so source is not understood.
You have obliviously been running your system without the configuration
in those other shell files.
Sure, it's entirely possibly that my login has been silently
On Nov 14, 2014, at 08:15 PM, Gunnar Hjalmarsson wrote:
Being thrown back indicates a syntax error.
Are those errors logged anywhere permanently?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
On Nov 14, 2014, at 09:59 PM, Gunnar Hjalmarsson wrote:
I don't know. Syntax errors directly in e.g. ~/.profile or /etc/profile
are logged in ~/.xsession-errors both with the latest lightdm version
and with previous versions, but I don't know whether syntax errors in
files which are sourced from
On Nov 14, 2014, at 11:38 PM, Gunnar Hjalmarsson wrote:
Right now I don't know how to best deal with this issue. Any advice
appreciated.
Probably use tee(1) to get the output both into the temp file and
~/.xsession-errors.
--
You received this bug notification because you are a member of
This bug was fixed in the package libidl - 0.8.14-0.4
---
libidl (0.8.14-0.4) unstable; urgency=medium
* Non-maintainer upload.
* Run dh-autoreconf to update config.{sub,guess} and
{libtool,aclocal}.m4, necessary for some new ports. Thanks
Brahadambal Srinivasan.
I tested a straight-up sid version build on utopic amd64 and i386.
Built and installed without a hitch. I'm patch piloting so I'll
syncpackage it.
** Changed in: libidl (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Desktop
On Nov 18, 2014, at 02:41 PM, Martin Pitt wrote:
Bash's input redirection simply is way more powerful. Granted, bash
takes a tad longer to start up, but any tee or other external program
which you call in addition will probably hurt performance just as much.
Purely selfishly, switching back to
Public bug reported:
gnome-do and Xorg/unity/desktop seem to be incompatible on a fresh
install of either utopic or vivid. This is either tied to 1080p
(1920x1080) or a fresh install of either version. Details as I know
them are provided here.
I have a brand new machine which is running 1080p
** Also affects: gnome-do (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1396232
Title:
Xorg freeze
Status in “gnome-do” package in
Public bug reported:
dist-upgrade on utopic caused this error
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: blt-dev (not installed)
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
ApportVersion: 2.14.4-0ubuntu1
Architecture: amd64
Date:
** Changed in: oneconf (Ubuntu)
Assignee: Barry Warsaw (barry) = (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to oneconf in Ubuntu.
https://bugs.launchpad.net/bugs/1165104
Title:
oneconf is only showing the pc you
On Apr 30, 2013, at 06:59 PM, Jan D wrote:
Still affects me:
Traceback (most recent call last):
File /usr/bin/phatch, line 16, in module
main(config_paths, app_file = __file__)
File /usr/share/phatch/phatch/app.py, line 203, in main
from core.settings import create_settings
File
This is probably what's causing pycurl to crash in LP: #1163609
** Changed in: curl (Ubuntu)
Assignee: (unassigned) = Barry Warsaw (barry)
** Changed in: curl (Ubuntu)
Status: Triaged = In Progress
** Changed in: curl (Ubuntu)
Importance: Medium = High
** Changed in: curl
1 - 100 of 258 matches
Mail list logo
