gnome-volume-control is vastly improved in Jaunty. The Volume Control
Preferences menu now lists whether each 'track' pertains to Playback,
Recording, Switches, or Options.
The Alsa mixer still has too many options in the Preferences menu for my
on-board Intel audio hardware (see below). See the
I was wrong. Not only is this not fixed, it is not even consistent in
Hardy.
- Checking and unchecking various checkboxes in the Volume Control
Preferences dialog causes additional sliders to appear in the Playback,
Recording and Options tabs somewhat randomly. For example, after some
fiddling
ethanay: I was the OP. With the same hardware as before, under Hardy
(gnome-volume-control 2.22.0, alsa 1.0.16-0ubuntu4):
- I now see only one Input Source box in the Options tab (even though the
Preferences box contains three checked Input Source checkboxes).
- The same is true for the Capture
This has been fixed since Hardy. Closing.
** Changed in: gnome-media (Ubuntu)
Status: New = Fix Released
--
[Gutsy] Usability problems in gnome-volume-control
https://bugs.launchpad.net/bugs/138989
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Daniel Chen, please justify marking this bug report as invalid. I
believe that, at the very least, texlive-latex-recommended should depend
on texlive-latex-base, to prevent a user from ever seeing this error.
** Changed in: texlive-base (Ubuntu)
Status: Invalid = New
--
[Feisty] mathpazo
Great, then this bug was apparently fixed in the Feisty development
cycle. Marking as fix released.
** Changed in: texlive-base (Ubuntu)
Status: New = Fix Released
--
[Feisty] mathpazo style file is missing from texlive-latex-recommended
https://bugs.launchpad.net/bugs/93809
You received
I believe this issue has been resolved in upstream kernels for about two
years. I no longer use Ubuntu, or that iPod, or any Firewire devices, so
I'm afraid I can't easily check.
--
Ejecting firewire HD (iPod) freezes kernel
https://bugs.launchpad.net/bugs/52943
You received this bug
Resolved in 2.6.24-16.
** Changed in: linux-meta (Ubuntu)
Status: New = Fix Released
--
[Hardy] Resume from suspend -- regression since 2.6.24-14
https://bugs.launchpad.net/bugs/215552
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: linux-image
My Asus desktop (Intel Core 2, Intel 965G integrated graphics) has
resumed reliably from suspend in previous versions of Ubuntu and
throughout the Hardy development series. Since the latest kernel update,
2.6.24-15, my machine has been unable
** Attachment added: /var/log/messages output while resuming (unsuccessfully)
from suspend
http://launchpadlibrarian.net/13352192/resume-failure-2.6.22-15.txt
--
[Hardy] Resume from suspend -- regression since 2.6.24-14
https://bugs.launchpad.net/bugs/215552
You received this bug
** Attachment added: Output of lspci -vv
http://launchpadlibrarian.net/13352225/lspci-vv.txt
--
[Hardy] Resume from suspend -- regression since 2.6.24-14
https://bugs.launchpad.net/bugs/215552
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I no longer use mutt. This was a one-off segfault; my stack trace should
have been routed to the mutt developers in October 2006, when I reported
it. It's probably useless to them now, over a year later. Is the Ubuntu
bug tracking system seriously broken, or just seriously under-staffed?
Thanks
I can't reproduce this bug after restarting the machine. It may have
been caused by an upgrade of some library dependencies of GNUcash (Gtk?
X?). I'll re-open the bug if I can reproduce it.
** Changed in: gnucash (Ubuntu)
Status: New = Invalid
--
[Hardy] gnucash-bin crashed with signal 5
Public bug reported:
Binary package hint: mozilla-thunderbird
Currently the Gnome Applications|Internet menu entry for Thunderbird is
Mozilla Thunderbird Mail/News, whereas the entry for Firefox is
Firefox Web Browser. I suggest that the word Mozilla be removed from
the menu entry for
The bug was, it seems, accidentally marked invalid for compiz, when it
should only be invalid for gnome-screensaver.
** Changed in: compiz (Ubuntu)
Status: Invalid = Confirmed
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You
On Mon, 2008-02-04 at 06:59 +, Ted Gould wrote:
No, I marked it invalid because it doesn't make sense that there is
something gnome-screensaver could do would crash compiz. Even if there
was, that's a bug with compiz not gnome-screensaver. They're at the
wrong places in the stack to
As Ted Gould points out, this seems to be a bug with compiz or X, not
gnome-screensaver.
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed = Invalid
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug
Public bug reported:
Binary package hint: gnucash
I am using Ubuntu Hardy amd64, gnucash 2.2.3-1ubuntu2.
I started typing into the description field in the ledger, hit the Home
key, and continued adding to the description from the front. A few
letters in, the autosave feature sprang into life,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/11750693/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/11750695/Disassembly.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/11750696/ProcMaps.txt
** Attachment
Ted, have you really marked a segfault bug with 22 duplicates as
invalid because you personally have not experienced it on your
particular hardware?
--
compiz.real crashed with SIGSEGV when attempting to unlock screen
https://bugs.launchpad.net/bugs/131679
You received this bug notification
I also get a SIGSEGV on Hardy amd64 when resuming from suspend with an
Intel G965 graphics card. I presume it's the same bug. My stack trace
is:
Stacktrace:
#0 0x7f25ae818f33 in ?? () from /usr/lib/compiz/libworkarounds.so
#1 0x7f25ae819dfa in ?? () from
I am seeing videos with dodgy color maps too in Gutsy AMD64, but I have
an Intel G965 graphics chipset. My videos come out mostly green and
black, with patches of purple. Restarting the PC seems to fix the
problem (but I need to verify this properly). I am wondering if the bug
is triggered by X
Just to confirm: Gutsy's kernel is unaffected by this bug.
--
[Feisty] Kernel timer losing clock ticks on amd64
https://bugs.launchpad.net/bugs/102383
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Great work, TJ! I can verify that your package resolves the SIGSEGV on
my amd64 machine running Gutsy.
--
nm-applet crashed with SIGSEGV in gtk_combo_box_set_model
https://bugs.launchpad.net/bugs/124336
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
*** This bug is a duplicate of bug 146812 ***
https://bugs.launchpad.net/bugs/146812
** This bug has been marked a duplicate of bug 146812
Gusty Beta: error on startup. Internal Error failed to initialize HAL!
--
[gutsy] Failed to initialize HAL
https://bugs.launchpad.net/bugs/144044
You
*** This bug is a duplicate of bug 146812 ***
https://bugs.launchpad.net/bugs/146812
** This bug has been marked a duplicate of bug 146812
Gusty Beta: error on startup. Internal Error failed to initialize HAL!
--
[gutsy] failed to initialize hal
https://bugs.launchpad.net/bugs/137559
You
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
** This bug has been marked a duplicate of bug 127473
Failed To initialize HAL!
--
error de hal
https://bugs.launchpad.net/bugs/134885
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
** This bug has been marked a duplicate of bug 25931
Failed to initalize HAL.
--
Gusty Beta: error on startup. Internal Error failed to initialize HAL!
https://bugs.launchpad.net/bugs/146812
You received
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
** This bug is no longer a duplicate of bug 146812
Gusty Beta: error on startup. Internal Error failed to initialize HAL!
** This bug has been marked a duplicate of bug 25931
Failed to initalize HAL.
--
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
** This bug is no longer a duplicate of bug 146812
Gusty Beta: error on startup. Internal Error failed to initialize HAL!
** This bug has been marked a duplicate of bug 25931
Failed to initalize HAL.
--
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
** This bug is no longer a duplicate of bug 127473
Failed To initialize HAL!
** This bug has been marked a duplicate of bug 25931
Failed to initalize HAL.
--
error de hal
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
** This bug has been marked a duplicate of bug 25931
Failed to initalize HAL.
--
Failed To initialize HAL!
https://bugs.launchpad.net/bugs/127473
You received this bug notification because you are a
I can confirm this bug; nm-applet segfaults with an identical backtrace
to Dave Gilbert's. I am using Gutsy AMD64 but with a bcm43xx wireless
card.
--
nm-applet crashes on connect to other wireless network
https://bugs.launchpad.net/bugs/137989
You received this bug notification because you are
The bug was solved in the mainline kernel some time between 2.6.20 and
2.6.21. I suppose we need someone to use git-bisect to track down the
patch (or ask Thomas Gleixner...) in order to get a fix for Dapper.
There's a list of candidates here:
This affects Gutsy. I've clarified the original report.
** Summary changed:
- Input Source boxes are unlabelled in gnome-volume-control
+ [Gutsy] Usability problems in gnome-volume-control
** Description changed:
Binary package hint: gnome-media
- I find that the correct mixer settings
Is anyone working on this? This problem is still present on Gutsy, and
also affects Intel integrated graphics chipsets like the G965. The
workarounds listed here unfortunately only address nVidia cards.
** Changed in: desktop-effects (Ubuntu)
Status: New = Confirmed
--
enabled desktop
** Summary changed:
- sound problem in Audigy 2
+ Gnome Volume Control change device function has no effect
--
Gnome Volume Control change device function has no effect
https://bugs.launchpad.net/bugs/87909
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Public bug reported:
Binary package hint: gnome-media
I find that the correct mixer settings are extremely difficult to arrive
at using gnome-volume-control -- the process often takes me several
minutes of frustrating trial and error after each reboot or after waking
from suspend, both of which
** Attachment added: Options tab in gnome-volume-control showing identical,
uninformative labels of Input Source for different channels
http://launchpadlibrarian.net/9248929/Screenshot-Volume%20Control%3A%20HDA%20Intel%20%28Alsa%20mixer%29%20-%20Options.png
--
Input Source boxes are
** Attachment added: Recording tab showing separate capture channels (Capture,
Capture 1, Capture 2). These are also poorly labelled (what are Capture 1 and
Capture 2?) but at least they are distinct. Do these correspond to the three
Input Source boxes in the Options tab?
This bug is still present on Gutsy (which currently has alsa-
base-1.0.13-3ubuntu1).
--
Microphone bug in Ubuntu HDA_Intel
https://bugs.launchpad.net/bugs/37736
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
The bug doesn't seem to be present in Gutsy, which has a newer upstream
version (1.5.6 versus 1.0.5).
I assume the bug is still present in Edgy. I have no idea about Feisty.
I don't see how Launchpad can sensibly keep one bug report for multiple
versions. If the bug is fixed in Gutsy but not in
Public bug reported:
Binary package hint: notecase
With NoteCase 1.5.6 in Gutsy (notecase_1.5.6-0ubuntu1) on amd64,
demoting a second-level node to the first level causes a failed
assertion:
(notecase:13031): Gtk-CRITICAL **: gtk_tree_model_get_iter: assertion
`path-depth 0' failed
The
Public bug reported:
Binary package hint: notecase
In NoteCase 1.5.6 in Gutsy (1.5.6-0ubuntu1) on amd64, the keyboard
shortcuts such as Insert, Shift+Insert, Shift+arrow keys described in
the right-click popup menus from the left pane have no effect.
** Affects: notecase (Ubuntu)
*** This bug is a duplicate of bug 121796 ***
https://bugs.launchpad.net/bugs/121796
Kamus: this bug is present even when now using desktop effects on Gutsy.
--
[Gutsy] Move to Another Workspace has no effect
https://bugs.launchpad.net/bugs/131169
You received this bug notification because
*** This bug is a duplicate of bug 121796 ***
https://bugs.launchpad.net/bugs/121796
Kamus: sorry, s/when now/when not/
--
[Gutsy] Move to Another Workspace has no effect
https://bugs.launchpad.net/bugs/131169
You received this bug notification because you are a member of Ubuntu
Bugs, which
*** This bug is a duplicate of bug 121796 ***
https://bugs.launchpad.net/bugs/121796
Sebastien: Are you sure this is a duplicate of bug #121796? Its
description seems completely different to me. Indeed, the original
submitter of bug #132372 (which _does_ seem to be a duplicate of
#121796)
*** This bug is a duplicate of bug 36443 ***
https://bugs.launchpad.net/bugs/36443
** This bug has been marked a duplicate of bug 36443
Unable to move synaptic download window to another workspace
--
Cannot move to other workspace / desktop when processing
Public bug reported:
Binary package hint: metacity
Right-clicking a window's title bar and choosing Move to Another
Workspace has no effect for me in Gutsy. This is true for all
applications (not just Synaptic as in bug 36443). Choosing Move to
Workspace Left or ... Right works as expected. This
My system has just experienced an oops and a kernel panic upon resume
from hibernation; I think this bug might have caused it. My caps and
scroll-lock LEDs are flashing but the suspended session came up anyway
and the system is, amazingly, still running. The relevant dmesg output
is attached. The
This bug is fixed by 2.6.21 and 2.6.22, presumably by the clockevents
patches. So Gutsy will be fine.
--
[Feisty] Kernel timer losing clock ticks on amd64
https://bugs.launchpad.net/bugs/102383
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
It would still be a good idea to test with it though.
Okay, if nobody beats me to it, I'll test it in about two weeks, when
I have access to one of those machines again. (Interestingly, it's
never been an issue on one G965 I have, but affects a whole lab-full
of HP Q965 machines. Presumably it
Good news!
--
cp dumps core when copying 4GB files to a VFAT filesystem
https://bugs.launchpad.net/bugs/75574
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
The amd64 package libg2c0-dev installs a dangling symlink in
/usr/lib32/:
[EMAIL PROTECTED]:~$ ls -l /usr/lib32/libg2c*
-rw-r--r-- 1 root root 344962 2007-01-02 17:43 /usr/lib32/libg2c.a
-rw-r--r-- 1 root root728 2007-01-02 17:42 /usr/lib32/libg2c.la
lrwxrwxrwx 1 root
On 5/23/07, Micah Cowan [EMAIL PROTECTED] wrote:
Patch also sent to linux-kernel development mailing list:
http://lkml.org/lkml/2007/5/23/146
Thank you! Well done!
--
cp dumps core when copying 4GB files to a VFAT filesystem
https://bugs.launchpad.net/bugs/75574
You received this bug
kalyp: I suggest you remove the network-manager and
network-manager-pptp packages, install the subversion package, and
compile the latest SVN version from source. You'll find instructions
for this online.
--
Crash while trying to connect to PPTP server
https://bugs.launchpad.net/bugs/67881
You
** Changed in: kvm (Ubuntu)
Status: Unconfirmed = Confirmed
--
kvm crashes on load (exception 12)
https://bugs.launchpad.net/bugs/107172
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
This is a known problem with Intel CPUs:
http://kvm.qumranet.com/kvmwiki/Intel_Real_Mode_Emulation_Problems
This also seems to affect the latest upstream versions (e.g. kvm-19).
** Summary changed:
- kvm crashes on load (exception 12)
+ kvm crashes on load on Intel CPUs (exception 12)
--
kvm
This is a known problem upstream with Intel CPUs:
http://kvm.qumranet.com/kvmwiki/Intel_Real_Mode_Emulation_Problems
** Changed in: kvm (Ubuntu)
Status: Unconfirmed = Confirmed
** Summary changed:
- kvm crashes on load (exception 13)
+ kvm crashes on load with Intel CPUs (exception 13)
I can reproduce this every time with kvm_16-1ubuntu2 on an HP Compaq
dc7700p desktop system with Intel VT enabled in the BIOS (v2.09) running
Feisty x86_64 (kernel 2.6.20-15). This happens with out without -no-acpi
or -no-rtc.
My system log has hundreds of lines like the following:
[ 3271.013496]
Confirmed to affect kernel 2.6.20 on several different machines. Fixed
by 2.6.21-rc5.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Unconfirmed = Confirmed
--
[Feisty] Kernel timer losing clock ticks on amd64
https://bugs.launchpad.net/bugs/102383
You received this bug notification
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Needs Info = Confirmed
--
Ejecting firewire HD (iPod) freezes kernel
https://bugs.launchpad.net/bugs/52943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Booting with noapic doesn't seem to help; the clock is still losing
three seconds every minute. I've attached the output of dmesg.
Shall I report this upstream?
** Attachment added: Output of dmesg using noapic boot parameter
http://librarian.launchpad.net/7339308/dmesg_noapic.log
** Also
On 4/16/07, Sarah Hobbs [EMAIL PROTECTED] wrote:
guys, the bitching doesn't help. If anything, people are less inclined
to look at, due to all the useful information being hidden by all the
bitching.
It's confirmed. now wait. and help out.
This stuff is all free, and mostly
I can confirm that kvm is now installable (version 1:16-1ubuntu2) with
the current kernel.
--
Kvm not installable in feisty
https://bugs.launchpad.net/bugs/106028
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Well Done, Micah! I'm glad this is in capable hands :)
--
cp dumps core when copying 4GB files to a VFAT filesystem
https://bugs.launchpad.net/bugs/75574
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Summary changed:
- [feisty] kvm depends of kvm-api-9 but it not exists that package
+ [feisty] kvm depends of kvm-api-9 but that package is uninstallable
--
[feisty] kvm depends of kvm-api-9 but that package is uninstallable
https://bugs.launchpad.net/bugs/105263
You received this bug
I can confirm this is still a problem with kvm 18-1ubuntu1. It depends
on kvm-api-9, which is reported as being uninstallable. I'm using the
2.6.20-14-generic kernel on amd64. So the status of this bug should be
reverted to 'Confirmed' or 'In progress'.
** Attachment added: Log of an attempt to
I should add that this is a huge problem for these machines (HP Compaq
dc7700p desktops). The clock drift is far too severe for ntpd to correct
for it. The only workaround I know is to turn off the ntp daemon and run
ntpd -q every couple of minutes.
--
[Feisty] Kernel timer losing clock ticks on
The same bug is present in the 2.6.20-14-generic kernel.
--
[Feisty] Kernel timer losing clock ticks on amd64
https://bugs.launchpad.net/bugs/102383
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: linux-image-2.6.20-13-generic
This may or may not be a duplicate of bug 26064, reported for Breezy
(now closed).
We have four Core 2 duo machines with an Intel Q965 chipset that are all
losing ticks at about three seconds per minute (three hours per
** Attachment added: Output of lspci -vv
http://librarian.launchpad.net/7057274/lspci.log
--
Losing ticks on amd64
https://launchpad.net/bugs/26064
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'd like to re-open this bug for Feisty. We have four Core 2 duo
machines with an Intel Q965 chipset that are all losing ticks at about
three seconds per minute (three hours per day). This appears to be an
upstream kernel bug with both 2.6.19 and 2.6.20, since this occurs for
us with both Feisty
On 3/17/07, Matthew Flaschen [EMAIL PROTECTED] wrote:
Sarah Hobbs wrote:
it's in feisty because if we remove it, we then have to do all the
packaging again when it *does* work.
Of course, that's not true. It can be moved out of the repos now, and
back if/when it works. Nothing in the
Public bug reported:
Binary package hint: texlive-latex-recommended
The mathpazo (Palatino) fonts are included in the package texlive-latex-
recommended, but these are unusable from LaTeX without the style file
mathpazo.sty, which is missing.
As a trivial test case, the document
Ah, it appears that mathpazo.sty is in texlive-latex-base.
Does it really make sense to split up the style files and font files
into different packages? Aren't the style files and font files entirely
useless without each other?
--
[Feisty] mathpazo style file is missing from
*** This bug is a duplicate of bug 70535 ***
** This bug has been marked a duplicate of bug 70535
nautilus crashes when copying a 4G file on a vfat volume
--
Nautilus crashes trying to copy 4GB file to msdos fs
https://launchpad.net/bugs/26042
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 75574 ***
No, this bug is not bogus! cp should check this before it starts copying
a 4GB file and give a helpful error message. It should not waste the
user's time copying only the first 4GB of the file and then dump core.
This bug is simple to reproduce:
** Summary changed:
- cp crashes when copying large files to usb device
+ cp dumps core when copying 4GB files to a VFAT filesystem
** Tags added: ipod vfat
--
cp dumps core when copying 4GB files to a VFAT filesystem
https://launchpad.net/bugs/75574
--
ubuntu-bugs mailing list
This bug is simple to reproduce: create a large (4GB) tar file and copy it to
a VFAT partition (e.g. an iPod). cp dumps core.
Preferably cp should not waste the user's time copying only the first
4GB of the file before raising an error, but should check in advance
whether the file size will be
Good work!
Should the shared-mime (upstream) bug report also be closed?
--
application/mbox should be a sub-class of text/plain?
https://launchpad.net/bugs/83001
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm this bug with an Intel G965 X3000 GMA. I'm using xorg-
server-core-1.1.1-0ubuntu13 and linux-2.6.20-6-generic. My architecture
is AMD64.
A backtrace from /var/log/Xorg.0.log.old is similar to that of the
original reporter:
Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x71)
** Attachment added: My complete Xorg.0.log file
http://librarian.launchpad.net/6217560/Xorg.0.log.old
--
X appears to crash randomly
https://launchpad.net/bugs/71913
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
(All of these Xorg crashes I've experienced so far (about two per day)
have occurred while using Firefox.)
--
X appears to crash randomly
https://launchpad.net/bugs/71913
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: nautilus
Nautilus 2.17.90 refuses to open certain text files, claiming:
Error: no application found
Cannot open /home/me/file.txt: No application is known for this kind of file.
A test case:
echo From Dostoevsky: test1.txt
echo In Dostoevsky:
Onlymee: thanks for the info. A clarification: nm-ppp-starter.c doesn't
exist in the source tree for version 0.6.4. And by your definition the
NM in Feisty is old: there's no 'dict' in nm-vpn-service.c.
I think we should push Feisty's network-manager-pptp to version 0.6.4
with the above trivial
I've changed my mind. I now think we should package an SVN version for
Feisty. I've compiled the SVN version and I'm impressed. It works for
me.
This is a big deal for me. DSL providers in Austria like inode.at
*require* PPTP connections for authentication. Without this one gets no
access at all.
Public bug reported:
Binary package hint: f-spot
F-Spot 0.3.2 gives an error when trying to export photos to a folder
with a single quote like Gallery - Fred's wedding:
Mono.Data.SqliteClient.SqliteSyntaxException: unrecognized token: 1.JPG
at
Feisty has the same pptp version as edgy. If it's not compatible with
network-manager 0.6.4, does that explain the segfaults?
I tried compiling the 0.6.4-tagged branch from SVN, but I get a linker
error: relocation R-X86_64_32 against `a local symbol' ... recompile
with -fPIC. Passing --with-pic
Some progress: I compiled it with the right CFLAGS. Version 0.6.4
produces a nm-pptp-auth-dialog binary instead of nm-ppp-auth-dialog from
the previous version. Was it renamed?
If I run the test given by onlymee earlier in the thread, but with the
new filename, I get:
$
I still get a segfault with this patch. I'm using Feisty AMD-64,
network-manager-pptp-0.6.3+cvs20060819. Here's a backtrace from gdb:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47328421673936 (LWP 30782)]
0x2b0b7e41022b in free () from /lib/libc.so.6
(gdb) bt
#0
Gustavo: It's from the source tree of network-manager-
pptp-0.6.3+cvs20060819, in the auth-dialog/ directory.
--
Crash while trying to connect to PPTP server
https://launchpad.net/bugs/67881
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm also seeing this in 2.6.20-5-generic.
--
Unable to debug under 2.6.19: Failed to read a valid object file image from
memory
https://launchpad.net/bugs/74691
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ah, sorry, my mistake: I don't even have nfs-common installed under Feisty. I
was confused about this because I'm happily using an NFS share (mounted
statically in /etc/fstab) even without the nfs-common package. I had assumed
this was impossible, but clearly nfs-common *isn't* required for
Yes, that's what I thought. Indeed apt-cache show nfs-common lists
portmap as a dependency. But something seems odd. Why does
# apt-get remove portmap
not remove nfs-common too?
--
[Feisty] portmap missing after upgrade from Edgy?
https://launchpad.net/bugs/78457
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: epiphany-browser
I can repeatably crash epiphany-browser by loading the following page:
http://www.amazon.com/gp/reader/080583270X/ref=sib_dp_pt/102-6275526-9992103
#reader-link
and switching to other windows.
Crash report attached.
** Affects:
** Attachment added: Crash report from Epiphany 2.17.4-0-ubuntu1
http://librarian.launchpad.net/5631763/_usr_bin_epiphany.1079.crash
--
[Feisty] Crash displaying pages in the Amazon Online Reader
https://launchpad.net/bugs/78441
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Ah, libflashplayer.so appears in the stack trace, so a likely culprit is
my Adobe plugin. (But after removing libflash0c2, libflash-swfplayer,
and libflash-mozplugin, I can't reproduce the crash. Perhaps these
conflict with the Adobe plugin. Damned Flash.)
Epiphany-browser still has the following
Public bug reported:
Binary package hint: portmap
After upgrading from Edgy to Feisty, I could no longer mount NFS shares.
Manually installing portmap fixed the problem. Presumably portmap was
installed on my system before the upgrade, since I could mount NFS
shares fine until then.
Perhaps a
Public bug reported:
[EMAIL PROTECTED]:~$ sudo apt-get build-dep matplotlib
Password:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Build-Depends dependency for matplotlib cannot be satisfied because the
package xbase-clients[!s390] cannot be
1 - 100 of 120 matches
Mail list logo
