Slackware :: Abiword Broken After Upgrading 13.0 To 13.1?
Feb 25, 2011
After upgrading I also updated abiword and wv from slackbuilds.It complains it can't find libwv-1.2.so.3, although libwv-1.2.so.4 exists.Making a symbolic link gets it to start, although then it complains about libpng and hwile it starts the toolbar icons are not displayed, instead with red X's in their place.What is needed to get abiword easily working on 13.1?
I avoided upgrading to 10.04 when it was initially released because I couldn't afford for anything to go wrong with my computer around exam time. Sure enough, when I decided to upgrade today, the process got about halfway through and then gave me an error and left me with an unbootable system except in a recovery terminal.
In this terminal I discovered that most of the packages the upgrade wanted to configure depended in some way on shared-mime-info or desktop-file-utils. Configuring these with dpkg --configure gives me an error along the lines of:
Code: undefined symbol: g_malloc0_n and an error code of 127. So, dpkg leaves those packages and consequently can't configure many of the subsequent packages in the dist-upgrade.
I've just upgraded to the 11.04 beta, everything working fine to start with (apart from not being able to find anything in the new interface!), but now, a few days later, the nfs mounts to my NAS are broken. I've had a quick go at manually mounting; for instance, if I try to mount 192.168.1.1/Public to /home/Public (where it usually is) it says that the mount point doesn't exist. It's not true, I can see it, and if I test it by trying a mkdir it confirms it. This is a pretty big deal, I've got ALL my stuff on the NAS. I can still see it from my phone and the web interface of the NAS, so I know it's there...Should I just re-install 10.10 and be patient until the final release comes out?
I just upgraded to Ubuntu 10.04 from 9.10 and now my Windows XP will not boot from grub. It shows up on the grub boot list but when I select it, all I get is a black screen. It worked perfectly just minutes before the upgrade, but now I cannot use windows, which I need really badly at this point.
I was upgrading from 9.X (can't remember what X is) to I believe it was 10.2 (ok, this happened over a month ago and I just haven't had the time to run after it), and lost power. Obviously doesn't sound good, right? Now when I boot I get the message "alloc magic is broken at 0xaff2c150". I have no idea if this error message is indicative of the whole problem, or what, but I can't get back to my system. I would really rather not lose my work.
I was recently watching an avi file, when suddenly, my tower (the computer) got really, really noisy. That's pretty normal when I'm on my Windows side, but very unusual for Ubuntu Linux. I knew something was in the wind then and there. So I exit my Dragon Player to discover that ! gasp ! KDE is down, replaced with the default wallpaper for GNOME, and no bars anywhere. I reset the system only to find that it refuses to boot into either KDE or GNOME. Having been in something similar to this situation before, I decide that Xorg.conf must be broken somehow. In an effort to get to the GUI where I can safely edit it, I try reinstalling KDE and GNOME, which both failed.
So I try installing xdm...which results in only being able to access the login screen for XFCE. Whenever I try to log in using the correct credentials, it simply refreshes the log-in screen.
1. Is this, indeed, the sign of a broken Xorg.conf, or a broken Xserver in general? Or is there something larger that was changed?
2. How do I fix this? (I've already tried using Ubuntu 10.10 64 in rescue mode, but I can't seem to change anything in the system itself.)
3. Is this possibly a result of upgrading straight from 10.04? Is it possible that having both KDE and GNOME contributed to this?
I've upgraded Slackware-13.1 I had installed to Slackware-Current using a local tree I had download with mirror-slackware-current.sh script, but when I rebooted I could not get the graphics to load. I think it's because I've also modified /etc/groups and add an username after audio: and video: group, but I forgot that and had to remove slackware from the machine.
Some time in the past after upgrading from one version of Slackware to another, I remember having issues using the previous version's .kde directory. This was remedied by removing that directory and letting KDE recreate it followed by me painstakingly migrating files one by one to get all my settings, mail, etc. under the new version of KDE. Is this the case with the upgrade from 13.1 to 13.37 and is there a better way that I'm missing?!
I just installed slackware, and I configured it to automatically boot into x without first checking to make sure x would work. I started X, and I'm not quite sure what's wrong with it, but it's messed up, and I don't know how to get out of it
I'm trying to upgrade KDE from 4.2 to 4.3 since I encountered couples of problem with it and some people suggested me to upgrade it to 4.3.
Questions: 1. Is KDE 4.3 available in 64 bit? 2. KDE consists of bunch of packages, what is the best way to start? Should I uninstall the whole current packages in my machine and then install the new ones? 3. Using pkgtool, how do I know if I remove the whole KDE packages? Are all KDE packages named that begin with word "KDE"? 4. How to do this safely so to avoid corrupting the system?
I have some doubts about the official Pat's upgrading procedure. In the UPGRADE.TXT file, one of the stepts says:
Code: upgradepkg --install-new *.t?z What does --install-new mean? Pkgs I have no installed on my 13.1 will be installed on the 13.37 upgrade? For example, I did not installed KDE on 13.1. Will be installed when upgrade? - What about third party pkgs? Slacky, SlackBuilds.org, compiled by myself. Should I remove them before upgrading slack?
procedure or instructions on how to reinstall the X server or upgrade it to the latest? Every time I played around with X I screwed up things good... I think it got corrupted and I have display problems that I cant fix, so far everything points to a software problem, probably X server...If you need more background info:
1. Upgrade the kernel and kernel-modules packages normally.
That sounds simple except that day-to-day, I don't run a stock Slackware kernel. I compile and run my own and always have. As I look back on my history with Slackware, I don't think I've ever upgraded kernel packages once I got a system up and running. When there's been big changes (2.4 to 2.6, for example), I've done a full re-install.
Most recently when I made the jump to 64bit, I did a full install using the huge.s kernel and once everything worked, I downloaded the current source from kernel.org and was on my way. I haven't booted huge.s since that day.
I do, of course, know how to upgrade my own custom kernel, but I like having huge.s installed as a backup. If I upgrade gcc/glibc, compile a new custom kernel and update lilo.conf/fstab without upgrading huge.s, then I will be left with only one working kernel.
So, my question is: is it simply a matter of running upgradepkg on the 6 kernel packages (headers, modules, firmware, generic, huge and source)? or is there more to it than that..ie, what about the system maps and symlinks in /boot?
I'm looking at running -current instead of 13.1, and wondering about 'upgrading' to -current, as well as running multi-lib. I found the following procedures from another post of about a year ago, but I'm not sure from what directory to run such a script:
Should the procedures above work for me? and although I know that things may occasionally break here and there (and get fixed too), are there any known issues right now that would break things on my machine?
I have a weird bug : segmentation fault appears when executing the 'retq' instruction of my sigalrm callback in static link...It seems it happens only on slackware...Here is a simple test case, compiled in shared -> no problem, static -> crash...Paste the following script in a file named "test-sigalrm-pack2.sh", and execute it: it will generate the C++ source and a simple build/test script.... Just launch the build script (tst-sigalrm-build).
I can't think what i've done to make my sound suddenly pack in. One minute all is working well, then its not anymore. The only thing I did in between was install claws-mail yesterday. This evening an error mssage popped up and now no sound.
My card is HDA Intel; The error when i open Kmixer is -
GStreamer was unable to detect any sound devices. Some sound system specific GStreamer packages may be missing. It may also be a permissions problem.
Does anyone have current running with X on old ATI hardware? I have a laptop with ATI Mobile M7 and X completely fails to load. There are no errors in the Xorg log file. No failed modules or failure to load a module. The last line in the Xorg log says something to the effect of "VGA0 does not support DRI2".
When monitoring the processes while I start X, I can see xinit load, then X. After the line above is added to the log file, X dies. This is so bad that it takes my entire display with it so I cannot switch terminal. I cannot restart a tty session from a remote connection. The only way to get the display back is to reboot.
I tried the suggestions form this thread to no avail. Recompiling the kernel with "CONFIG_PREEMPT_NONE=y" also had no effect. To get a working system I had to roll back to X from Slack 13, which works fine with current.
Did i missed something with the upgrade? Anything else I should try?
Code: Slackware-current 32 (with X from Slackware 13) Kernel: generic-smp-2.6.33-smp 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
after i update to -current a few days ago. my slack partition cannot be mounted...and after that it's show 'kernel panic'.before i experience that problem, i have encounter an odd problem after i update my slack to -current, after i lock my screen and i want to unlock it, i cannot unlock it, it says 'i must kill kscreenlocker manually'. After that i reboot using root account. then i cannot enter my slackware again.kernel panic in boot screen.Kernel panic: VFS : Unable to mount root fs (8,2)
I've just moved all my machines from Ubuntu to Squeeze and am currently trying to remove Open Office. When marking for removal and uninstalling OO the package manager requires that AbiWord and associated suite of office apps be installed as a replacement. I would like to completely purge both as I have little to no need for them, and the little I do use a word processor for I tend to use cloud based solutions. Is there a way to resolve the dependency that seems to exist that requires one or the other to be on the system at any given time?
I've recently upgraded from Slackware 12.2 to Slackware 13.0 and so far everything works fine with one exception: the TightVNC package that comes with Slackware-13.0 (in /extra) produces a garbled desktop. Applications look fine, but the default desktop of 13.0 is corrupted. Restarting the VNC server doesn't solve the problem. Before the upgrade, I had 1.3.9 compiled from source. I have just installed the 1.3.10 package that came with Slack-13.0 on top of what was there, hoping it would overwrite old files as needed (couldn't find an automatic uninstall procedure for 1.3.9).
I have attached a printscreen. Notice the taskbar and the top left quarter of the screen. Firefox seems to be rendered properly though. Has anyone encountered this before or may have a clue what could be causing it?