Oh no! Something has gone wrong

[Sergei G]

I am trying to run Debian 8.8 under current version 5.1.22 of VirtualBox 
on Windows 10 and I am getting


Oh no! Something has gone wrong

error message.  I went down to simplest level of running Debian Gnome 
Live disk and I am still getting this error.


I tried a few display settings (128MB of video memory, enable/disable 3D 
acceleration) without success.


I know had the same issue when I tried to install live Debian on my new 
hardware directly:


Intel Pentium G4560 CPU on Gigabyte B250M-D3H motherboard.  I suspect 
that CPU built-in video is not supported.  I resolved the issue on the 
hardware by using a video card that I know works with Linux.

Re: Oh no! Something has gone wrong

[Felix Miata]

Sergei G composed on 2017-06-04 00:31 (UTC-0700):

> I am trying to run Debian 8.8 under current version 5.1.22 of VirtualBox 
> on Windows 10 and I am getting

>  Oh no! Something has gone wrong

> error message.  I went down to simplest level of running Debian Gnome 
> Live disk and I am still getting this error.

> I tried a few display settings (128MB of video memory, enable/disable 3D 
> acceleration) without success.

> I know had the same issue when I tried to install live Debian on my new 
> hardware directly:

> Intel Pentium G4560 CPU on Gigabyte B250M-D3H motherboard.  I suspect 
> that CPU built-in video is not supported.  I resolved the issue on the 
> hardware by using a video card that I know works with Linux.

Do you have a question?

Your suspicion is correct. Kaby Lake (G4560) gfx is not supported on 8.8. It's
much too new. If you wish to use your Kaby Lake gfx, either install Stretch
instead of Jessie, or upgrade Jessie's kernel to one that supports Kaby Lake 
(4.9).

Your subject error message is a standard/common Gnome error that results from
trying to use gfx that has insufficient Xorg driver and/or hardware support.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Oh no! Something has gone wrong

[Sergei G]

Thank you

You have answered my question perfectly.

Is stretch going to give me trouble?


On 6/4/2017 12:55 AM, Felix Miata wrote:

Sergei G composed on 2017-06-04 00:31 (UTC-0700):


I am trying to run Debian 8.8 under current version 5.1.22 of VirtualBox
on Windows 10 and I am getting
  Oh no! Something has gone wrong
error message.  I went down to simplest level of running Debian Gnome
Live disk and I am still getting this error.
I tried a few display settings (128MB of video memory, enable/disable 3D
acceleration) without success.
I know had the same issue when I tried to install live Debian on my new
hardware directly:
Intel Pentium G4560 CPU on Gigabyte B250M-D3H motherboard.  I suspect
that CPU built-in video is not supported.  I resolved the issue on the
hardware by using a video card that I know works with Linux.

Do you have a question?

Your suspicion is correct. Kaby Lake (G4560) gfx is not supported on 8.8. It's
much too new. If you wish to use your Kaby Lake gfx, either install Stretch
instead of Jessie, or upgrade Jessie's kernel to one that supports Kaby Lake 
(4.9).

Your subject error message is a standard/common Gnome error that results from
trying to use gfx that has insufficient Xorg driver and/or hardware support.

Re: HP CP1215 - CUPS not printing from Stretch to Jessie server.

[Curt]

On 2017-06-03, Gary Dale  wrote:
>
>> The Printing section on the wiki deals with "Double Filtering". It might
>> help.
>>
>
> Where is the wiki?
>
>
I think this must be it:

https://wiki.debian.org/PrintQueuesCUPS#Double_Filtering

-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

Re: Install Debian 8.8.0/XFCE on32 bit system

[Stephen P. Molnar]

On 06/01/2017 07:55 PM, David Wright wrote:

On Thu 01 Jun 2017 at 12:32:01 (-0400), Greg Wooledge wrote:

On Thu, Jun 01, 2017 at 12:23:56PM -0400, Stephen P. Molnar wrote:

On 06/01/2017 10:24 AM, David Wright wrote:



  ? [!!] Partition disks ?



   ???  SCSI1 (0,0,0) (sda) - 60.0 GB ATA IC25N060ATMR04-0



   ???  SCSI3 (0,0,0) (sdb) - 1.0 GB Generic Flash Disk



