Bug#1041774: [Pkg-utopia-maintainers] Bug#1041774: udisks2: Hangs for about 20 secs. and timeout error after upgrading to 2.10.0-3 on trixie

2023-07-24 Thread Ricardo Pérez López
El dom, 23 jul 2023 a las 21:56, Michael Biebl ()
escribió:

> Am 23.07.23 um 16:06 schrieb Ricardo Pérez:
> > Package: udisks2
> > Version: 2.10.0-3
> > Severity: important
> > X-Debbugs-Cc: rica...@ubuntu.com
> >
> > Dear Maintainer,
> >
> > After upgrading to 2.10.0-3 on trixie, when I try to run Thunar or
> > something similar, it hangs for about 20 secs. and then I got the
> > following error message:
> >
> > Error creating proxy: Error calling StartServiceByName for
> org.gtk.vfs.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24)
>
> This should be https://github.com/storaged-project/udisks/issues/1139
>
> It's supposedly both a bug in Thunar (for not running the query async)
> and should be mitigated by installing util-linux 2.39 (from experimental).


After upgrade to util-linux 2.39 and libmount 2.39 from experimental, the
issue seems to be fixed. Thank you!

Ricardo.


Bug#485739: libgems-ruby1.8: Installs gems multiple times

2008-09-04 Thread Ricardo Pérez López
I can confirm this bug as well in my Ubuntu 8.04.1.

I'm using rubygems version 1.1.1-1~hardy1.

$ sudo gem update
Updating installed gems
Bulk updating Gem source index for: http://gems.rubyforge.org/
Updating actionmailer
Bulk updating Gem source index for: http://gems.rubyforge.org/
Successfully installed activesupport-2.1.1
Successfully installed actionpack-2.1.1
Successfully installed actionmailer-2.1.1
Updating activerecord
Successfully installed activesupport-2.1.1
Successfully installed actionpack-2.1.1
Successfully installed actionmailer-2.1.1
Successfully installed activerecord-2.1.1
Updating activeresource
Successfully installed activesupport-2.1.1
Successfully installed actionpack-2.1.1
Successfully installed actionmailer-2.1.1
Successfully installed activerecord-2.1.1
Successfully installed activeresource-2.1.1
Updating rails
Successfully installed activesupport-2.1.1
Successfully installed actionpack-2.1.1
Successfully installed actionmailer-2.1.1
Successfully installed activerecord-2.1.1
Successfully installed activeresource-2.1.1
Successfully installed rails-2.1.1
Updating ruby-debug
Building native extensions.  This could take a while...
Successfully installed activesupport-2.1.1
Successfully installed actionpack-2.1.1
Successfully installed actionmailer-2.1.1
Successfully installed activerecord-2.1.1
Successfully installed activeresource-2.1.1
Successfully installed rails-2.1.1
Successfully installed ruby-debug-base-0.10.2
Successfully installed ruby-debug-0.10.2
Gems updated: activesupport, actionpack, actionmailer, activesupport,
actionpack, actionmailer, activerecord, activesupport, actionpack,
actionmailer, activerecord, activeresource, activesupport, actionpack,
actionmailer, activerecord, activeresource, rails, activesupport,
actionpack, actionmailer, activerecord, activeresource, rails,
ruby-debug-base, ruby-debug





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#487043: Firestarter fails to run on locales other than English

2008-06-19 Thread Ricardo Pérez López
Package: firestarter
Version: 1.0.3-6

Firestarter refuses to run when you use a locale other than English.

The problem is in the (generated) file /etc/firestarter/firestarter.sh.
The following lines:

IP=`/sbin/ifconfig $IF | grep inet | cut -d : -f 2 | cut -d \\ -f 1`
MASK=`/sbin/ifconfig $IF | grep Mas | cut -d : -f 4`
BCAST=`/sbin/ifconfig $IF |grep Bcast: | cut -d : -f 3 | cut -d \\ -f 1`

fails when the locale is other than English, because they look up
several keyword (Mas, Bcast:) which doesn't appears in ifconfig in
Spanish. Example:

[EMAIL PROTECTED]:~$ LANG=C ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:18:f3:53:b2:9a
  inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0
  UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
  RX packets:2736 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2634 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:2917432 (2.7 MB) TX bytes:368744 (360.1 KB)
  Interrupt:18 Base address:0xa000

[EMAIL PROTECTED]:~$ ifconfig eth0
eth0 Link encap:Ethernet direcciónHW 00:18:f3:53:b2:9a
  inet dirección:192.168.2.100 Difusión:192.168.2.255
