Skip to main content

eva qq in ubuntu

花了两天才弄好eva

其实学校feisty的源可以直接安装配置eva的,只是我仍在用edgy且短时内不打算升到feisty.edgy源里没有eva.我不想为此修改source.list再update,否则倒是改回来就不好整了,于是从源里下了个deb安装,不过需要依赖很多高版本的库,但是edgy源里这些库的版本号不够...

于是编译安装吧

eva 官方论坛里有个源码包下载,不过我编译后不能正常登录,说"您所在ip不能使用旧版本之类"...关于这个信息,eva的调试信息出的都是16进制的,需要用16进制编辑器写一下再看.
后来查到可以修改src/libeva/evadefines.h,这就要查QQ版本号代码了,我从飘云QQ里搞来了个列表,不过跟这个.h里的定义有很大出入,我尝试了几个均失败了.

最后终于发现我一直在犯傻 -- feisty源里也有源码下载,而且是cvs版本的,比较新.于是乎编译安装,最后,哈!能登录了!

但是开始时字体有问题,我在网上搜,说是应该改kde系统字体,用kcontrol改(一开始我看成konsole了,搞了半天,莫名其妙),这个不必多说.

这样就能正常使用了,截图功能还不错,不过截图发送有问题,传文件也不行.不知道为什么,不过也没多大关系,当初Luma时也差不多.

最后对eva开发维护者表示感谢!
Labels:

Comments

Post a Comment

Popular posts from this blog

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...
Post a Comment
Read More »

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...
Post a Comment
Read More »

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...
3 comments
Read More »