Thanks Gunnar,
I have filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991228
** Bug watch added: Debian Bug tracker #991228
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991228
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Package changed: anki (Ubuntu) => mozc (Ubuntu)
** Description changed:
This was working fine before I upgraded to 21.04. Since then I am seeing
what appears to be a bad interaction between the Japanese input method
and anki or anki's underlying widget set. Hiragana input works by
This issue has now been fixed in mozc under issue 510 above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931554
Title:
Japanese hiragana input fails after first keypress in anki
To manage
c.f. https://github.com/google/mozc/issues/510
** Bug watch added: github.com/google/mozc/issues #510
https://github.com/google/mozc/issues/510
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As far as I can tell line 207 above fails due to the text being the
empty string "", but the cursor_pos and anchor_pos are both 1, so line
207 is trying to assign the string from position 1 to position 0 within
the empty string. That makes some sense given how the input method
works. At the time
mozc_engine.cc:207 appears to be source of an exception in a C++ string, so
surrounding_text.end - selection_end_it < 0...
(gdb) list
202 const size_t selection_length = abs(info->relative_selected_length);
203 const auto _start_it = surrounding_text.begin() +
selection_start;
204
I think I'm narrowing down on the source of the issue. I'm seeing crashes in
ibus-engine-mozc as part of package ibus-mozc
After building from source and installing debug symbols the key parts of the
stack trace appears to be as follows
#10 std::__cxx11::basic_string,
std::allocator
c.f. https://github.com/ankitects/anki/issues/1239
** Bug watch added: github.com/ankitects/anki/issues #1239
https://github.com/ankitects/anki/issues/1239
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This was working fine before I upgraded to 21.04. Since then I am seeing
what appears to be a bad interaction between the Japanese input method
and anki or anki's underlying widget set. Hiragana input works by typing
the roman characters that make up a word. After typing a
Here are two alternative ways to demonstrate this command line parsing bug:
1. In a bash terminal say:
trap "I received an invalid TERM signal" SIGTERM
/bin/kill -s TERM -15
Note that bash ignores the TERM unless this trap is present, so the TRAP makes
it clear what is going on.
2. In a bash
Public bug reported:
When upgrading from 13.10 to 14.04 today I had the rtupdate processing
fail twice, once on the onboard package and once on an ubuntuone
package. In both cases the rtupdate file asked dpkg to list the contents
of the packages, which were not installed at the time of the query.
Public bug reported:
All menu items are greyed out and insensitive on my machine after an
upgrade from 13.10 to 14.04. The only menu items that show as sensitive
are sub-menus, all of whose menu items are greyed out.
I am still able to save my current project with the Ctrl-S shortcut, and
I can
I can't say I have a workaround, but I did manage to get my machine built after
several hours of trying. After the successful copy of files to the target and
the failure to install the subsequent packages I switched to recovery mode,
specifying the raid mirror as my root filesystem. In this
I am seeing this on a 13.10 serer install with UEFI bios. I am
installing onto a RAID1 mirror of two intel SSDs. The copying files
step appears successful but whatever apt commands get run in the target
by the installer seem to fail. Apt and dpkg commands run in chroot by
hand seem to work.
One
Public bug reported:
I have recently upgraded my wife's laptop to 10.04. Now at boot time it
occasionally stops during the boot process to warn about failing to
mount /proc/bus/usb, and asks if we would like to continue. Here's an
excerpt from today's boot log:
(this is the first line in the
** Attachment added: Full boot log
http://launchpadlibrarian.net/48093710/boot.log
--
Filesystem could not be mounted: /proc/bus/usb
https://bugs.launchpad.net/bugs/577636
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hrrm... following the advice from
http://ubuntuforums.org/showthread.php?t=1468486 I have removed the usb
line from my fstab. I notice my more recently-installed server box
doesn't have this line, and everything appears to be working properly
without it. Presumably this is a problem faced only by
** Changed in: gdm (Ubuntu)
Status: Invalid = New
--
Cannot change volume while on logon screen
https://bugs.launchpad.net/bugs/156169
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This has annoyed me for a long time, also. It particularly affects first
startup of the computer.
Steps to reproduce:
1. Set your volume up reasonably high before shutdown, or otherwise ensure the
volume levels are high in alsa at boot time
2. Reboot the machine
3. Log in
4. Arggh! The ubuntu
Is this a duplicate of bug #156169?
--
GDM does not allow control over sound volume level
https://bugs.launchpad.net/bugs/528031
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
Public bug reported:
Two packages stalled my 10.04 upgrade last night, requiring user
intervention to continue. The first was a pam library, which asked me
for a list of services to restart. The second was the rpm package,
indicating to me that it was not able to use its existing database with
Just a quick update.
I am still running Jaunty at the present time. I'm pretty busy at the
current moment and haven't had time to upgrade to Karmic. I have been
working through the AGP modes in xorg.conf. I am up to 4 (tried 1 2,
but not 8). This has been more stable for me, which is to say that
Public bug reported:
I am not able to browse for printer shares exposed by a windows machine
at my mother-in-law's house. I can type the name in manually, but
browsing causes a crash of system-config-printer. This is an up-to-date
32-bit i686 hardy laptop with wireless-only connectivity.
Method:
** Attachment added: Wireshark (pcap) capture of smb conversation
http://launchpadlibrarian.net/30202388/SAMBA%20printer%20browse%20crash.pcap.gz
--
Crash while browsing smb printer shares
https://bugs.launchpad.net/bugs/412336
You received this bug notification because you are a member of
The attention sound is not happening for me under the same conditions
with Karmic. Actually, I don't seem to be getting any attention sound at
all at the moment, but neither do I see any repeated messages in the
auth log. It looks like it isn't a problem for me under Karmic.
--
Login attention
Ok, this is for my own benefit (and Mark's as he is having the same
problem as noted above) as much as anyone's.
I put a strace on various gdm processes while this was going on. The
strace shows read and writes consistent with the initial login as user
1, and the final login to switch back to
** Attachment added: gdm choooser strace output
http://launchpadlibrarian.net/26929705/gdmchooser.strace
--
Login attention sound on continuous repeat after user switch
https://bugs.launchpad.net/bugs/373961
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ok. I have a workaround in code, and remain confident that the root cause is
switching virtual terminals while a key is being pressed or has just been
pressed causing a keyboard repeat.
I modified gdmopen.c and getvt.c. Wherever I saw the ioctl to switch virtual
terminals (VT_ACTIVATE) I added
Ok, may I suggest setting back to Unconfirmed status?
I am still able to reproduce this reliably. I experimented with pressing
Tab instead of Enter at the gdm login prompt. Enter still puts the login
cycle into continuous repeat. However Tab only plays the sound once as
gdm returns to the login
Yes, as noted in the bug report. The trigger is user 1 logging out
back to gdm while user 2 still has a session going. When user 2 logs
in through gdm back to their running session.
This has happened reliably for me, 100% of the time so far after a
small number of attempts. My auth.log
Public bug reported:
Binary package hint: network-manager-gnome
This appears to be the same as Bug 284162, however 284162 has apparently since
been hijacked by a different source problem altogether. Here are the steps to
reproduce:
Preconditions: User 1 and User 2 have credentials to enable
I would like to track the progress of this bug. Would you mind marking
it as a duplicate of the report that you are referring to?
--
Login attention sound on continuous repeat after user switch
https://bugs.launchpad.net/bugs/373961
You received this bug notification because you are a member of
Are your referring to bug 237429? As noted, my triggering conditions are
different but I would be happy for these to be investigated together.
237429 seems to indicate this happens on a normal fast user switch,
which is not my bug. Note that the information in this bug (373961)
suggests that gdm
I have just experienced another lockup, so rather than raise another bug report
about it I thought I would continue attaching information to this one. My
assumption at this stage is that they have the same root cause.
The lockup behaviour I experienced today was as follows:
* Applications locked
** Attachment added: Xorg log from during lockup
http://launchpadlibrarian.net/26529137/Xorg.0.log
--
glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200
se)
https://bugs.launchpad.net/bugs/373968
You received this bug notification because you are a member of
** Attachment added: sample strace output from Xorg process during lockup
http://launchpadlibrarian.net/26529158/Xorg-strace
--
glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200
se)
https://bugs.launchpad.net/bugs/373968
You received this bug notification
Public bug reported:
This bug may be the same as bug 237429, but my triggering conditions are
different. Like 237429, I get a continuous drumming noise. I am able to
reproduce this on both of my Ubuntu machines (running 9.04). Steps to reproduce
are:
1. Log in user 1 on a freshly-booted
Public bug reported:
I have been getting glyph corruption since upgrading to Jaunty (examples
attached). Mostly it is a few characters here and there, but in some
cases the corruption is substantial. The corruption seems to be the
random flipping or changing of pixels across the glyph, sometimes
** Attachment added: Today's Xorg log: not a crash log
http://launchpadlibrarian.net/26491204/Xorg.0.log
--
glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200
se)
https://bugs.launchpad.net/bugs/373968
You received this bug notification because you are a member
** Attachment added: Corruption of m and w
http://launchpadlibrarian.net/26491223/Screenshot-2-crop.png
--
glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200
se)
https://bugs.launchpad.net/bugs/373968
You received this bug notification because you are a member of
** Attachment added: Widespread corruption after fast user switch. This user
is running compiz.
http://launchpadlibrarian.net/26491247/Screenshot.png
--
glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200
se)
https://bugs.launchpad.net/bugs/373968
You received
** Attachment added: Corruption of W, m, and l
http://launchpadlibrarian.net/26491217/Screenshot-1-crop.png
--
glyph corruption and occasional X lockup in Jaunty with ati rv280 (radeon 9200
se)
https://bugs.launchpad.net/bugs/373968
You received this bug notification because you are a
Sorry about the delay. It's no dice on Hardy at this stage.
I tested the aforementioned modes: 1, 2, 4, and 8. All produced the same
result. My PW191 monitor indicates no signal. My keyboard number lock
and other lights are still working, but attempting to Ctrl+Alt+1 to a
console and reboot
I upgraded to Intrepid today, and can report success. I removed the
driver=vesa line from my xorg.conf file after the upgrade, and it came
up ok both after an X restart and after a restart of the whole machine.
I have reviewed the X log and can see the radeon driver being loded.
I am happy for
Leann,
I have checked with my wife, who indicates that sound has been working
for some time now under Hardy, and on the aforementioned laptop. I'm not
quite sure when it came good, but it looks to be a while ago. Sorry
about keeping this bug open for so long in the mean-time.
Benjamin.
--
G'day,
I believe I am experiencing this same problem so many years later. My
install is Hardy Heron, amd64. I have rebuilt most of the system without
replacing the video card. Before the rebuild and under 32-bit gutsy the
card appeared to function correctly. After the rebuild and under 64-bit
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/15330985/Xorg.0.log
--
[regression][rv280] black screen and console freeze when X starts - drm lockup
https://bugs.launchpad.net/bugs/67487
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: xserver-xorg-video-ati
G'day,
I get a complete console lock-up when gdm starts with the default
xorg.conf under amd64 Hardy Herron with version 1:6.8.0-1 of xserver-
xorg-video-ati. The keyboard is unresponsive, including Caps Lock. I am
unable to
** Attachment added: Partial lspci -vv output
http://launchpadlibrarian.net/15332376/lspci-vv
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/15332377/Dependencies.txt
--
[rv280] X fails to start under Hardy amd64
https://bugs.launchpad.net/bugs/240169
You received
** Attachment added: Xorg log
http://launchpadlibrarian.net/15332383/Xorg.0.log
--
[rv280] X fails to start under Hardy amd64
https://bugs.launchpad.net/bugs/240169
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Confirmed: Hardy amd64. Fix seems to work.
--
tinyerp-client doesn't start
https://bugs.launchpad.net/bugs/179087
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
Unfortunately, this problem has reappeared for me under Hardy Herron.
Installing the backports package has not solved it for me. I haven't
looked into why any further as yet.
--
Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
https://bugs.launchpad.net/bugs/120302
You
G'day,
Further to my previous success using a custom-patched kernel, I found
tonight that installing the backports module under gutsy gives me sound.
The package I selected was linux-backports-modules-generic,2.6.22.14.21
which pulled in linux-backports-modules-2.6.22-14,2.6.22-14.10. A quick
vicomte: Yeah, I'm still floating around :)
http://soundadvice.id.au/blog/
--
Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
https://bugs.launchpad.net/bugs/120302
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Hello,
I have managed to get some sound functions working with a custom-patched
kernel.org 2.6.23.1. I applied [1] to the patch_realtek.c file, part of
the snd_hda_intel driver. The patch is against a different version, so I
had to apply it manually in the end. Attached is the file I ended up
I have just upgraded to gutsy in order to get alsa 1.0.14 and the
2.6.22-10 kernel. Unfortunately, I still have no sound. It looks like
the upstream patch does not fix this problem. Attachments to follow.
--
Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
** Attachment added: amixer
http://launchpadlibrarian.net/9189845/amixer.txt
--
Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
https://bugs.launchpad.net/bugs/120302
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: aplay --list-devices
http://launchpadlibrarian.net/9189849/aplay-device-list.txt
--
Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
https://bugs.launchpad.net/bugs/120302
You received this bug notification because you are a member of Ubuntu
** Attachment added: asoundconf list
http://launchpadlibrarian.net/9189852/asoundconf.txt
--
Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
https://bugs.launchpad.net/bugs/120302
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: dmesg
http://launchpadlibrarian.net/9189853/dmesg.txt
--
Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
https://bugs.launchpad.net/bugs/120302
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: cat /proc/interrupts
http://launchpadlibrarian.net/9189854/interrupts.txt
--
Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
https://bugs.launchpad.net/bugs/120302
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: sudo lspci -nnvv
http://launchpadlibrarian.net/9189855/lspci.txt
--
Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
https://bugs.launchpad.net/bugs/120302
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
** Attachment added: lspnp -v
http://launchpadlibrarian.net/9189856/lspnp.txt
--
Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
https://bugs.launchpad.net/bugs/120302
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: cat /proc/asound/oss/sndstat
http://launchpadlibrarian.net/9189858/sndstat.txt
--
Feisty Sound not working at all on a toshiba a200 satellite has intel HDA
https://bugs.launchpad.net/bugs/120302
You received this bug notification because you are a member of Ubuntu
Bugs,
I just tried patching and building alsa as specified here:
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/116326/comments/75
No joy with either internal speakers or headphones. I can change volume
as before, and this apparently works. Everything appears to see the
card, and
65 matches
Mail list logo
