Is this still happening? I no longer have the system that I found this
bug on. I posted the workaround in this threads first message, and a
solution was committed to Ubuntu long ago. Should not be a problem in
current ubuntu. Yes, my searches say that the fix was committed in
July 2011.
If you
Fix has been committed upstream.
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Fix Committed
--
GSM dialup: Timeout waiting for AT+CPIN?
https://bugs.launchpad.net/bugs/607517
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Advances in networkmanager has made it possible to use bluetooth modems.
Connecting a new bluetooth device allows you to enable the DUN service,
which sends the dbus messages to networkmanager, which picks up the
rfcomm device.
Which is all very good, for the use of bluetooth, but we still do not
Public bug reported:
When I updated my pxeboot/nfs system to 10.10, several applets failed to load,
and the log files contained the following messages:
Oct 19 22:25:58 computer08 kernel: [ 66.326808] non-accessible hardlink
creation was attempted by: gconfd-2 (fsuid 1000)
Oct 19 22:26:05
Posted upstream in gnome bugzilla for network-manager
Link is
https://bugzilla.gnome.org/show_bug.cgi?id=629898
** Bug watch added: GNOME Bug Tracker #629898
https://bugzilla.gnome.org/show_bug.cgi?id=629898
--
GSM dialup: Timeout waiting for AT+CPIN?
https://bugs.launchpad.net/bugs/607517
Public bug reported:
Binary package hint: network-manager
When attempting to connect using my Samsung SGH-A501, the dial process halts
with the attempt to check the pin status. Relevant log from modem-manager:**
Message: (ttyACM0) opening serial device...
** Message: Modem
** Attachment added: script file containing output of network-manager and
modem-manager --debug
http://launchpadlibrarian.net/52186268/nm-log
--
GSM dialup: Timeout waiting for AT+CPIN?
https://bugs.launchpad.net/bugs/607517
You received this bug notification because you are a member of
After looking in the bowls of modem-manager, I found the line which
creates this request. Adjusting the timeout (I chose 15 seconds) fixes
the problem. Very simple patch attached.
This probably needs investigating as to whether the timeout for all pin
checks or sets needs to be increased. I
This is a known issue in mythtv. The mythtv bug ticket is
http://svn.mythtv.org/trac/ticket/7315
Fixes in svn have been reported as working for some, but others are
still reporting the issue. A workaround seems to be turning off 'Delete
files slowly' (database name
I see we have just got linux 2.6.31_16, but I cannot see the patch in
the changes list. Does anyone know if the patch made it? I don't have
reliable net access at my myth box, so I cannot easily try it to see.
--
regression: support for dvico dual digital 4 card
How are you going getting the patch into v4l, Robert? It would be good
to have these devices powered down when not required, because they are
hungry little fellows.
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification
Public bug reported:
When attempting to set up my mobile phone as a bluetooth modem, I could
not find a way to specify the device node (/dev/rfcomm0). I have the
bluetooth binding set up correctly, and I have the connection working
with gnome-ppp.
Description:Ubuntu intrepid (development
-config-printer/system-config-printer.py
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
Package: system-config-printer-gnome 0.7.80+svn1942-0ubuntu2
PackageArchitecture: all
ProcCmdline: python /usr/share/system-config-printer/system-config-printer.py
ProcCwd: /home/robbak
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/11970835/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/11970836/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/11970837/ProcStatus.txt
** Attachment
The cause of my troubles was that i had not marked the printers as published
- when I did that, it found them, and everything worked as advertised.
Still, crashing is not the right thing to do, and this crash will still occur
if people choose the obsecurity of an unpublished printer.
--
I just experienced this when inserting a sony memory stick. I also had
this crash before, when using an sd(?) card. Incidentally, both had the
DCIM virus on them.
--
gnome-mount crashed with SIGSEGV in g_datalist_id_set_data_full()
https://bugs.launchpad.net/bugs/122673
You received this bug
16 matches
Mail list logo