The above ...[!!] Partition disks... is exactly what I'm seeing.  The
question comes down to which option do I take?  I only want to partition
sda, so that I don't wipe the other drives in the system.


The important part is that "sda" and "sdb" are not meaningful labels in
the general case.  You need to look at the rest of the information --
the size, the description, the model number, the existing partitions.
Use those to decide which disk to write to.


That's right. The strings you see above in the example are the
/dev/disk/by-id files (or part thereof) and those filenames
(or parts thereof) can frequently be found written on the outside
of the disk's casing (and sometimes on the box) as Model/Serial/Part
Number or whatever.

When I managed to persuade the Computing Service to issue me with
several disks at the same time (very infrequently), I would make
sure I created partitions with slightly different (usually by one
cylinder, a historical concept!) absolute and relative sizes so that
I could distinguish them in circumstances where size was the only
parameter visible.

Cheers,
David.




My thanks to all who responded to my plea for help.  The problem has 
been solved.  As it turned out the command line installer had the option 
for partitioning the hda and I managed to install Debian Stretch rc4.


--
Stephen P. Molnar, Ph.D.Life is a fuzzy set
www.molecular-modeling.net  Stochastic and multivariate
(614)312-7528 (c)
Skype: smolnar1

Re: Proper sources list from Jessie > Stretch

[Lisi Reisz]

On Sunday 04 June 2017 00:27:06 Ric Moore wrote:
> On 06/02/2017 10:41 AM, Fungi4All wrote:
> > Sorry for the top-post but I think it is appropriate
>
> It is not ever appropriate, no matter what you think. Ric

+1

Lisi

Re: Oh no! Something has gone wrong

