mlangermann: are there please any drawbacks to the temporary solution
you kindly offered (i.e. why did you call it temporary)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780916
Title:
Serious
Please any chance of getting this fixed in the 18.04 LTS (Bionic)? It
seems the package is hardly usable without this fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780916
Title:
Serious
I have experienced this issue today when upgrading a 32-bit fully up-to-
date 11.04 system to 11.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873517
Title:
When upgrading from maverick to
Jean-Baptiste, thanks for your bugreport. Could you please attach 2 log
files from your ~/.speech-dispatcher/log directory: speech-
dispatcher.log and espeak.log? They can contain the text that was spoken
to you which could contain private information, but if you are OK
sending the files, it could
The reason of abort is NULL pointer passed as pa_simple to
pa_simple_write. I reported it upstream:
https://its.freebsoft.org/its/issues/6773
** Changed in: speech-dispatcher (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This was fixed in Oneiric in 0.7.1-6ubuntu1. Not sure if this is SRU
worthy for earlier releases, going for no, if someone thinks otherwise,
please reopen.
** Changed in: speech-dispatcher (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a
Public bug reported:
Binary package hint: gnome-disk-utility
1. Install Maverick i386 desktop (happened 3 months ago)
2. Update it to latest software using apt-get update and apt-get
dist-upgrade. I did not restart to boot into the new kernel.
3. Run sudo do-release-upgrade over ssh to upgrade
This is much more a gnome-orca problem than speech-dispatcher problem.
At least the gnome-orca package maintainer(s) will have better idea what
could start Orca if not the autostart file.
** Package changed: speech-dispatcher (Ubuntu) = gnome-orca (Ubuntu)
--
You received this bug notification
** Changed in: speech-dispatcher (Ubuntu)
Assignee: (unassigned) = Boris Dušek (dusek)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769602
Title:
speech-dispacher specifies global options
This is already fixed in Debian unstable. I will merge the Debian
package into the Ubuntu package after Oneiric opens up for development.
** Changed in: speech-dispatcher (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Lucid contains an outdated version of Speech Dispatcher (0.6 series), so
I will test the current series (0.7) present in Maverick and later. I am
unable to reproduce this on clean install of Maverick (10.10). orca
picks up espeak-generic fine:
0. launch gnome-terminal, do everything that follows
Hi,
I am sorry I did not respond, but it was hard to test since I am no
longer using Linux and I could not arrive quickly on an idea how to test
this. However I would like to test it in VMware virtual machine, I just
would need a little bit of guidance on how to (preferably repeatedly)
trigger an
I was using 32-bit version when I encountered the bug I reported.
--
Partitioner displays partition too small-like incorrect message
https://bugs.launchpad.net/bugs/219568
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
1. Attached. (I clicked on the Continue in the message dialog and then saved
the syslog.)
2. Sigh, I actually overlooked the / character, since it looked like a stray
character to me. If it was with a partition with a longer name (i.e. /mnt), I
am sure I would not have overlooked it.
**
Attached syslog with the correct script traced as you specified. This
time I tried 10GB HDD instead of 12GB, it appeared again, the number
seemed very similar to the one in screenshot (1999 ... I did not
actually check all the digits, but guess it was the same). Also this
time I attached the
Public bug reported:
I installed Ubuntu 8.04 RC1 in VMware Fusion. I chose hostname of
ubuntu-8.04-rc1, however after install the hostname was ubuntu-8
(/etc/hostname). Apparently the content of the hostname after the dot
(inclusive) got stripped away. This is IMHO similar to
Public bug reported:
I was installing Ubuntu 8.04 RC1. In the partitioner in the installer, I
chose manual setup (as opposed to guided setup). I created a scheme
that's shown on the screenshot attached. The error message in the
screenshot does not make sense. It read Some of the partitions you
** Attachment added: ubuntu-8.04-rc1_partitioner-too-small-partition.tiff
http://launchpadlibrarian.net/13577175/ubuntu-8.04-rc1_partitioner-too-small-partition.tiff
--
Partitioner displays partition too small-like incorrect message
https://bugs.launchpad.net/bugs/219568
You received this
Wireless still not working in Hardy Alpha 5. Macbook Pro rev3 (Santa
Rosa), lspci reports AR5418 for the wireless (same as macavity's
Macbook).
--
[Hardy, Gutsy] Wireless adapter not detected on MacBook Pro rev.3 (santa rosa)
https://bugs.launchpad.net/bugs/125919
You received this bug
Public bug reported:
Hi,
I was doing an update that update-manager offered to me on my Gutsy
machine. One of the packages updated was NetworkManager. As it was being
deployed, I saw in the console that it was being restarted (probably in
order for the update to take effect immediately).
@Sebastian:
the second patch you applied is obsoleted by another more correct patch in the
same bugzilla entry. And this first better patch just got commited to Gnome SVN.
The first patch from msiner also just got commited to Gnome SVN, so what's
needed for the package is to remove both patches
Hi, I have qemu-i386 crashing on an x86 machine. I did install libc-dbg,
qemu-dbgsym and did gdb session exactly as recommended. (the problem does
happen on my production Feisty machine x86 machine, I reproduced the problem
with Ubuntu Feisty default install + updates until today in VMware,
I created a patch that handles the crash bug on Gutsy, could someone
please build a .deb for Gutsy with this patch so that others can test
it? (it works for me)
the patch is in Gnome bugzilla -
http://bugzilla.gnome.org/show_bug.cgi?id=329922, it's the last one
(named Do not update input list
@Balaji:
I agree it should not overwrite your saved file. But, e.g. if you want
to improve the old (saved) version, you should be able to record a new
record (without overwriting the old record), be able to play it back to
decide whether it's better than the saved one, and then, if you want,
save
OK, see my last comment in upstream bugzilla - gnome-media from SVN,
both with and without the proposed patch applied, exhibit the same buggy
behavior. So it's not this patch that introduces the new regression, but
either some other changes in grecord (which seems very inactive though),
or other
@Sebastian: thanks, I will now know for the future
@jhasse: :-) I guess I will have to visit my eye doctor ;-)
I tested the patched version on Feisty with the deb provided at comment
#28 (https://bugs.launchpad.net/ubuntu/+source/gnome-
media/+bug/92879/comments/28). The new regression that is
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/8598670/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/8598671/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/8598672/ProcStatus.txt
** Bug watch
Public bug reported:
Binary package hint: gcalctool
see the report upstream
ProblemType: Bug
Architecture: i386
Date: Sun Jul 29 12:34:46 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gcalctool
NonfreeKernelModules: vmxnet
Package: gcalctool 5.19.5-0ubuntu1
PackageArchitecture: i386
I confirm this bug on Gutsy Tribe 3 + all updates as of Jul 28. I did
the same thing as Jeroen - since I am testing Gutsy in VMware, I had no
photos, so I simply clicked Cancel on the import dialog that's
displayed when you run F-Spot for the first time. Then the main window
appeared, and this
Hi, I tested with tribe 3 + all updates until as of today, Jul 28. See
upstream bug report for details.
The bug is solved, but (I don't know if it's new, probably yes) a new
one is created - hitting on record, then stop, and then hitting on
record again without saving the previous record makes
Very same problem here with ipw3945. Quite a disappointment for me,
since I hoped I will not have to touch the command-line for network
configuration in Feisty.
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug
Maybe you someone could add his/her comment not only in Launchpad, but
also in the Gnome bugzilla (bug number430101, or use the link at the top
right), where the real solution will get place, so that the problem
might get more attention there.
--
gnome-sound-recorder unable to playback
Public bug reported:
Binary package hint: vnc-common
Hi,
I am running Feisty. I enabled VNC on my laptop so that I can view its
screen when I am at a school computer, I used the
System-Preferences-Remote Desktop tool and enabled VNC. I could
connect from school to my laptop with no problem,
Running x86 Feisty release (not x86_64 as with the livecd), the problem
is not present. So either this was fixed, or it's only x86_64-specific
issue.
--
[feisty] Hitting ower button shows shutdown dialog, when canceled the same
dialog appears again
https://bugs.launchpad.net/bugs/107036
You
Ooops, I hit the button Also needs fixing here to look where it needs
to fix, and did not realize from the text that it makes a change to
bugzilla instead of bringing me to that page I wanted to see, sorry for
any inconvenience.
--
Urgent text is poorly readable due to low contrast (blue on
sadly, X crashes on start with Feisty RC
here is diff between xorg.conf from beta to RC:
Modes 1400x1050 (pitch 1400)
---
Modes 1024x768 800x600 640x480
122c115
Modes 1400x1050 (pitch 1400)
---
Modes
** Attachment added: Xorg.0.log
http://librarian.launchpad.net/7340465/Xorg.0.log
--
Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is
ok)
https://bugs.launchpad.net/bugs/83072
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Running Ubuntu Feisty Beta (x86_64), on ASUS F2JE laptop.
When I hit the physical power button on my notebook, the shut down dialog
appears as it should. However, when I press Cancel in that dialog, the dialog
reappears once more. In the second dialog, clicking Cancel
The problem occurs when using the Feisty Beta LiveCD (I have only Edgy
installed on my harddisk). So there might be some fix released for this
after Beta. When Feisty RC is released, I will retest.
--
[feisty] Hitting ower button shows shutdown dialog, when canceled the same
dialog appears
Sorry if I am blind, but how do I find the # of associated upstream bug
in gnome bugzilla? The Remote Bug # field is empty.
--
gnome-sound-recorder unable to playback
https://bugs.launchpad.net/bugs/92879
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I just reported it to upstream and updated the remote bug #.
** Changed in: gnome-media (upstream)
Importance: Undecided = Unknown
Bugwatch: None = GNOME Bug Tracker #430101
Status: Unconfirmed = Unknown
--
gnome-sound-recorder unable to playback
btw., why fglrx (ATI's binary driver) is not used for my card when we
have the restricted driver manager?
--
Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is
ok)
https://bugs.launchpad.net/bugs/83072
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 92879 ***
https://bugs.launchpad.net/bugs/92879
** This bug has been marked a duplicate of bug 92879
gnome-sound-recorder unable to playback
--
[feisty,beta] Invalid parameters on recording sound with Sound recorder
(gnome-sourd-recorder)
surprise that gnome-
sound-recorder actually can record. Other users will definitely not have
such patience (and even conclude their microphone does not work in
Ubuntu).
Best regards,
Boris Dušek
** Affects: gnome-media (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
[feisty
into account.
All the best,
Boris Dušek
--
[herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression
from herd3
https://launchpad.net/bugs/89552
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Contents of /proc/asound in Feisty Beta, just in case they are needed.
** Attachment added: /proc/asound - tar.gz archive
http://librarian.launchpad.net/7079155/proc-asound.tar.gz
--
[herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression
from herd3
Wow, in Feisty Beta it's fixed. However, part of boot is displayed in
text mode, I don't know if this is intentional.
--
Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is
ok)
https://launchpad.net/bugs/83072
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
,
Boris Dušek
P.S.: Sorry, what I attached is not a bz2, but a gz archive of
/proc/asound (but accidentaly named *.bz2). I am resubmitting a
correctly named file again, for your convenience.
--
[herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression
from herd4
https
Still present in Herd 5 (Feisty).
--
Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is
ok)
https://launchpad.net/bugs/83072
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
ALC861, not ALC660 (tar.bz2 archive
of /proc/asound attached).
Please find in attachements tar.bz2 archive of /proc/asound, then
outputs of dmesg, lspci, lspci -n, lspci -v and lsmod.
If you need any info or further testing, I will be glad to provide.
Best regards,
Boris Dušek
** Affects: linux
** Attachment added: /proc/asound - tar.bz2 archive
http://librarian.launchpad.net/6608587/proc-asound.tar.bz2
--
[herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression
from herd4
https://launchpad.net/bugs/89552
--
ubuntu-bugs mailing list
** Attachment added: dmesg
http://librarian.launchpad.net/6608590/dmesg
--
[herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression
from herd4
https://launchpad.net/bugs/89552
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: lspci
http://librarian.launchpad.net/6608591/lspci
--
[herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression
from herd4
https://launchpad.net/bugs/89552
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: lspci -n
http://librarian.launchpad.net/6608592/lspci-n
--
[herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression
from herd4
https://launchpad.net/bugs/89552
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: lspci -v
http://librarian.launchpad.net/6608594/lspci-v
--
[herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression
from herd4
https://launchpad.net/bugs/89552
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: lsmod
http://librarian.launchpad.net/6608595/lsmod
--
[herd5,alsa] no sound (and no microphone), snd_hda_intel, realtek - regression
from herd4
https://launchpad.net/bugs/89552
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
.
If you need any info or further testing, I will be glad to provide.
Best regards,
Boris Dušek
+
+ P.S.: Sorry, what I attached is not a bz2, but a gz archive of
+ /proc/asound (but accidentaly named *.bz2). I am resubmitting a
+ correctly named file again, for your convenience.
** Attachment
Hello Norbert,
And for the next bug report, please read what is written in the ouput:
fmtutil-sys failed. Output has been stored in
/tmp/texlive.fmtutil.GPC14041
Please include this file if you report a bug.
Well, I did read the output, and said in my bugreport that:
texlive-formats-extra
Public bug reported:
Hello,
This happens on Edgy. I had tetex installed, but then decided to switch
to texlive, so I installed texlive-full (and the installer told me that
tetex will be removed, so I think there shouldn't be any conflict
between tetex and texlive).
But three packages from
Resolved in herd3, additionally microphone now works, unlike in Edgy and
Dapper.
--
(feisty, alsa-driver) NULL pointer in snd_hda_codec
https://launchpad.net/bugs/83096
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: xserver-xorg
Hello,
I tried Feisty Herd 2 (as live CD), and it has the same problem as Edgy Eft:
The screen in graphical environment is skewed; autodetection uses the vesa
driver.
This is a regression from Dapper - there it worked fine.
I have some
** Attachment added: lspci -n
http://librarian.launchpad.net/6170298/lspci-n.feisty
--
Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is
ok)
https://launchpad.net/bugs/83072
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
discover --disable=parallel,serial,usb,ide,scsi,pcmcia
Output is empty.
--
Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is
ok)
https://launchpad.net/bugs/83072
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: xresprobe vesa
http://librarian.launchpad.net/6170480/xresprobe-vesa.feisty
--
Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is
ok)
https://launchpad.net/bugs/83072
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: /var/log/Xorg.0.log - for Xorg :0 -ac -logverbose 999
http://librarian.launchpad.net/6170527/Xorg.log.feisty.verbose
--
Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is
ok)
https://launchpad.net/bugs/83072
--
ubuntu-bugs mailing list
This is for the reconfigured server, where the screen is not skewed, but
resolution is only 1024x768
** Attachment added: /var/log/Xorg.0.log
http://librarian.launchpad.net/6170569/Xorg.log.feisty.reconf.verbose
--
Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is
Feisty autodetected configuration
** Attachment added: xorg.conf
http://librarian.launchpad.net/6170596/xorg.conf.feisty
--
Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is
ok)
https://launchpad.net/bugs/83072
--
ubuntu-bugs mailing list
is present no matter if I choose default boot options, or if
I remove quiet splash and add vga=771 (or vga=791).
I will be glad if I can help to resolve this issue by providing
additional information.
+
+ Thanks,
+ Boris Dušek
--
Skewed screen - Mobility Radeon X1450 with vesa (only feisty
remove quiet splash and add vga=771 (or vga=791).
I will be glad if I can help to resolve this issue by providing
additional information.
Thanks,
Boris Dušek
--
Skewed screen - Mobility Radeon X1450 with vesa (only feisty, edgy; dapper is
ok)
https://launchpad.net/bugs/83072
0068:f67d3cf8
If you need any other information, I will be glad to provide.
Thanks,
Boris Dušek
** Affects: linux-meta (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
(feisty, alsa-driver) NULL pointer in snd_hda_codec
https://launchpad.net/bugs/83096
--
ubuntu-bugs
70 matches
Mail list logo