Máscara:255.255.255.0
  ARRIBA DIFUSIÓN CORRIENDO MULTICAST MTU:1500 Metric:1
  RX packets:2723 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2620 errors:0 dropped:0 overruns:0 carrier:0
  colisiones:0 txqueuelen:1000
  RX bytes:2908959 (2.7 MB) TX bytes:365950 (357.3 KB)
  Interrupción:18 Dirección base: 0xa000

As a workaround, you can hack the /etc/firestarter/firestarter.sh file,
replacing the three above lines with the following:

IP=`LANG=C /sbin/ifconfig $IF | grep inet | cut -d : -f 2 | cut -d \\ -f
1`
MASK=`LANG=C /sbin/ifconfig $IF | grep Mas | cut -d : -f 4`
BCAST=`LANG=C /sbin/ifconfig $IF |grep Bcast: | cut -d : -f 3 | cut -d \
\ -f 1`

The following is a patch which can be used to hack the problem, using
the above workaround:

 BEGIN OF THE PATCH =
--- src/scriptwriter.c.old  2008-04-30 22:42:08.0 +0200
+++ src/scriptwriter.c  2008-04-30 22:44:23.0 +0200
@@ -88,9 +88,9 @@
fprintf (f, \n# --(Extract Network Information)--\n\n);
 
fprintf (f, # External network interface data\n
-   IP=`/sbin/ifconfig $IF | grep inet | cut -d : -f 2 | cut 
-d \\  -f 1`\n
-   MASK=`/sbin/ifconfig $IF | grep Mas | cut -d : -f 4`\n
-   BCAST=`/sbin/ifconfig $IF |grep Bcast: | cut -d : -f 3 | 
cut -d \\  -f 1`\n
+   IP=`LANG=C /sbin/ifconfig $IF | grep inet | cut -d : -f 2 
| cut -d \\  -f 1`\n
+   MASK=`LANG=C /sbin/ifconfig $IF | grep Mas | cut -d : -f 
4`\n
+   BCAST=`LANG=C /sbin/ifconfig $IF |grep Bcast: | cut -d : 
-f 3 | cut -d \\  -f 1`\n
NET=$IP/$MASK\n\n);
 
fprintf (f, if [ \$NAT\ = \on\ ]; then\n
 END OF THE PATCH =

Please, can anybody apply the patch? Thanks a lot.




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#336501: Fatal Error: File /usr/lib/smarteiffel/ seems to be empty

2005-10-30 Thread Ricardo Pérez López
Package: smarteiffel
Version: 1.1-6

1. I create an Eiffel code (e.g. a hello world), in hello.e. The root
class is HELLO, and the root procedure is make.
2. I go into smarteiffel.sh
3. I set the root class and root procedure accordingly.
4. I type 5 to compile the system, and then I get the following error
message:

** Fatal Error: File /usr/lib/smarteiffel/ seems to be empty.
--

and the system didn't compile.

However, if I do:

$ se-compile hello make

then it compiles perfectly, and leads to a a.out executable.

And... if I do:

$ export SmartEiffel=/usr/lib/smarteiffel
$ se-compile hello make

I get the above error message, and it didn't compile.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#330703: Accented chars doesn't works in es_ES.UTF-8 console text mode

2005-09-29 Thread Ricardo Pérez López
Package: console-data
Version: 2002.12.04dbs-49

1. I install Debian Sarge.
2. I do dpkg-reconfigure locales, and select es_ES.UTF-8 locale by
default (I'm Spanish, and I want to use UTF-8 coding by default).
3. Now and then, I can't type accented chars (áéíóú) in the text
consoles (tty1, tty2, etc.). That chars are dead keys: I must to type
the accent key, and then type the vocal.

I think UTF-8 doens't works very well with the Spanish keyboards and the
dead keys.

Obviously, this issue renders the console unusable in Spanish keyboards
with UTF-8.

Any ideas?

Ricardo.




Bug#330703: This *can* help

2005-09-29 Thread Ricardo Pérez López
I don't know if this can help:

1. «dumpkeys  output.txt». The output.txt file is in ISO, not in UTF-8.
2. «recode latin9..utf8 output.txt». This convert the output.txt file into UTF-8
coding.
3. I try then «loadkeys output.txt», but I got a «syntax error» in the line
which the «compose» lines begins.

It seems that the loadkeys command doesn't supports a file codified in UTF-8. I
noticed that the command «dumpkeys --help» shows the following output:

available charsets:
iso-8859-{1,2,3,4,5,7,8,9,10,15},koi8-{r,u},mazovia,cp-1250,iso-10646-18,iso-ir-197,iso-ir-209

There's no UTF-8 there. Maybe the solution could be to recode the «loadkeys»
file to understand the compose keys in UTF-8...