[Liam O'Toole]

On 2017-06-04, Felix Miata  wrote:
> Sergei G composed on 2017-06-04 00:31 (UTC-0700):
>
>> I am trying to run Debian 8.8 under current version 5.1.22 of
>> VirtualBox on Windows 10 and I am getting
>
>>  Oh no! Something has gone wrong
>
>> error message.  I went down to simplest level of running Debian Gnome
>> Live disk and I am still getting this error.
>
>> I tried a few display settings (128MB of video memory, enable/disable
>> 3D acceleration) without success.
>
>> I know had the same issue when I tried to install live Debian on my
>> new hardware directly:
>
>> Intel Pentium G4560 CPU on Gigabyte B250M-D3H motherboard.  I suspect
>> that CPU built-in video is not supported.  I resolved the issue on
>> the hardware by using a video card that I know works with Linux.
>
> Do you have a question?
>
> Your suspicion is correct. Kaby Lake (G4560) gfx is not supported on
> 8.8. It's much too new. If you wish to use your Kaby Lake gfx, either
> install Stretch instead of Jessie, or upgrade Jessie's kernel to one
> that supports Kaby Lake (4.9).
>
> Your subject error message is a standard/common Gnome error that
> results from trying to use gfx that has insufficient Xorg driver
> and/or hardware support.

OP is running jessie on VirtualBox, so the host hardware shouldn't
matter. If he installs virtualbox-guest-x11 and virtualbox-guest-dkms
(preferably from jessie-backports) in the guest and reboots it, he
should be able to run GNOME.

-- 

Liam

Re: switching flavors

[Frank M]

On 06/03/2017 11:11 PM, Gary Dale wrote:

On 03/06/17 08:59 PM, Frank M wrote:

I am running Debian Stretch, and like to change to Sid.

Can I just change my sources.list to unstable and upgrade?

I have run Sid before and am prepared to deal with some breakage


Yes, although I'd do a dist-upgrade (or full-upgrade if using aptitude).

Based on some earlier problems with Stretch and the discussions around 
it, I'm not sure that sid is necessarily less stable. Apparently they 
dump stuff into Stretch without anyone actually checking to see that 
it can work with other Stretch libraries.




Thanks Gary. Will do later today.

Re: switching flavors

[Frank M]

On 06/04/2017 02:20 AM, Davor Balder wrote:

Yes - and based on some work I did earlier in the week if you keep the
things simple I would say your upgrade should be uneventful.

I  changed the repo to unstable

Then I did:

apt-get update

apt-get upgrade

That was it.


Cheers


D

On 04/06/17 13:11, Gary Dale wrote:

On 03/06/17 08:59 PM, Frank M wrote:

I am running Debian Stretch, and like to change to Sid.

Can I just change my sources.list to unstable and upgrade?

I have run Sid before and am prepared to deal with some breakage

Yes, although I'd do a dist-upgrade (or full-upgrade if using aptitude).

Based on some earlier problems with Stretch and the discussions around
it, I'm not sure that sid is necessarily less stable. Apparently they
dump stuff into Stretch without anyone actually checking to see that
it can work with other Stretch libraries.





Great. Thanks very much. We'll see how it goes.

Re: Install Debian 8.8.0/XFCE on32 bit system

[David Wright]

On Sat 03 Jun 2017 at 18:18:02 (-0400), Felix Miata wrote:
> David Wright composed on 2017-06-01 18:55 (UTC-0500):
> 
> > When I managed to persuade the Computing Service to issue me with
> > several disks at the same time (very infrequently), I would make
> > sure I created partitions with slightly different (usually by one
> > cylinder, a historical concept!) absolute and relative sizes so that
> > I could distinguish them in circumstances where size was the only
> > parameter visible.
> 
> Most of my / partitions are 4800M, 5600M or 7200M, to facilitate interchange
> with minimal need to do any re-partitioning. I have bunches of multiboot test
> systems, and do a lot of cloning. There's no way I could keep track of what I
> have without a written record of what lives where. Luckily, the only 
> partitioner
> ever used here[1] creates logs with tables that inventory each disk 
> wonderfully.
> (Old) example: http://fm.no-ip.com/Tmp/Dfsee/fi965d03.txt

Yes, I've always kept an inventory of drives (and everything else)
with the partitioning scheme, udev data, SMART output, and a general
diary of anything unusual. But what I was talking about above is
what's available to you at the moment you press the final confirmatory
keystroke when, say, formatting a partition with DOS 6.22 or its
predecessors. IIRC (20 years ago) at that moment, the only feedback
from the system about which partition will actually be formatted
is its size. And back in those days, if you formatted a DOS
partition in linux, there was a good chance it wouldn't work because
of disagreements over geometry. You had to let DOS choose the
geometry and then linux would follow it.

But you're unusual in working in this area, so unlike most of us
you're going to have a dedicated tool available; in fact you work
on it I see.

Cheers,
David.

Re: switching flavors

[SDA]

On Sun, Jun 04, 2017 at 04:20:02PM +1000, Davor Balder wrote:
> Yes - and based on some work I did earlier in the week if you keep the
> things simple I would say your upgrade should be uneventful.
> 
> I  changed the repo to unstable
> 
> Then I did:
> 
> apt-get update
> 
> apt-get upgrade
> 
> That was it.

Nope, not done yet. You still need to do a full upgrade. In apt it's 'apt 
full-upgrade' in aptitude it's 'aptitude dist-upgrade'. Not sure what the 
eqivalent command is in apt-get.

Re: Install Debian 8.8.0/XFCE on32 bit system

[Felix Miata]

David Wright composed on 2017-06-04 11:19 (UTC-0500):
...
> But you're unusual in working in this area, so unlike most of us
> you're going to have a dedicated tool available; in fact you work
> on it I see.

I'm not sure what you mean. I'm only a DFSee user, no kind of programmer. I
discovered the value of sticking to one single partitioning tool with an
interface consistent across environments for use on multiboot systems back in
2000, when I first took serious interest in adding Linux to my installed systems
repertoire for eventual migration from OS/2. Back then in v3.x it had native
binaries for DOS, Windows and OS/2 only. Its Linux binary was introduced in
2004, Mac in 2007. GPT writing, which I have yet to use, was a long time coming,
introduced in 2015.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: HP CP1215 - CUPS not printing from Stretch to Jessie server.

[Brian]

On Sat 03 Jun 2017 at 18:45:13 -0400, Gary Dale wrote:

> After much gnashing of teeth (actually disassembling my Samsung C410 to
> remove two sheets of paper wrapped around the fuser), I'm still confused
> about something. When I set up my Samsung C410 through the CUPS web
> interface, on the server I use the Samsung C410 driver and the usb
> connection. On the client I use the discovered printer but again need to use
> the Samsung C410 driver which now shows up as Remote printer: Samsung C410
> Series (color).

You do not *need* to use the Samsung C410 PPD or the rastertospl filter
on the client. In fact, you are better off just letting cups-browsed
take care of things and not bothering with using the CUPS web interface.

> When I set up the HP Color LaserJet CP1215, on the server I use the HP Color
> LaserJet CP1215 Foomatic driver and the usb connection. However on the
> client when I use the discovered printer and the CP1215 driver, it doesn't
> work. I need to use raw printing.

If cups-browsed is sidelined a raw queue would be the only other sensible
method.

> I'm sorry but this doesn't make any sense to me. If I understand things
> correctly, CUPS knows that the printer is remote and is being handled by a
> CUPS server but can't figure out which machine should do the rendering.
> Instead it leaves it up to the driver to add the smarts to figure out who
> should do it.

CUPS on the client knows the URI to send the job to. Prior to that it
will perform filter operations on the job because it has been told to
do so.  There is no negotiation between client and server as to which
machine handles filtering, so the server will probably attempt to filter
the job again. The main job of the driver (PPD?) is to get the print job
in a form suitable to go to the printer. It functions only within the
queue it is set up for.

There is no reliable way to detect whether data which are sent to the
server are printer-specific data (to be sent directly to the printer) or
data which must be filtered to get printer-specific data. I suppose if
the server identifies a file as application/octet-stream it could be
printed. You would have to look at Jessie and Stretch error_logs to
determine that and sort out what you see as puzzling.

> I've got several printers attached to my server, including 2 Samsungs, 1
> Epson and the CP1215. Only the CP1215 seems to believe that it is a local
> raw printer on my client. And again, this only seems to be a problem since I
> moved to Stretch. I think this qualifies as a bug.

A Jessie or Stretch client would produce Zenographics Zjstream printer
data to send to the server; no change there. CUPS on the server (which
hasn't changed) is the one doing the MIME media typing and saying it
cannot detect the file type.

A sound principle to apply to duplicate filtering is - don't do it.

-- 
Brian.

Re: switching flavors

[Joe]

On Sun, 4 Jun 2017 12:20:51 -0400
SDA  wrote:

> On Sun, Jun 04, 2017 at 04:20:02PM +1000, Davor Balder wrote:
> > Yes - and based on some work I did earlier in the week if you keep
> > the things simple I would say your upgrade should be uneventful.
> > 
> > I  changed the repo to unstable
> > 
> > Then I did:
> > 
> > apt-get update
> > 
> > apt-get upgrade
> > 
> > That was it.  
> 
> Nope, not done yet. You still need to do a full upgrade. In apt it's
> 'apt full-upgrade' in aptitude it's 'aptitude dist-upgrade'. Not sure
> what the eqivalent command is in apt-get.
> 

Other way around, aptitude is safe-upgrade and full-upgrade, it's
apt-get which has upgrade and dist-upgrade. apt mixes the two, with
upgrade and full-upgrade.

-- 
Joe

Re: switching flavors

[Frank M]

On 06/04/2017 01:44 PM, Joe wrote:

On Sun, 4 Jun 2017 12:20:51 -0400
SDA  wrote:


On Sun, Jun 04, 2017 at 04:20:02PM +1000, Davor Balder wrote:

Yes - and based on some work I did earlier in the week if you keep
the things simple I would say your upgrade should be uneventful.

I  changed the repo to unstable

Then I did:

apt-get update

apt-get upgrade

That was it.

Nope, not done yet. You still need to do a full upgrade. In apt it's
'apt full-upgrade' in aptitude it's 'aptitude dist-upgrade'. Not sure
what the eqivalent command is in apt-get.


Other way around, aptitude is safe-upgrade and full-upgrade, it's
apt-get which has upgrade and dist-upgrade. apt mixes the two, with
upgrade and full-upgrade.



Did an apt full-upgrade. Now running Sid. No problems.
Thanks guys.

Re: switching flavors

[Davor Balder]

You're right

there should be also

apt-get dist-upgrade


as the third command on the bottom


Cheers


D

On 05/06/17 02:20, SDA wrote:

> On Sun, Jun 04, 2017 at 04:20:02PM +1000, Davor Balder wrote:
>> Yes - and based on some work I did earlier in the week if you keep the
>> things simple I would say your upgrade should be uneventful.
>>
>> I  changed the repo to unstable
>>
>> Then I did:
>>
>> apt-get update
>>
>> apt-get upgrade
>>
>> That was it.
> Nope, not done yet. You still need to do a full upgrade. In apt it's 'apt 
> full-upgrade' in aptitude it's 'aptitude dist-upgrade'. Not sure what the 
> eqivalent command is in apt-get.
>

stretch & ArpON

[polymax]

stretch Debian Package: arpon (2.7.2-1 and others)

Does arpOn work using a vpn or/and Tor ?
If yes , does it need a special configuration ?


It is much better to not publish than to publish incorrect data.

Re: HP CP1215 - CUPS not printing from Stretch to Jessie server.

[Gary Dale]

On 04/06/17 01:34 PM, Brian wrote:

On Sat 03 Jun 2017 at 18:45:13 -0400, Gary Dale wrote:


After much gnashing of teeth (actually disassembling my Samsung C410 to
remove two sheets of paper wrapped around the fuser), I'm still confused
about something. When I set up my Samsung C410 through the CUPS web
interface, on the server I use the Samsung C410 driver and the usb
connection. On the client I use the discovered printer but again need to use
the Samsung C410 driver which now shows up as Remote printer: Samsung C410
Series (color).

You do not *need* to use the Samsung C410 PPD or the rastertospl filter
on the client. In fact, you are better off just letting cups-browsed
take care of things and not bothering with using the CUPS web interface.
Not really true. You seem to be trying to say that the CUPS printer 
discovery on the web interface shouldn't be used, which doesn't seem to 
be the way the web interface is designed. There is no indication that 
the find option is in any way deprecated.





When I set up the HP Color LaserJet CP1215, on the server I use the HP Color
LaserJet CP1215 Foomatic driver and the usb connection. However on the
client when I use the discovered printer and the CP1215 driver, it doesn't
work. I need to use raw printing.

If cups-browsed is sidelined a raw queue would be the only other sensible
method.
Except that it doesn't seem to work that way. It's just the CP1215 that 
needs to be set explicitly to raw. The other printers don't work when I 
set their driver to raw. I need to use the driver.





I'm sorry but this doesn't make any sense to me. If I understand things
correctly, CUPS knows that the printer is remote and is being handled by a
CUPS server but can't figure out which machine should do the rendering.
Instead it leaves it up to the driver to add the smarts to figure out who
should do it.

CUPS on the client knows the URI to send the job to. Prior to that it
will perform filter operations on the job because it has been told to
do so.  There is no negotiation between client and server as to which
machine handles filtering, so the server will probably attempt to filter
the job again. The main job of the driver (PPD?) is to get the print job
in a form suitable to go to the printer. It functions only within the
queue it is set up for.

There is no reliable way to detect whether data which are sent to the
server are printer-specific data (to be sent directly to the printer) or
data which must be filtered to get printer-specific data. I suppose if
the server identifies a file as application/octet-stream it could be
printed. You would have to look at Jessie and Stretch error_logs to
determine that and sort out what you see as puzzling.
That makes no sense. CUPS knows it's sending something to a remote queue 
( DNSSD: ) so it should be able figure out that it shouldn't do double 
filtering. I don't care where the filtering gets done but it should be 
done properly.

I've got several printers attached to my server, including 2 Samsungs, 1
Epson and the CP1215. Only the CP1215 seems to believe that it is a local
raw printer on my client. And again, this only seems to be a problem since I
moved to Stretch. I think this qualifies as a bug.

A Jessie or Stretch client would produce Zenographics Zjstream printer
data to send to the server; no change there. CUPS on the server (which
hasn't changed) is the one doing the MIME media typing and saying it
cannot detect the file type.

A sound principle to apply to duplicate filtering is - don't do it.

Except that if I follow your advice and change my Samsung and Epson 
queues to raw on the client, they stop working.


Which leads me to ask again why this inconsistent handling of remote 
queues shouldn't be classified as a bug?

Why was apache2's logfiles moved mid april?

[Gene Heskett]

Greetings all;

100% uptodate wheezy install here.

I try to keep a handle on my web site traffic with awffull, but it has 
not generated any new data since sometime in april, so I go looking for 
the why tonight and find that apache2's logfiles were moved 
to /var/log/httpd.  I was going to reconfigure awffull, but that would 
have cost me about 5 years of history,  so I moved the files, and where 
apache2 keeps its logs back to /var/log/apache2.

Was there a good reason to issue an update to apache2.conf that moved 
those logfiles?

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page