I've tried installing both ibus-anthy and ibus-mozc in Jessie but I still cannot input Japanese.
By contrast, In Wheezy, when using anthy for example, I can see ibus preferences icon where I can configure ibus and anthy. This doesn't show up in Jessie.
I'm trying out a Jessie install and have noticed VNC doesn't work as well as it used to. I often install a desktop environment on a headless machine, disable *dm, and use vnc4server to create a desktop session if I want to use a GUI. When I try to do the same on Jessie, I run into problems.
Using Gnome, all I get is the generic "Oops something went wrong" error. Looking at .xsession-errors, there are some errors that hint at the problem.
Code: Select allXsession: X session started for ryan at Mon Dec 29 06:07:30 CST 2014
X Error of failed request:Â BadValue (integer parameter out of range for operation)
 Major opcode of failed request: 109 (X_ChangeHosts)
 Value in failed request: 0x5
 Serial number of failed request: 6
 Current serial number in output stream: 8
[Code] ....
Some possibly related bugs: [URL] ...
The same thing seems to happen with Cinnamon. Since I doubt a fix for the above issue will make it into Jessie, I tried XFCE. However, that doesn't work correctly either. When running XFCE via VNC something is misreporting the version of xrandr as 1.1 instead of 1.4. Since xfsettingsd appears to want version 1.2+, many things are broken.
This post on the Ubuntu forums suggests the issue might be fixed in xfsettingsd version 4.11: [URL] .....
Is there a better way of getting a remote desktop in Jessie that I'm overlooking?
I recently install a Debian 8.0 Jessie on a Laptop Dell latitude E6540 with gnome 3.14+3. But the problem is that it doesn't recongnize my multimedia buttons, I tried some methods but I didn't get results.
Code:
Code: Select all$showkey --scancodes
volume up  -- 0xe0 0x30 0xe0 0xb0
volume down -- 0xe0 0x2e 0xe0 0xae
volume mute -- 0xe0 0x20 0xe0 0xa0
$showkey --keycodes
volume up  -- 115
volume down -- 114
volume mute -- 113
[Code] ....
When I reassinged the keys on Settings>Keyboard>Shortcuts to F7, F8 and F9 it works, but when use the keys volume up, down and mute It doesn't show anything.
The same happens with Fn + Brightness keys, in this case it worked the first time but then stop to work I don't know why..
When I installed my 64 bit system of Ubuntu 10.04 the sound worked very well and I were very happy. The problem started however when I installed Skype which uses pulseaudio. As soon as I start skype (or any other application that uses pulse, HoN for example) the applications sound output or input does not work at all. If I have pulseaudio started in some way, applications that I suppose do not use it like spotify or flash player stops to produce sounds. And when I type "pulseaudio" in the terminal it gives me this:
[Code]...
Debian configurating, so I try to use wifi adapter, but it doesn't work. I have installed Debian Jessie from netinst CD. To reach perfect speed no options were selected. After I installed xfce4 and xfce4-goodies.I follow some different instructions and no dice. Wicd show me no avalable wifi connections. used Ubuntu 14, Ubuntu 12, etc. and I didn't have any problems with wi-fi connections. Some outputs of comands...
Code: Select allsatyva@meliorD:~$ cat /etc/debian_version
8.3
Code: Select allsatyva@meliorD:~$ lspci | grep 4313
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
[code]....
I am trying to get the QL1060N to print and cut under Jessie.
I used the Ql1060N on wheezy (cups 1.5.3) with the standard Brother driver and the ptouch/foomatic driver of the QL550. They both worked out of the box.
Configuration for Brother QL1060N Driver:
Description:ql1060n
Location:
Driver:Brother QL-1060N CUPS v1.1 (grayscale, 2-sided printing)
Connection:socket://XXX:9100
[Code] ....
On Jessie (cups 1.7.5):
I first tried the standard Brother driver from here: [URL] ....It didn't work at all. When I print, Cups tells me that the job has been completed, even though nothing has been done. Sometimes I also got the error "job canceled, filter failed", but I can't reproduce this error...
The foomatic/ptouch driver for the QL550 prints like it did before, but doesn't cut the lables automatically like it used to in wheezy. (I'm using the same printing file/picture as in wheezy and also the same configuration.)
I know the problem has been partly solved in this old thread [URL] .....
Now we have Jessie as stable, yet LXDE doesn't shutdown properly:
On the same computers, Wheezy LXDE shut down very fast
I installed Jessie from the netinstall image.
On a 2007 computer, it's like the old days with a Pentium II running some version of Puppy Linux or Slitaz. The system shuts down after a while but the computer remains on.
On a 2013 laptop, I added the line init=/bin/systemd in the Grub default file as advised on the old thread above. The laptop shuts down after a while, the system first, then the hard disk goes to sleep, then all the leds are off.
If I run the magic command, the computer shutdowns in a breeze, perhaps even quicker than good old Wheezy:
Code: Select all# systemctl poweroff
Now, is this still a systemd bug? Doesn't look like it since the systemctl command works. Is it an LXDE bug? Looks like it in a way - if the LXDE shutdown button enabled the systemctl poweroff command, I suppose the button would work?
Is there a way to make the LXDE shutdown button run the systemctl poweroff command?
I'm glad Wheezy is still with us because I wouldn't install Jessie for newbies — they'd think shutdown (through clicking on a button) is even worse than in Windows.
I would like to use Japanese kana (hiragana, katakana, kanji) on Ubuntu but everything that I've tried to get it set up and running isn't working. The Spanish that I have set up is working perfectly so far.
I've read, the SCIM input program should start up automatically when loading a program, it doesn't. When I have it loaded I cannot seem to get the input working.
I had some issues with nvidia drivers, and removed all of the packages using
Code: Select allrm /etc/X11/xorg.conf and Code: Select allapt-get purge nvidia*
Upon reboot, I was back with nouveau drivers and proceeded to reinstall nvidia drivers according to [URL] .....
Code: Select allapt-get install nvidia-driver
apt-get install nvidia-xconfig
I can then change my refresh rate using
Code: Select allnvidia-settings
but when I hit "Save to X configuration file", I get the following output in terminal:
Code: Select allroot@debian:/home/anon# nvidia-settings
Package xorg-server was not found in the pkg-config search path.
Perhaps you should add the directory containing `xorg-server.pc'
to the PKG_CONFIG_PATH environment variable
No package 'xorg-server' found
As a result, my nvidia preferences aren't saved across reboot.
Here are all of my sources:
Code: Select alldeb [arch=amd64,i386] http://repo.steampowered.com/steam/ precise steam
deb-src [arch=amd64,i386] http://repo.steampowered.com/steam/ precise steam
deb http://ftp.ca.debian.org/debian/ jessie non-free contrib main Â
deb-src http://ftp.ca.debian.org/debian/ jessie non-free contrib mainÂ
[Code] ....
System Specs:
Debian GNU/Linux 8 (jessie) 64-bit
Gnome Version 3.14.1
Processor: Intel® Core™ i7-4770K CPU @ 3.50GHz × 8
Graphics: GeForce GTX 780/PCIe/SSE2
Actually I want to log a bug but I don't really know what package to log it against. The problem is that by default Pango is choosing the AR PL UMing CN as the font to render Japanese text when the current font doesn't have Japanese glyphs. But AR PL UMing CN is a Chinese font, so Chinese glyphs for kanji characters (e.g., 覚) are displayed. This is jarring and confusing for Japanese readers.
This situation mostly arises when you have mixed English and Japanese text. Some applications (for instance Firefox) will allow you to select a font for Asian text. Thus if the text contains only Asian characters it will use the font you select, rather than what Pango would have selected. But if it is a mix of English and Japanese, you end up with the wrong glyphs.
Other environments (like gnome-terminal, or a gedit) have difficulties as well. Since the primary interface requires mono spaced roman characters you run into difficulty selecting fonts. Most Japanese fonts only have proportional roman characters. This means that if use a nice roman font and use Japanese text (for instance file names), you end up with Chinese glyphs. What I want is a mechanism that will work across all of Gnome for selecting the font I want to use for Chinese characters. That way I can choose either Japanese or Chinese glyphs.
I realize this is low priority. It only bugs me a little, but many of my Japanese colleagues are put off from using Ubuntu because they are confused by the Chinese glyphs that pop up on my screen from time to time. As I said, I'd like to file a bug, but I'm not sure against what package...
I am learning japanese and I would like to be able to switch between english and japanese input while keeping an english interface. How would I achieve that? I am using KDE, by the way.
In the Kiten documentation I read that pressing Shift+Space would enable japanese input (built-in in Kiten, according to the documentation). But that does not seem to work in my system.
Yesterday my Japanese input on F11x64 broke horribly. I have been using iBus all along, and didn't think I did any upgrades, but maybe there was a restart that picked up something previous. As soon as I hit the key to turn on the input method to type Japanese there would be a python process using 100% cpu, but no keyboard input. After fiddling about reinstalling python, iBus, scim and anthy and anything I else I could think of, I decided to upgrade to F13 to see if it would fix it. (trying to use scim instead of iBus hung the machine during start-up after login (I'm using KDE too if that makes any difference)). I did an upgrade instead of a fresh install fyi...
F13 is no better, and has the same issues with the python process. I have tried reinstalling everything again, as well as trying to avoid scim altogether, and just running iBus and Anthy. (The only other issue that I can think of (that prompted the initial restart) was that my .xsession-errors file in my home directory became huge -> 1.7gb!) Japanese input is crucial to my work (It doesn't even work if the default language of the system is set to Japanese), so hope someone has some ideas on how to resolve this, or even just knowing tha japanese is working for someone on a x64 KDE install would be encouraging...
I know it is possible, and I have been trying everything I can find, but I can't seem to get it to work. I went to languages in YaST and enabled Japanese as a second language, and I have tried adding japanese as a secondary keyboard layout under configure desktop-> regional and language settings. I have a little flag in the system tray that I can click to change from US to Japanese, but all that does is change what the punctuation buttons do.
View 9 Replies View RelatedI am running KDE 4.5.1 on Ubuntu and came to Ubuntu from Windows, On Windows they have a very sophisticated Input Method for typing foreign characters especially symbolic ones like Japanese.
I find that while Linux makes a lot of things so much easier than any other system, I have yet to figure out how to get any sort of input method running on Ubuntu (KDE Desktop).
It's important for me to be able to type hiragana, katakana, and kanji as I'm learning the Japanese language. I've browsed forums for about 2 weeks giving examples on Ibus, uuim, and some others but even though Ibus works a little buggy on Gnome I really need an alternative that's works well and with the KDE desktop.
Additionally, I have never seen any method (that did or didn't work) with installing Japanese font, everybody just said it was tricky.
For years I have been using scim-anthy for Japanese input under Linux. However just moving to ubuntu 10.10 I noticed that the development for scim has ceased and lots of people recommend moving to ibus. So I tried: I got ibus and ibus-anthy installed. I choose ibus as keyboard method input system under System->Adminsitration->Language Support ibus is up and running. I can see the icon. In ibus opreferences I added anthy under Input methods. I restarted X resp. the whole computer. I can choose Japanese-Anthy when clicking on the ibus icon. But nothing happens. I am still writing latin characters, no anthy popped up (like it used with scim), nothing.
View 2 Replies View RelatedI can't seem to get Japanese input working with scim-anthy. I have scim 1.4.9 installed and the daemon running. I have the scim-anthy 1.3.1 package installed as well. I can open and modify the scim-settings, but I can't get the anthy dialog to appear. Apparently, ctrl-space should bring up the dialog, but nothing happens. I tried following the instructions on this page under "Open a program with japanese input enabled - via command line", but still no dialog. After starting the daemon, I tried:
Code: XMODIFIERS='@im=SCIM' LC_CTYPE=en_US.UTF-8 gvim And no luck. Note that I don't really understand what that command is supposed to do. Should it be something different?
Anyone knows a good input method for japanese writing in openSuSE 11.2 ? I tried to find something that works well (like microsoft IME) but unfortunately couldn't find anything...
View 3 Replies View RelatedI can't input Japanese charactersn KWriteough the input works in all other applications as far as I know). Does anyone have an idea what the cause might be, or what I should be looking at?The point is not that can't see the characters (but e.g. gibberish instead), but that the characters that I type in the input bar are not transfered into KWrite upon commit.
View 1 Replies View RelatedBefore I upgraded to Karmic, I had Japanese text input set up on my system, but since the upgrade it no longer works. I can still read Japanese text, and when I press Ctrl+SPACE I still get the ANTHY box in the bottom right-hand corner, but Japanese is no longer on the list of supported languages. how to get Japanese back?
View 1 Replies View RelatedI have installed VirtualBox and since then resuming from hibernation doesn't work again (my previous thread: [URL] ....). My question is: Can VirtualBox kernel modules (vboxpci, vboxnetadp, vboxnetflt, vboxdrv) break hibernation? If yes, what to do? Maybe unload them before hibernation, blacklist when resuming and load after resume? And how to do that with systemd? URL....
View 4 Replies View RelatedI installed the adobe plugin, and my browser crashes. I uninstalled it, and installed the one in the apt repository (mozilla-plugin-gnash) and it shows up in my about: plugins in iceweasel, but flash just doesn't play.
View 4 Replies View RelatedI'm running newest pidgin on sid and i have few problems. First of all notifications doesn't work (plugin is of course turned on), also even when i turn on blinking icon it's not blinking. Oh and why the tray icon is so small now?
View 1 Replies View RelatedI have problems with xrandr in a system with Nvidia GeForce 8600GT video card. I want to use xrandr to rotate the screen on the fly.
~:$ xrandr -q
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 320 x 175, current 1600 x 1200, maximum 1600 x 1200
default connected 1600x1200+0+0 0mm x 0mm
1600x1200 50.0*
1600x1024 51.0
[Code]....
I tried enable the last option, change values for xinerama and twinview, but nothing works.
Just as the title says: I installed iceweasel 6 in debian squeeze (via mozilla.debian.net) and while errors and requests are captured in the web console, I simply cannot use it to evaluate arbitrary javascript I type in it.
Does anyone have this problem as well? It's been like this since v5 as well. I already tried purging and reinstalling, as well as running with another profile.
I am having trouble getting evolution to work properly with my imap server. It won't show any messages. Icedove works fine, though. I'd rather use evolution because of the calendar. I'm not sure what I am doing wrong. The IMAP server is hosted by network solutions. I have screenshots of both clients. I've blacked out a few things for privacy.
Here are screenshots of evolution as configured:
Here are screenshots of icedove's configuration:
I just got a new Dell monitor (U2715H), and even with beta Nvidia driver (355.06) on Debian testing x86_64, it doesn't detect highest resolution (2560x1440) when connected over HDMI to Nvidia Geforce GT 620. I have an HDMI 2.0 compliant cable, and according to Dell reps, the monitor should support 2560x1440 over HDMI.
Some suggested using xrandr to set the video mode explicitly. I tried doing it, and first got a EDID file with nvidia-settings, and run edid-decode. Where is what I got there:
Code: Select allDetailed mode: Clock 241.500 MHz, 597 mm x 336 mm
        2560 2608 2640 2720 hborder 0
        1440 1443 1448 1481 vborder 0
        +hsync -vsync
So I used those values to make a new mode in xrandr:
Code: Select allxrandr --newmode "2560x1440_60.00"Â 241.50Â 2560 2608 2640 2720Â 1440 1443 1448 1481 +hsync -vsync
xrandr --addmode HDMI-0 "2560x1440_60.00"
But I got this error:
Code: Select allX Error of failed request:Â BadMatch (invalid parameter attributes)
 Major opcode of failed request: 140 (RANDR)
 Minor opcode of failed request: 18 (RRAddOutputMode)
 Serial number of failed request: 31
 Current serial number in output stream: 32
not sure exactly when this broke, but for some reason I'm not able to use CTRL-ALT-F1 anymore to fall back to the first virtual console.I can kill X with CTRL-ALT-BACKSPACE just fine, but I'd like to be able to get a normal shell to kill things when I've messed too much with graphical stuff.
View 4 Replies View RelatedAfter upgrading to gnome 2.28.2 and Nautilus 2.28.4, nautilus leaves text file(including .php .jave etc,.) icon blank while it works well with image and pdf files.
gnomevfs-info asd
Name : asd
Type : Regular
MIME type : application/octet-stream
Size : 27433
Not showing "Default app" but automatically opened by gedit. I am sorry but I don't really know what info matters. So tell me what info I should post here.
Every time I boot my machine, some of the playback values in alsamixer are set to 0 and are muted, so I have no sound.
The thing is, I have tried setting these to normal levels and then run sudo alsactl store. Then, if I run sudo alsactl restore after I reboot, the sound comes back up. However, if I have alsactl restore in /etc/rc.local, it doesn't work: I still get muted sound when I reboot. I have to run sudo alsactl restore manually each time.
I have already checked whether /etc/rc.local runs at startup, and it does. Also, I know that /var/lib/alsa/asound.state contains the correct values, because when I run sudo alsactl restore, the sound returns to normal levels. So what remains is either alsactl restore doesn't work in /etc/rc/local, or something runs after it and mutes the sound.
I have some troubles with my microphone.I can hear it in ootput if I knock on it or speak, but I can't record from mic. It also does not work in skype.cant figure out what is the problem.
View 5 Replies View Related