LMDE BREAKAGES - (Tracking SID!) -{CLOSED}
Forum rules
LMDE 2 has reached end of support as of 1-1-2019
LMDE 2 has reached end of support as of 1-1-2019
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
Me too, me too! I took the install I set up to test UP5 and upped it to Sid yesterday. Still working great even with the Mint preferences file in place. It's like a real LMDE Sid machine
Wonder how long that will last? Probably longer than me. I know I'll rebuild it some other way within a week. I'm a Linux junkie I tell ya!
Wonder how long that will last? Probably longer than me. I know I'll rebuild it some other way within a week. I'm a Linux junkie I tell ya!
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
Keep an eye on that squeezy. I think it may cause some upgrade problems in the future.squeezy wrote:...............Still working great even with the Mint preferences file in place.............
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
Yeah, no doubt about that...if I can keep from installing something else within a few days
I really should partition this drive to accommodate multiple installations. There's definitely stuff I keep coming back to that I could leave in place.
GeneC, you run multiple setups on your machine I see. What's your partitioning scheme? I've got an 80 GB drive I dedicate to playing with Linux. I ought to be able to hold 2-3 installations. I'm pretty much a hobbyist user so don't need a ton of space.
I really should partition this drive to accommodate multiple installations. There's definitely stuff I keep coming back to that I could leave in place.
GeneC, you run multiple setups on your machine I see. What's your partitioning scheme? I've got an 80 GB drive I dedicate to playing with Linux. I ought to be able to hold 2-3 installations. I'm pretty much a hobbyist user so don't need a ton of space.
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
Interesting. I see only one partition is marked bootable. I would have thought all the partitions holding an OS would be bootable, or can you only have one bootable partition?
I'm going to try this. How do you handle grub installs? Do you bypass it on all but one install?
I'm going to try this. How do you handle grub installs? Do you bypass it on all but one install?
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
SDA1 is where grub is installed.
When I install a new or re-install a clone to another partition,
EDIT: (Orig info was incorrect).
I will go into SDA6 and run
This puts the grub config from sda6 back to sda1(where the mbr is).
(I customize with grub customizer).
Not unnecessary, but I like to keep things 'neat'
When I install a new or re-install a clone to another partition,
EDIT: (Orig info was incorrect).
I will go into SDA6 and run
Code: Select all
sudo grub-install /dev/sda
(I customize with grub customizer).
Not unnecessary, but I like to keep things 'neat'
Last edited by GeneC on Fri Aug 03, 2012 12:59 pm, edited 3 times in total.
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
Yeah, I like things neat, too
OK, I'm off to repartition my drive!
OK, I'm off to repartition my drive!
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
Hmm.
After thinking about it. The info about MOVING grub was incorrect.
I edited the post above to clarify.
I believe grub is always on SDA1 , no matter what partition it was last installed from (as long as you choose that option when grub is installed), as I believe that is where the MBR is located.
Now I have totally confused both of us.....
Using the command I gave just changes the grub config to whatever the setup is on the partition (sda1, 2, 3... et) you choose.
In any event its not an issue. It does work...
After thinking about it. The info about MOVING grub was incorrect.
I edited the post above to clarify.
I believe grub is always on SDA1 , no matter what partition it was last installed from (as long as you choose that option when grub is installed), as I believe that is where the MBR is located.
Now I have totally confused both of us.....
Using the command I gave just changes the grub config to whatever the setup is on the partition (sda1, 2, 3... et) you choose.
In any event its not an issue. It does work...
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
Well, I'm back with my new multi-partitioned disk I chose LMDE as the main distro that I'll not remove. I put a UP4 install on right now, thinking I'll always use the current stable LMDE offering here. Now, what else can I tinker with. A SID MATE install looks tempting right now
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
tks Gene, things in testing aren't exactly moving fast as you know
and tbh this should be a relatively safe install:
- no gnome-stuff whatsoever; it was a debian squeeze lxde install where i configured xfce and in this couple months has been updated first to testing and yesterday to sid;
- no networkmanager; wicd works here very well;
- no proprietary graphics drivers; just a good old intel GM45;
with this said, i know that sid is sid and one day KABOOM something will break and badly;
what i'm particularly watching here:
- as always xorg/mesa/kernel (we never know when/if the next one is gonna be a good one) and the issues with 3.5 kernel tho apparently already spotted are not very reassuring;
- the upcoming xfce 4.10 (it's still broken in experimental), so let's see how debian handles this transition;
- in a more trivial note: i still use Marillat repo (deb-multimedia) and also is a factor to watch, specially now that he was forced to drop the use of the name debian in his site;
and now the mandatory screenie
bare in mind 2 things:
-this was supposed to be a dual-boot setup (last year when i got this box) yeahh right
- this xfce is not here (is in the laptop)
and tbh this should be a relatively safe install:
- no gnome-stuff whatsoever; it was a debian squeeze lxde install where i configured xfce and in this couple months has been updated first to testing and yesterday to sid;
- no networkmanager; wicd works here very well;
- no proprietary graphics drivers; just a good old intel GM45;
with this said, i know that sid is sid and one day KABOOM something will break and badly;
what i'm particularly watching here:
- as always xorg/mesa/kernel (we never know when/if the next one is gonna be a good one) and the issues with 3.5 kernel tho apparently already spotted are not very reassuring;
- the upcoming xfce 4.10 (it's still broken in experimental), so let's see how debian handles this transition;
- in a more trivial note: i still use Marillat repo (deb-multimedia) and also is a factor to watch, specially now that he was forced to drop the use of the name debian in his site;
and now the mandatory screenie
bare in mind 2 things:
-this was supposed to be a dual-boot setup (last year when i got this box) yeahh right
- this xfce is not here (is in the laptop)
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
Keep an eye on the Aptosid forum. They are on top of breakages in SID.zerozero wrote:....with this said, i know that sid is sid and one day KABOOM something will break and badly;
what i'm particularly watching here:
- as always xorg/mesa/kernel (we never know when/if the next one is gonna be a good one) and the issues with 3.5 kernel tho apparently already spotted are not very reassuring;...
http://aptosid.com/index.php?name=PNphp ... c27c096455
I've upgraded to 4.10 from experimental twice and was disappointed, as it doesn't seem to be all there yet. Debian is slow on this one....- the upcoming xfce 4.10 (it's still broken in experimental), so let's see how debian handles this transition;...
Well... something to look forward too, I guess....
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
No breakages here with the main Xfce 4.10 packages. The only issue I've noticed is with auxiliary packages not being upgraded, such as xfce4-mixer.zerozero wrote:the upcoming xfce 4.10 (it's still broken in experimental)
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
I have OpenArena and updating my system (while pointing to sid correctly) caused the skybox to turn black - it rendered incorrectly although the game was still playable.
This is the solution that I found that worked:
1. Use any editor to open ~/.openarena/baseoa/q3config.cfg
2. Look for seta r_fastsky
3. If it has a setting of "1", change it to "0". It should look like this:
seta r_fastsky "0"
The skybox should then render correctly (i.e. not black).
This is the solution that I found that worked:
1. Use any editor to open ~/.openarena/baseoa/q3config.cfg
2. Look for seta r_fastsky
3. If it has a setting of "1", change it to "0". It should look like this:
seta r_fastsky "0"
The skybox should then render correctly (i.e. not black).
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
Nodejs and Npm are broken today, can anyone confirm?
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
QT4 updates coming through that have caused havoc on my multi-arch system. Might be worth sitting for a few days.
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
No problems here, but my machine arch is x64. Will log into KDE, but all qt programs that I use in Cinnamon are OK (qBittorent, smplayer etc).GregE wrote:QT4 updates coming through that have caused havoc on my multi-arch system. Might be worth sitting for a few days.
Steve
:Edit: Sorry for the delay! Been playing with KDE and lost track of time, all working, no problems to report.
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
The qt problem is with one lib (libqt4-network:i386) and Skype:386 on a multi-arch system. I would think it will clear when the updates are all through both archs.
Only going to affect two of us here
Only going to affect two of us here
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
Here everything seems ok with multi-arch system.
Re: LMDE BREAKAGES - (Tracking SID!) - Jul 19th
It is only some programs that have issues. For me I have lost Skype. Wine and Picasa are working fine. It is a conflict between bits of QT in the multi-arch system. There has been a bug filed, so if you are affected it is a "wait and see:" issue.Regulus74 wrote:Here everything seems ok with multi-arch system.
https://groups.google.com/forum/?fromgr ... %5B1-25%5D
Luckily I hardly use Skype so I do not care that much.
I will keep checking and report back when it is fixed.