1 Jun
2013
1 Jun
'13
10:52 p.m.
Please forgive me if these questions is already answered:
(Ubuntu Studio 12.10 32-bit on Toshiba Sattelite p850 laptop)
It seems that after the last updates my machine is now running the
generic kernel 3.5.0-33 by default. This seems to have broken JACK,
which was running without problems for a long time. So I have the
following questions:
- How do I "downgrade" so that the 3.5.0-31-lowlatency kernel becomes my
default setting?
- Why does Ubuntu Studio bother with the generic kernel anyway?
Thankful for any and all input!
Al F
2 Jun
2 Jun
12:24 a.m.
On Sat, 01 Jun 2013 22:52:18 +0200, Alf Haakon Lund wrote:
Please forgive me if these questions is already
answered:
(Ubuntu Studio 12.10 32-bit on Toshiba Sattelite p850 laptop)
It seems that after the last updates my machine is now running the
generic kernel 3.5.0-33 by default. This seems to have broken JACK,
which was running without problems for a long time. So I have the
following questions:
- How do I "downgrade" so that the 3.5.0-31-lowlatency kernel becomes my
default setting?
I'm using Ubuntu Studio 13.04, so it may be different on yours, but
the old kernels are not deleted and you can choose an older one from
the list you see after pressing the Grub menu second entry 'Advanced
options for ubuntu'. If the one you want is there - you can make Grub
use it as the default by editing (as root/sudo) /etc/default/grub
Change the line which says GRUB_DEFAULT="0" to GRUB_DEFAULT="1>3"
but you'll need to change the "3" to reflect how far down the list
of bootable entries it appears in the list - and, bear in mind, 0
is the first.
In other words - to boot the entry on the 4th line it would be "1>3"
Then run 'update-grub' and you should get the kernel you want on the
next re-boot. Tap the Shift key during boot if you don't usually see
any Grub options.
Hoping it helps.
--
John.
1:32 a.m.
On Sat, June 1, 2013 1:52 pm, Alf Haakon Lund wrote:
Please forgive me if these questions is already
answered:
(Ubuntu Studio 12.10 32-bit on Toshiba Sattelite p850 laptop)
It seems that after the last updates my machine is now running the
generic kernel 3.5.0-33 by default. This seems to have broken JACK,
which was running without problems for a long time. So I have the
following questions:
- How do I "downgrade" so that the 3.5.0-31-lowlatency kernel becomes my
default setting?
Remove any package with generic in it's name. (should be 3):
linux-image-3.5.0-33-generic, linux-headers-3.5.0-33-generic and
linux-image-extra-3.5.0-33-generic.
You may also want to remove (if they are installed):
linux-generic, linux-headers-generic, linux-image-generic, linux, linux
image, etc. I can't remember which ones the upgrader uses to point to the
latest generic kernel. However, if you leave them installed, they may pull
in the next new generic kernel again.
- Why does Ubuntu Studio bother with the generic
kernel anyway?
They don't. The upgrader is not a UbuntuStudio Project and seems to break
some things in UbuntuStudio. A fresh install just has the low latency
kernel... at least any of the UbuntuStudio versions I have tried ... all
of them from 12.04 to 13.10alpha. I, personally, have had other issues
with upgrades in Ubuntu Studio as well. Reinstall is best. (but then I
have been doing fresh installs since SlackWare 0.9.* or so... maybe I
should come out of the dark ages?)
--
Len Ovens
www.OvenWerks.net
3:28 a.m.
On 02. juni 2013 01:32, Len Ovens wrote:
On Sat, June 1, 2013 1:52 pm, Alf Haakon Lund wrote:
Thank you! Makes me wonder how the generic kernel entered my system,
then, but not enough to investigate! I'll just remove the generics...
As for upgrade vs fresh install I never managed one successful upgrade
(OK, maybe I tried just twice ;-) ) so I prefer the fresh install.
Though I've broken a bone or two by leaving all the config files on my
home partition and then installing on the root partition. WOW, can it
break things...
Please forgive me if these questions is already
answered:
(Ubuntu Studio 12.10 32-bit on Toshiba Sattelite p850 laptop)
It seems that after the last updates my machine is now running the
generic kernel 3.5.0-33 by default. This seems to have broken JACK,
which was running without problems for a long time. So I have the
following questions:
- How do I "downgrade" so that the 3.5.0-31-lowlatency kernel becomes my
default setting?
Remove any package with generic in it's name. (should be 3):
linux-image-3.5.0-33-generic, linux-headers-3.5.0-33-generic and
linux-image-extra-3.5.0-33-generic.
You may also want to remove (if they are installed):
linux-generic, linux-headers-generic, linux-image-generic, linux, linux
image, etc. I can't remember which ones the upgrader uses to point to the
latest generic kernel. However, if you leave them installed, they may pull
in the next new generic kernel again.
- Why does Ubuntu Studio bother with the generic
kernel anyway?
They don't. The upgrader is not a UbuntuStudio Project and seems to break
some things in UbuntuStudio. A fresh install just has the low latency
kernel... at least any of the UbuntuStudio versions I have tried ... all
of them from 12.04 to 13.10alpha. I, personally, have had other issues
with upgrades in Ubuntu Studio as well. Reinstall is best. (but then I
have been doing fresh installs since SlackWare 0.9.* or so... maybe I
should come out of the dark ages?)
11:40 a.m.
On 06/01/2013 03:28 PM, Alf Haakon Lund wrote:
On 02. juni 2013 01:32, Len Ovens wrote:
I've tried upgrading Ubuntu from one version to the next, and pretty
much had no success. So with Ubuntu, I prefer a fresh install.
Debian's been no problem at all with upgrades. Even successfully changed
from stable to sid once simply by changing my repositories.
Upgraded Sid on my desktop machine today, 440+ upgraded packages, and it
works flawlessly.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
On Sat, June 1, 2013 1:52 pm, Alf Haakon Lund wrote:
Thank you! Makes me wonder how the generic kernel entered my system,
then, but not enough to investigate! I'll just remove the generics...
As for upgrade vs fresh install I never managed one successful upgrade
(OK, maybe I tried just twice ;-) ) so I prefer the fresh install.
Though I've broken a bone or two by leaving all the config files on my
home partition and then installing on the root partition. WOW, can it
break things... Please forgive me if these questions is already
answered:
(Ubuntu Studio 12.10 32-bit on Toshiba Sattelite p850 laptop)
It seems that after the last updates my machine is now running the
generic kernel 3.5.0-33 by default. This seems to have broken JACK,
which was running without problems for a long time. So I have the
following questions:
- How do I "downgrade" so that the 3.5.0-31-lowlatency kernel becomes my
default setting?
Remove any package with generic in it's name. (should be 3):
linux-image-3.5.0-33-generic, linux-headers-3.5.0-33-generic and
linux-image-extra-3.5.0-33-generic.
You may also want to remove (if they are installed):
linux-generic, linux-headers-generic, linux-image-generic, linux, linux
image, etc. I can't remember which ones the upgrader uses to point to the
latest generic kernel. However, if you leave them installed, they may
pull
in the next new generic kernel again.
- Why does Ubuntu Studio bother with the generic
kernel anyway?
They don't. The upgrader is not a UbuntuStudio Project and seems to break
some things in UbuntuStudio. A fresh install just has the low latency
kernel... at least any of the UbuntuStudio versions I have tried ... all
of them from 12.04 to 13.10alpha. I, personally, have had other issues
with upgrades in Ubuntu Studio as well. Reinstall is best. (but then I
have been doing fresh installs since SlackWare 0.9.* or so... maybe I
should come out of the dark ages?)
2:06 p.m.
On 02/06/13 17:40, david wrote:
On 06/01/2013 03:28 PM, Alf Haakon Lund wrote:
... with more than a little help from that team of a dozen or so guardian angels
behind the scenes in aptosid, managing that small repository of fixes and apt
hold-backs, and making sure their kernel is ready for use so your life is easier
... the way it should be. But your upgrade to sid wasn't with them I guess.
I certainly hope they continue this work, I have been using their system since
they did this work at kannotix 7 years ago, when etch was sid. I had naively
made some choices of hardware that I didn't realise were bold (to put it mildly)
for linux and theirs was the only installer that could boot it. A very big
learning curve on that project, but I got there. I can confirm they do a very
good job.
Simon
On 02. juni 2013 01:32, Len Ovens wrote:
I've tried upgrading Ubuntu from one version to the next, and pretty much had no
success. So with Ubuntu, I prefer a fresh install.
Debian's been no problem at all with upgrades. Even successfully changed from
stable to sid once simply by changing my repositories.
Upgraded Sid on my desktop machine today, 440+ upgraded packages, and it works
flawlessly.
On Sat, June 1, 2013 1:52 pm, Alf Haakon Lund wrote:
They don't. The upgrader is not a UbuntuStudio Project and seems to break
some things in UbuntuStudio. A fresh install just has the low latency
kernel... at least any of the UbuntuStudio versions I have tried ... all
of them from 12.04 to 13.10alpha. I, personally, have had other issues
with upgrades in Ubuntu Studio as well. Reinstall is best. (but then I
have been doing fresh installs since SlackWare 0.9.* or so... maybe I
should come out of the dark ages?)
Thank you! Makes me wonder how the generic kernel entered my system,
then, but not enough to investigate! I'll just remove the generics...
As for upgrade vs fresh install I never managed one successful upgrade
(OK, maybe I tried just twice ;-) ) so I prefer the fresh install.
Though I've broken a bone or two by leaving all the config files on my
home partition and then installing on the root partition. WOW, can it
break things... 
6:55 p.m.
On Sun, Jun 02, 2013 at 08:06:25PM +0800, Simon Wise wrote:
I certainly hope they continue this work, I have been
using their
system since they did this work at kannotix 7 years ago, when etch
was sid.
Just a small nitpick, but etch has never been sid. Sid will always be
sid (or unstable). It is the testing distribution which gets the code
name.
Jessie is the code name for the current testing, and in about 2.5 - 3
years time it will become the new stable.
--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X
5:06 p.m.
On Sun, June 2, 2013 2:40 am, david wrote:
I've tried upgrading Ubuntu from one version to
the next, and pretty
much had no success. So with Ubuntu, I prefer a fresh install.
Debian's been no problem at all with upgrades. Even successfully changed
from stable to sid once simply by changing my repositories.
Upgraded Sid on my desktop machine today, 440+ upgraded packages, and it
works flawlessly.
Good to know. I am not sure what debian's release schedule is, but the
freeze seems to be a lot longer than Ubuntu does. That would give more
time for testing. Also UbuntuStudio is a) a very small team. b) a very
different install. That is, the mix of applications and their attached
libs is greater than any other ubuntu.
I have found it very frustrating that something simple like a video player
needs to be switched almost every release to find one that works. I would
like to concentrate the creative SW, but find that the basic desktop needs
fixing more often.
I am quite excited though, about the idea of dropping Studio on top of any
Ubuntu flavour. A small installer would allow the user to choose just the
workflow they want and install that and the lowlatency kernel. It would
also install a more organized menu for the creative workflows (I used to
have a "multimedia" menu that I had to scroll all over to find anything)
For those DEs that still think in those terms (and are XDG compliant).
For those interested, the menu package should work well on any distro,
ubuntu or not, so long as it uses the XDG style of doing menus. Unity and
Gnome Shell are the noted ones that don't really think in terms of menus
any more. I think Gnome Shell does have a menu option though. Unity does
not and besides it seems Unity has proven not to amiable to audio use for
many people anyway. When I have it finished and tested, I will post the
download site.
--
Len Ovens
www.OvenWerks.net
6:26 p.m.
On 02. juni 2013 17:06, Len Ovens wrote:
On Sun, June 2, 2013 2:40 am, david wrote:
That sounds like a terrific idea! Meanwhile, anybody here who can give
some short starting hints on how to configure debian for audio? Decided
I want to give it a go as I'm anyway set to repartition and test Ubuntu
Studio 13.04.
I've tried upgrading Ubuntu from one version
to the next, and pretty
much had no success. So with Ubuntu, I prefer a fresh install.
Debian's been no problem at all with upgrades. Even successfully changed
from stable to sid once simply by changing my repositories.
Upgraded Sid on my desktop machine today, 440+ upgraded packages, and it
works flawlessly.
Good to know. I am not sure what debian's release schedule is, but the
freeze seems to be a lot longer than Ubuntu does. That would give more
time for testing. Also UbuntuStudio is a) a very small team. b) a very
different install. That is, the mix of applications and their attached
libs is greater than any other ubuntu.
I have found it very frustrating that something simple like a video player
needs to be switched almost every release to find one that works. I would
like to concentrate the creative SW, but find that the basic desktop needs
fixing more often.
I am quite excited though, about the idea of dropping Studio on top of any
Ubuntu flavour. A small installer would allow the user to choose just the
workflow they want and install that and the lowlatency kernel. It would
also install a more organized menu for the creative workflows (I used to
have a "multimedia" menu that I had to scroll all over to find anything)
For those DEs that still think in those terms (and are XDG compliant).
For those interested, the menu package should work well on any distro,
ubuntu or not, so long as it uses the XDG style of doing menus. Unity and
Gnome Shell are the noted ones that don't really think in terms of menus
any more. I think Gnome Shell does have a menu option though. Unity does
not and besides it seems Unity has proven not to amiable to audio use for
many people anyway. When I have it finished and tested, I will post the
download site.
10:10 p.m.
For general playback of audio or for audio production and composing music ?
On Sun, June 2, 2013 5:26 pm, Alf Haakon Lund wrote:
On 02. juni 2013 17:06, Len Ovens wrote:
~~~
Home site - http://djbarney.org
On Sun, June 2, 2013 2:40 am, david wrote:
That sounds like a terrific idea! Meanwhile, anybody here who can give
some short starting hints on how to configure debian for audio? Decided
I want to give it a go as I'm anyway set to repartition and test Ubuntu
Studio 13.04.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
I've tried upgrading Ubuntu from one version
to the next, and pretty
much had no success. So with Ubuntu, I prefer a fresh install.
Debian's been no problem at all with upgrades. Even successfully
changed
from stable to sid once simply by changing my repositories.
Upgraded Sid on my desktop machine today, 440+ upgraded packages, and
it
works flawlessly.
Good to know. I am not sure what debian's release schedule is, but the
freeze seems to be a lot longer than Ubuntu does. That would give more
time for testing. Also UbuntuStudio is a) a very small team. b) a very
different install. That is, the mix of applications and their attached
libs is greater than any other ubuntu.
I have found it very frustrating that something simple like a video
player
needs to be switched almost every release to find one that works. I
would
like to concentrate the creative SW, but find that the basic desktop
needs
fixing more often.
I am quite excited though, about the idea of dropping Studio on top of
any
Ubuntu flavour. A small installer would allow the user to choose just
the
workflow they want and install that and the lowlatency kernel. It would
also install a more organized menu for the creative workflows (I used to
have a "multimedia" menu that I had to scroll all over to find anything)
For those DEs that still think in those terms (and are XDG compliant).
For those interested, the menu package should work well on any distro,
ubuntu or not, so long as it uses the XDG style of doing menus. Unity
and
Gnome Shell are the noted ones that don't really think in terms of menus
any more. I think Gnome Shell does have a menu option though. Unity does
not and besides it seems Unity has proven not to amiable to audio use
for
many people anyway. When I have it finished and tested, I will post the
download site.
3 Jun
3 Jun
9:58 a.m.
New subject: Debian audio production starting tips (was: Jack, lowlatency, generic, update)
On 02. juni 2013 22:10, Barney Holmes wrote:
For general playback of audio or for audio production
and composing music ?
Small scale audio production: Record stuff and do some simple editing
and multitrack mixing. I'm (slowly) on my way learning Ardour and have
plans to dabble with hydrogen and try to understand VST and synth emulators.
Additionally, I'm using my system for general office tasks, through
libreoffice, firefox, notes etc.
I've been running Ubuntu Studio the last year or so (now on 12.10) and
like it, but after my mess with the generic kernel I want to look at
debian as a possible alternative to 13.04.
2 Jun
2 Jun
8:58 p.m.
On 06/02/2013 05:06 AM, Len Ovens wrote:
On Sun, June 2, 2013 2:40 am, david wrote:
Very slow. They just released Debian 7.
I've tried upgrading Ubuntu from one version
to the next, and pretty
much had no success. So with Ubuntu, I prefer a fresh install.
Debian's been no problem at all with upgrades. Even successfully changed
from stable to sid once simply by changing my repositories.
Upgraded Sid on my desktop machine today, 440+ upgraded packages, and it
works flawlessly.
Good to know. I am not sure what debian's release schedule is, but the
freeze seems to be a lot longer than Ubuntu does.
The freeze ran pretty long this time. (Which helped make me confident
about doing an upgrade, I figured things had been pretty well tested
before they finally moved into Sid.)
That would give more
time for testing. Also UbuntuStudio is a) a very small team. b) a very
different install. That is, the mix of applications and their attached
libs is greater than any other ubuntu.
I have found it very frustrating that something simple like a video player
needs to be switched almost every release to find one that works.
Hmm, haven't encountered that. But Mplayer's my player of choice.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
3 Jun
3 Jun
2:07 a.m.
On Sun, June 2, 2013 11:58 am, david wrote:
Totem doesn't work for me right now, I am not sure if it is the DE, my old
video card, the video driver or what.
--
Len Ovens
www.OvenWerks.net
On 06/02/2013 05:06 AM, Len Ovens wrote:
I have found
it very frustrating that something simple like a video
player
needs to be switched almost every release to find one that works.
Hmm, haven't encountered that. But Mplayer's my player of choice.
4 Jun
4 Jun
11:35 a.m.
On 06/02/2013 02:07 PM, Len Ovens wrote:
On Sun, June 2, 2013 11:58 am, david wrote:
Totem doesn't work for me right now, I am not sure if it is the DE, my old
video card, the video driver or what.
Sorry, have no clue. Haven't ever used Totem.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
On 06/02/2013 05:06 AM, Len Ovens wrote:
I have
found it very frustrating that something simple like a video
player
needs to be switched almost every release to find one that works.
Hmm, haven't encountered that. But Mplayer's my player of choice.
2 Jun
2 Jun
6:49 p.m.
On Sat, Jun 01, 2013 at 11:40:30PM -1000, david wrote:
Debian's been no problem at all with upgrades.
Even successfully
changed from stable to sid once simply by changing my repositories.
Yeah, that is the normal way to change to sid. IOW, you don't install
sid.
Upgraded Sid on my desktop machine today, 440+
upgraded packages,
and it works flawlessly.
Ouch, you are living on the edge there. Hope you aren't just
haphazzardly upgrading and expecting everything to just work!
--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X
8:29 p.m.
On 06/02/2013 06:49 AM, Chris Bannister wrote:
Nah, I used to mix sid, experimental and deb-multimedia ...
On Sat, Jun 01, 2013 at 11:40:30PM -1000, david
wrote:
Start with Sid in the first place: Aptosid.com.
Debian's been no problem at all with
upgrades. Even successfully
changed from stable to sid once simply by changing my repositories.
Yeah, that is the normal way to change to sid. IOW, you don't install
sid. Upgraded Sid
on my desktop machine today, 440+ upgraded packages,
and it works flawlessly.
Ouch, you are living on the edge there. Hope you aren't just
haphazzardly upgrading and expecting everything to just work!
This time it worked. I usually just upgrade what I'm interested in. But
I always prep for it by making an image of my system partition first.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
3 Jun
3 Jun
12:06 a.m.
david wrote:
Debian's been no problem at all with upgrades. Even successfully
changed from stable to sid once simply by changing my repositories.
Upgraded Sid on my desktop machine today, 440+ upgraded packages,
and it works flawlessly.
Greetings from the Debian upgrade treadmill ;-)
I've learned it works most reliably if you upgrade in two
stages:
apt-get upgrade
apt-get dist-upgrade
I just verify that it won't removing major packages, and do
a backup first if I see that the C libraries are going to change,
Although I benefit from the developments in multimedia
software I'm not sure I like exposing my system to so many
opportunities for failure.
A strategy I've used in past is to *not* upgrade until I
need something. Maybe could call it it "choose your own
freeze".
I'm told this is sub-optimal because the package upgrade
scripts are not tested against all previous packages.
Regards,
--
Joel Roth
1:36 a.m.
On 06/02/2013 12:06 PM, Joel Roth wrote:
david wrote:
Been doing it for many years now.
Debian's been no problem at all with upgrades. Even successfully
changed from stable to sid once simply by changing my repositories.
Upgraded Sid on my desktop machine today, 440+ upgraded packages,
and it works flawlessly.
Greetings from the Debian upgrade treadmill ;-) I've learned it works most reliably if you upgrade
in two
stages:
apt-get upgrade
apt-get dist-upgrade
I just verify that it won't removing major packages, and do
a backup first if I see that the C libraries are going to change,
I always do a backup first. Have had trivial things like changes in X
video drivers make X unusable.
Although I benefit from the developments in
multimedia
software I'm not sure I like exposing my system to so many
opportunities for failure.
A strategy I've used in past is to *not* upgrade until I
need something. Maybe could call it it "choose your own
freeze".
I usually just upgrade what I want when I want.
I'm told this is sub-optimal because the package
upgrade
scripts are not tested against all previous packages.
Hmm, never heard that.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
8:33 a.m.
Am 03.06.2013 01:36, schrieb david:
I always do a backup first. Have had trivial things
like changes in X
video drivers make X unusable.
I do it the other way round, I put on hold what I didn't want to
upgrade, and upgrade the rest.
I never do a backup, and in the last 10 Years I didn't ever need one. ;-)
I usually do apt-get update && apt-get -u dist-upgrade and read the
output, that gives me enough information if I need to put packages on
hold, or if I could safely just run the full upgrade.
If a package is broken after upgrade, I just downgrade it to the one
from testing.
Although I benefit from the developments in
multimedia
software I'm not sure I like exposing my system to so many
opportunities for failure.
A strategy I've used in past is to *not* upgrade until I
need something. Maybe could call it it "choose your own
freeze".
I usually just upgrade what I want when I want.
4 Jun
4 Jun
11:34 a.m.
On 06/02/2013 08:33 PM, hermann meyer wrote:
Am 03.06.2013 01:36, schrieb david:
Good thing your hard drive hasn't failed on you, then. ;-)
I always do a backup first. Have had trivial
things like changes in X
video drivers make X unusable.
I do it the other way round, I put on hold what I didn't want to
upgrade, and upgrade the rest.
I never do a backup, and in the last 10 Years I didn't ever need one. ;-) Although I benefit from the developments in
multimedia
software I'm not sure I like exposing my system to so many
opportunities for failure.
A strategy I've used in past is to *not* upgrade until I
need something. Maybe could call it it "choose your own
freeze".
I usually just upgrade what I want when I want. I usually do apt-get update && apt-get -u
dist-upgrade and read the
output, that gives me enough information if I need to put packages on
hold, or if I could safely just run the full upgrade.
I just look at what's marked upgradeable in Synaptic.
If a package is broken after upgrade, I just downgrade
it to the one
from testing.
So how does one downgrade? That I haven't figured out.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
5 Jun
5 Jun
1:30 p.m.
Am 04.06.2013 11:34, schrieb david:
There are different ways to do so, which one to use depend on how hard
it rocks over you. :-)
have a look at Debian package management:
http://www.debian.org/doc/manuals/debian-reference/ch02.en.html
chapter 2.6.4 Rescue with dpkg
chapter 2.7.10 Emergency downgrading
If a package is broken after upgrade, I just
downgrade it to the one
from testing.
So how does one downgrade? That I haven't figured out.
9:04 p.m.
On 06/05/2013 01:30 AM, hermann meyer wrote:
Am 04.06.2013 11:34, schrieb david:
There are different ways to do so, which one to use depend on how hard
it rocks over you. :-)
have a look at Debian package management:
http://www.debian.org/doc/manuals/debian-reference/ch02.en.html
chapter 2.6.4 Rescue with dpkg
chapter 2.7.10 Emergency downgrading
Thanks!
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
If a package is broken after upgrade, I just
downgrade it to the one
from testing.
So how does one downgrade? That I haven't figured out.
4148
days inactive
4152
days old
linux-audio-user@lists.linuxaudio.org
21 comments
9 participants
participants (9)
-
Alf Haakon Lund -
Barney Holmes -
Chris Bannister -
david -
hermann meyer -
Joel Roth -
John Murphy -
Len Ovens -
Simon Wise