@wqqar: going a bit off-topic here, but try running:
nmcli dev|grep '\bconnected *'
It should return a line ending with connected when there is a
connection, otherwise empty. Also try running (as root):
nmcli dev|grep -q '\bconnected *'|| nmcli con up id my_connection_id
If there's a problem,
A clumsy workaround for autoconnecting (and auto-reconnecting):
As root or with sudo, create a text file /ect/cron.d/keep-it-up with the
following contents: (as one line!)
*/2 * * * * root nmcli dev|grep -q '\bconnected *'|| nmcli con up id
my_connection_id /dev/null 21
Every other minute, it
Still reproducible in 11.10. A suggested workaround (using gnome-manual-
duplex) not applicable anymore with Unity.
** Changed in: foo2zjs (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've confirmed this problem with several 10.04 LTS (amd64) machines VM's
running on a VMware vSphere system. Each machine that had an uptime of
211 days suffered a sudden softlockup, triggered by an innocent-looking
'apt-get install libyaml-perl'. The machines were running
2.6.32-30-server.
Some
(I'm a bit puzzled by why the day limit seems to be approximate. Could
it have something to do with clock drifting and adjustments by eg. ntp?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/805341
Sorry to flood, just a minor point: the OP wrote: Of course the time
stamp (18446743993.431771) and 17163091968s (544 years!) are false. But
actually the first timestamp is not false - it reveals that the lockup
has occurred after 213,5 days of uptime. (18446743993/60/60/24/1000).
--
You
What happens next?
If there's no one willing to look at this issue, I could to try taking a
look myself. In that case it would help a lot if I could have some
pointers on:
* where to look for the bug
* how to test and inspect changes (without actually printing, if
possible)
Btw, the bug is
Till, here's the error_log attached. HTH.
** Attachment added: cups error_log
https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/648258/+attachment/1643611/+files/error_log
--
manual duplex fails when printing a document with an odd number of pages
https://bugs.launchpad.net/bugs/648258
Public bug reported:
Binary package hint: cups
This bug is seen when I try to print a document that has an odd number
of pages (3, 5, 7, ...). It happens on my HP Laserjet M1120 MFP.
What I expect (with a 5-page document):
1) Odd-numbered pages (1,3,5) are printed
2) The printer waits for me
** Attachment added: PDF test files
https://bugs.launchpad.net/bugs/648258/+attachment/1639955/+files/duplex-test.zip
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/648258/+attachment/1639956/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
Additional information: on this amd64 machine I had installed the extra
packages hplip-gui, hpijs-ppds, hplip-cups. I can reproduce the bug on
another machine (i386) that doesn't have these packages installed.
--
manual duplex fails when printing a document with an odd number of pages
11 matches
Mail list logo
