[Bug 372493] Re: f-u-s-a always show "Switch User" if more than 15 users
I also think that f-u-s-a is either misnamed or overdoing. Currently it manages presence, user switching and session ending. Because of this, it's becoming a very useful applet and people are interested in using it, of course. Also, it seems to me that it could become the de-facto standard in the GNOME desktop environment. So it sounds logical to allow people, especially technical ones (doing the deployment), to get full control of what we can do with it. And currently we don't have a full control on it: we lack the ability to fully disable one of the 3 functions of f-u-s-a. About ou "use case [...] quite unusual" and "it confuses your users", I can tell you it really _does_ confuse people, whatever the culture difference, as much in Asia (where I work) as in Africa (where Thomas work). On my side, I simply can't understand how this patch would harm anybody? But it would help us a lot, and probably others too, for sure! If you can't afford changing the meaning of "never" then please add some "never-ever" (or whatever) value to allow us fulfill our needs. TIA, J.C. -- f-u-s-a always show "Switch User" if more than 15 users https://bugs.launchpad.net/bugs/372493 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278341] Re: missing utf-8 input decoding in the Python Console plugin
Done and linked to this bug (correctly, I hope). Thank you for having pointed that. :-) Anything else to do? ** Bug watch added: GNOME Bug Tracker #558149 http://bugzilla.gnome.org/show_bug.cgi?id=558149 ** Also affects: gedit via http://bugzilla.gnome.org/show_bug.cgi?id=558149 Importance: Unknown Status: Unknown -- missing utf-8 input decoding in the Python Console plugin https://bugs.launchpad.net/bugs/278341 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278341] Re: missing utf-8 input decoding in the Python Console plugin
Mhhh... Did I do something wrong when linking to Gnome bug tracking system? Because first I didn't see the status change from Unknown to New, and now the bug is solved (fixed) already on Gnome's side but it's still shown as Unknown here. :-/ -- missing utf-8 input decoding in the Python Console plugin https://bugs.launchpad.net/bugs/278341 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262609] Re: [needs-packaging] PMB (PhpMyBibli) - integrated library system (ILS)
FYI, there is some Spanish people having already worked on PMB's (unofficial?) packaging. See: https://lliurex.net/projects/valencia/lliurex-pool-ng/browser /ubuntu-wnpp/trunk/pmb -- [needs-packaging] PMB (PhpMyBibli) - integrated library system (ILS) https://bugs.launchpad.net/bugs/262609 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278341] [NEW] missing utf-8 input decoding in the Python Console plugin
Public bug reported:
Binary package hint: gedit
Some friend found a problem with the Python Console plugin in gedit
2.22.3-0ubuntu1, coming with Ubuntu 8.04(.1).
When inputing some utf-8 encoded text, it's evaluated as a byte string
instead, meaning it's not decoded as it should and as it effectively is
in an external "python" or "ipython" ran into a terminal.
Here is some example to reproduce and understand the bug:
1/ in a gedit Python Console:
>>> ch = u"Stéphanie"
>>> ch
u'St\xc3\xa9phanie'
>>> print ch[2]
Ã
2/ in a "python" command run in a terminal:
>>> ch = u"Stéphanie"
>>> ch
u'St\xe9phanie'
>>> print ch[2]
é
We could explicitly ask for input decoding using """ch =
'Stéphanie'.decode('utf-8')""" and that works, of course, but I think it
should be managed at the gedit plugin level instead, since the whole
Gnome environment is using Unicode and the plugin should be aware of
that.
Now, about some solution, here is what I did to correct this problem, but I'm
not (yet ;-) ) a Python expert, so...
sudo sed -i -e '/get_text(inp, cur)$/s/$/.decode('utf-8')/'
/usr/lib/gedit-2/plugins/pythonconsole/console.py
sudo python2.5 /usr/lib/python2.5/py_compile.py
/usr/lib/gedit-2/plugins/pythonconsole/console.py
Explanation: add explicit 'utf-8' decoding anywhere the code get the
text input from the Python Console interface.
ProblemType: Bug
Architecture: i386
Date: Sun Oct 5 04:51:26 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gedit
Package: gedit 2.22.3-0ubuntu1 [modified:
usr/lib/gedit-2/plugins/pythonconsole/console.py]
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
PATH=/home/User
Name/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
LANG=fr_FR.UTF-8
SourcePackage: gedit
Uname: Linux 2.6.24-19-generic i686
** Affects: gedit (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug
--
missing utf-8 input decoding in the Python Console plugin
https://bugs.launchpad.net/bugs/278341
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278341] Re: missing utf-8 input decoding in the Python Console plugin
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/18224893/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/18224894/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/18224895/ProcStatus.txt ** Attachment removed: "ProcStatus.txt" http://launchpadlibrarian.net/18224895/ProcStatus.txt ** Attachment removed: "ProcMaps.txt" http://launchpadlibrarian.net/18224894/ProcMaps.txt ** Attachment removed: "Dependencies.txt" http://launchpadlibrarian.net/18224893/Dependencies.txt -- missing utf-8 input decoding in the Python Console plugin https://bugs.launchpad.net/bugs/278341 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278349] [NEW] pygtk-demo explicitly depends on python2.4
Public bug reported: Binary package hint: python-gtk2-doc Trying to run "pygtk-demo" from python-gtk2-doc 2.12.1-0ubuntu1 on Ubuntu 8.04(.1), I get an error about /usr/bin/python2.4 not found, but I can get it run using "python /usr/bin/pygtk-demo". Inspecting the /usr/bin/pygtk-demo script, we can read an explicit dependence on python2.4 in its first line: #! /usr/bin/python2.4 So I would suggest one of those two solutions: 1/ if it doesn't really depends on python2.4, change the first line to #!/usr/bin/env python 2/ if it really depends on python2.4, add some dependency (Recommends?) on python2.4 to the python-gtk2-doc package ** Affects: python-gtk2-doc (Ubuntu) Importance: Undecided Status: New -- pygtk-demo explicitly depends on python2.4 https://bugs.launchpad.net/bugs/278349 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278349] Re: pygtk-demo explicitly depends on python2.4
** Description changed: Binary package hint: python-gtk2-doc + + Note: this bug is not present anymore in Intrepid, but still it might be + considered for Hardy since it's a LTS. Trying to run "pygtk-demo" from python-gtk2-doc 2.12.1-0ubuntu1 on Ubuntu 8.04(.1), I get an error about /usr/bin/python2.4 not found, but I can get it run using "python /usr/bin/pygtk-demo". Inspecting the /usr/bin/pygtk-demo script, we can read an explicit dependence on python2.4 in its first line: #! /usr/bin/python2.4 So I would suggest one of those two solutions: 1/ if it doesn't really depends on python2.4, change the first line to #!/usr/bin/env python 2/ if it really depends on python2.4, add some dependency (Recommends?) on python2.4 to the python-gtk2-doc package -- pygtk-demo explicitly depends on python2.4 https://bugs.launchpad.net/bugs/278349 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278341] Re: missing utf-8 input decoding in the Python Console plugin
** Description changed:
Binary package hint: gedit
+
+ Note: this bug is still present in Intrepid beta version.
Some friend found a problem with the Python Console plugin in gedit
2.22.3-0ubuntu1, coming with Ubuntu 8.04(.1).
When inputing some utf-8 encoded text, it's evaluated as a byte string
instead, meaning it's not decoded as it should and as it effectively is
in an external "python" or "ipython" ran into a terminal.
Here is some example to reproduce and understand the bug:
1/ in a gedit Python Console:
>>> ch = u"Stéphanie"
>>> ch
u'St\xc3\xa9phanie'
>>> print ch[2]
Ã
2/ in a "python" command run in a terminal:
>>> ch = u"Stéphanie"
>>> ch
u'St\xe9phanie'
>>> print ch[2]
é
We could explicitly ask for input decoding using """ch =
'Stéphanie'.decode('utf-8')""" and that works, of course, but I think it
should be managed at the gedit plugin level instead, since the whole
Gnome environment is using Unicode and the plugin should be aware of
that.
Now, about some solution, here is what I did to correct this problem, but I'm
not (yet ;-) ) a Python expert, so...
sudo sed -i -e '/get_text(inp, cur)$/s/$/.decode('utf-8')/'
/usr/lib/gedit-2/plugins/pythonconsole/console.py
sudo python2.5 /usr/lib/python2.5/py_compile.py
/usr/lib/gedit-2/plugins/pythonconsole/console.py
Explanation: add explicit 'utf-8' decoding anywhere the code get the
text input from the Python Console interface.
-
- ProblemType: Bug
- Architecture: i386
- Date: Sun Oct 5 04:51:26 2008
- DistroRelease: Ubuntu 8.04
- ExecutablePath: /usr/bin/gedit
- Package: gedit 2.22.3-0ubuntu1 [modified:
usr/lib/gedit-2/plugins/pythonconsole/console.py]
- PackageArchitecture: i386
- ProcEnviron:
- SHELL=/bin/bash
- PATH=/home/User
Name/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
- LANG=fr_FR.UTF-8
- SourcePackage: gedit
- Uname: Linux 2.6.24-19-generic i686
** Tags removed: apport-bug
--
missing utf-8 input decoding in the Python Console plugin
https://bugs.launchpad.net/bugs/278341
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184741] Re: evince displays form data in a pdf file incorrectly
I would say this check-boxes display problem has been corrected in poppler 0.10.3, available in Jaunty. Ref.: https://bugs.freedesktop.org/show_bug.cgi?id=19359#c3 I am using Intrepid and I have just installed poppler 0.10.3 straight from Jaunty (without even rebuilding since it's a new version number) and backported Evince from Jaunty sources (really just rebuild) and it's working correctly with your document: the check-mark is on "No". On my side I still get problems with radio-buttons which do not get selected at all with this error message: Error: Missing 'Tf' operator in field's DA string And check-boxes and radio-buttons status do not get saved when saving a copy of the form, but that's another issue and I'm looking for another bug report on that point. -- evince displays form data in a pdf file incorrectly https://bugs.launchpad.net/bugs/184741 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 416000] [NEW] loosing %Title info => cups-pdf save as "_stdin_"
Public bug reported: Binary package hint: cups 1) Ubuntu release: Ubuntu 9.04 (Jaunty) 2) Package version: cups 1.3.9-17ubuntu3.2 3) What did I expect: PDF generated from printing through cups-pdf saved using the document title (from %Title in Postscript) as the file name ; it was working this way in Intrepid. 4) What happened instead: file are always saved as "_stdin_" (literally, and so overriding each other, but there is a workaround for this) whatever the document title is. cups-pdf use the document %Title information to generate the filename for the PDF to be saved. I discovered that the document entering cups- pdf processing was lacking this information, while it was available in the original Postscript document. So it's not a cups-pdf problem but a CUPS document processing instead. After investigating more, by putting cupsd LogLevel to debug, I also discovered that CUPS does process documents aimed at cups-pdf this way: [Job 380] envp[21]="CONTENT_TYPE=application/postscript" [Job 380] envp[24]="FINAL_CONTENT_TYPE=application/vnd.cups-postscript" [Job 380] Started filter /usr/lib/cups/filter/pstopdf (PID 4490) [Job 380] Started filter /usr/lib/cups/filter/pdftopdf (PID 4492) [Job 380] Started filter /usr/lib/cups/filter/cpdftocps (PID 4497) [Job 380] Started backend /usr/lib/cups/backend/cups-pdf (PID 4503) If I understand correctly, it first cleanup the Postscript code, then transform it into PDF (?), cleanup the PDF code and transform it back into Postscript before passing it to cups-pdf. I found that the pstopdf filter kept the %Title intact but the pdftopdf filter made it lost. IMHO, but I don't know printing processing well, this is a just a wrong path for going to cups-pdf. CUPS should just pass it to cups-pdf, after the minimal Postscript code cleanup and that's it. So this is the solution I choose to apply at my office: I moved away the file "/etc/cups/pstopdf.convs" (and restarted the "cups" service) so CUPS knew no more how to convert from Postscript to PDF. This made my day: PDF printing was saved using their document title again. So I declare this as a bug and suggest to take some action (may be mine, may be a better way) to allow other Ubuntu users to get it right without having to put their hand in it... ;-) ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- loosing %Title info => cups-pdf save as "_stdin_" https://bugs.launchpad.net/bugs/416000 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 42147] Re: "PDF Printer" does no not show up in "existing printers" (Dapper)
May be the shortest way to manage this problem is to extract the "file saving" part from the whole process to a "save file helper", then make only this being setuid root and well secured by going setuid to the final user as soon as it starts. Just my 2¢... -- "PDF Printer" does no not show up in "existing printers" (Dapper) https://launchpad.net/bugs/42147 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57239] video card no detected anymore
Public bug reported: Binary package hint: xserver-xorg-core My video card was running correctly until version 1:1.0.2-0ubuntu10.1 but is not anymore detected since the today upgrade to version 1:1.0.2-0ubuntu10.3. Downgrading to 1:1.0.2-0ubuntu10 solve the problem. Doing a "diff" between two Xwindow log file shows the last version fails to detect PCI busses higher than the first one (#0). +(II) PCI: Found 0 domains. -(II) PCI: 01:00:0: chip 10de,0168 card 104d,81eb rev a1 class 03,00,00 hdr 00 -(II) PCI: 06:05:0: chip 104c,ac8e card 2400, rev 00 class 06,07,00 hdr 82 -(II) PCI: 06:05:2: chip 104c,802e card 104d,818f rev 00 class 0c,00,10 hdr 80 -(II) PCI: 06:05:3: chip 104c,ac8f card 104d,8190 rev 00 class 01,80,00 hdr 80 -(II) PCI: 06:08:0: chip 8086,1068 card 104d,81d0 rev 03 class 02,00,00 hdr 00 -(II) PCI: 06:0b:0: chip 8086,4220 card 8086,2751 rev 05 class 02,80,00 hdr 00 Note that my video card is on bus #1 (from lspci): :01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce Go 6200 TurboCache] (rev a1) ** Affects: xorg-server (Ubuntu) Importance: Untriaged Status: Unconfirmed -- video card no detected anymore https://launchpad.net/bugs/57239 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57239] Re: video card no detected anymore
*** This bug is a duplicate of bug 57153 *** Don't hesitate to ask for any other information. I would be glad to help trying new versions too. -- video card no detected anymore https://launchpad.net/bugs/57239 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57239] Re: video card no detected anymore
*** This bug is a duplicate of bug 57153 *** ** Description changed: Binary package hint: xserver-xorg-core My video card was running correctly until version 1:1.0.2-0ubuntu10.1 - but is not anymore detected since the today upgrade to version - 1:1.0.2-0ubuntu10.3. Downgrading to 1:1.0.2-0ubuntu10 solve the problem. + but is not detected anymore since the today "dapper-updates" upgrade to + version 1:1.0.2-0ubuntu10.3. Downgrading to 1:1.0.2-0ubuntu10 solve the + problem. Doing a "diff" between two Xwindow log file shows the last version fails to detect PCI busses higher than the first one (#0). +(II) PCI: Found 0 domains. -(II) PCI: 01:00:0: chip 10de,0168 card 104d,81eb rev a1 class 03,00,00 hdr 00 -(II) PCI: 06:05:0: chip 104c,ac8e card 2400, rev 00 class 06,07,00 hdr 82 -(II) PCI: 06:05:2: chip 104c,802e card 104d,818f rev 00 class 0c,00,10 hdr 80 -(II) PCI: 06:05:3: chip 104c,ac8f card 104d,8190 rev 00 class 01,80,00 hdr 80 -(II) PCI: 06:08:0: chip 8086,1068 card 104d,81d0 rev 03 class 02,00,00 hdr 00 -(II) PCI: 06:0b:0: chip 8086,4220 card 8086,2751 rev 05 class 02,80,00 hdr 00 Note that my video card is on bus #1 (from lspci): :01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce Go 6200 TurboCache] (rev a1) -- video card no detected anymore https://launchpad.net/bugs/57239 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57239] Re: video card no detected anymore
*** This bug is a duplicate of bug 57153 *** Sorry for this duplicate... I should just have checked before creating this ticket... Anyway, version 1:1.0.2-0ubuntu10.4 (without PCI patch, downloaded from Rodrigo's link) is working just fine. -- video card no detected anymore https://launchpad.net/bugs/57239 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124805] Re: Ubuntu CD: language selection as first boot menu
It's an interesting idea... We may simply spread the word (along with the CD) to first press F2 to select the language at boot, or... we may totaly change the first image displayed at boot! Something like: every available languages displayed in the first frame in their own writing (like if we had press F2 straight at boot) then using cursor keys (or any other way) to choose one of them. In this case, this bug would probably better be attached to gfxboot. -- Ubuntu CD: language selection as first boot menu https://bugs.launchpad.net/bugs/124805 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
Ok... Let's precise a few points! ;-) First of all this bug report really should have been split into two or even three ones (not sure about the dependence between the first and second one): - one about the default keyboard choice for Vietnamese in gfxboot, currently VN but we need US (straight, not intl) ; - one about the default input method when running GTK2, currently VIQR (automatically chosen because of the "vi" locale) but we need SCIM ; - one about input method to add to language-support-vi, currently scim-tables-additional (which brings VIQR only) but we need instead scim-m17n AND m17n-db (which requires m17n-lib in turn) which brings VIQR (Vietnamese abroad), Telex (North Vietnam) and VNI (South Vietnam). Note on the last point that Ubuntu (in fact Debian) currently only provides the 1.3.1 version of m17n-db (and m17n-lib), which is usable enough but does not allow typing "freely" (which means putting the accentuation at the end of the word). This "free typing" thing is provided only from m17n-db 1.4.0 which I did package into our HanoiLUG repository and in my PPA ( https://launchpad.net/~progfou/+archive ). Hope this help. I hope these problems are not concerned by the current feature freeze (=> I hope we did not announce them too late...) since it's badly required here. The current situation is that we have to remaster the Ubuntu desktop CD at each release to try to enforce these policy a bit (but probably not doing this "The Right Way"™...). Feel free to ask us more information or even to ask us to re-report these bugs independently, in which case help on choosing the right package assignments would be greatly appreciated. Cheers, J.C. -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
Oh, and to answer Colin about console-setup (which is about console mode, isn't it?), in fact there are problems there too but far less important (IMHO) than in boot and graphic mode. This is because Vietnamese people are used to type without accents and so can deal with it if required. But ideally, we would need at a minimum correct accentuated characters display in console mode, which should be easily provided by just choosing some Vietnamese font like Vietnamese-Fixed or viscii10 or any other containing all Vietnamese pre-composed characters. I did'nt test this part much though... Requiring Unicode Level 2 for combining characters in console would be too much I guess, since the Linux kernel console code probably don't handle it, but we don't really need it anyway: pre-composed characters are enough to display any Vietnamese word correctly. About Vietnamese typing in console mode, we'll probably have to wait for the next Ubuntu release because we do not have any good solution to propose right now. We know of some, like using kernel module or library preloading, but personally I really dislike these kind of solutions and I'm looking for something more like tty input processing interception in user space. Cheers, J.C. -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
Ok. I've just check the console-setup package content and now I can see where it does apply. But yet I'm not sure to understand when the console-setup debconf options are configured during the installation. Is it from gfxboot or later from ubiquity? In fact we face problem as soon as we choose the "Vietnamese" language in gfxboot since it does imply a "vn" keyboard which really should be "us" instead. Then we face another problem when we run GTK2 applications (first with GDM, then with Ubiquity). It's because GTK2 has one of its default immodules (im-viqr.so) hinted for the "vi" language (see the result of "gtk-query-immodules-2.0") and so being automatically selected when in the "vi_VN" language environment. Here we probably need some GTK_IM_MODULE setting to disable this. In a final Vietnamese configuration we set it to scim, and I think it may apply to most of, if not all, other languages too. So I would recommend to let it be the default, especially before running Ubiquity. -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140051] Re: amd driver fails to autoconfigure
I've just discovered this bug report and reading it with interest. :-) I have a Linuterm, which is also based on the ThinCan DBE61. I'm trying to let it run LTSP on a Ubuntu "Gutsy" basis. Bartman, I've just downloaded and installed your packages. The Xorg server is able to start without crash or hang, in 800x600x8. I've attached my xorg.conf, Xorg.0.log and xwininfo. Let me know if you need any other information. I'll try to use this from know and see how far it's usable. Thanks for the research and packaging! ** Attachment added: "xorg.conf" http://launchpadlibrarian.net/11120601/xorg.conf_20080103_0026.txt -- amd driver fails to autoconfigure https://bugs.launchpad.net/bugs/140051 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140051] Re: amd driver fails to autoconfigure
Oh... We can't attach more than one file at a time?? ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/11120605/Xorg.0.log_20080103_0026.txt.bz2 -- amd driver fails to autoconfigure https://bugs.launchpad.net/bugs/140051 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140051] Re: amd driver fails to autoconfigure
** Attachment added: "xwininfo" http://launchpadlibrarian.net/11120631/xwininfo-root_20080103_0026.txt -- amd driver fails to autoconfigure https://bugs.launchpad.net/bugs/140051 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140051] Re: amd driver fails to autoconfigure
Great! I'm able to use Xorg at 1280x1024x16 without any trouble! :-) I just had to tune a few things manually, like: - HorizSync & VertRefresh to allow full screen size - DefaultDepth to get 16 bits depth - Modes in SubSection "Display" to get the size I wanted But we should be able to get most of this automagically. See what "ddcprobe" gives: vbe: VESA 2.0 detected. oem: Advanced Micro Devices memory: 16384kb mode: 640x480x256 mode: 800x600x256 mode: 1024x768x256 mode: 1280x1024x256 mode: 640x480x32k mode: 640x480x64k mode: 640x480x16m mode: 800x600x32k mode: 800x600x64k mode: 800x600x16m mode: 1024x768x32k mode: 1024x768x64k mode: 1024x768x16m mode: 1280x1024x32k mode: 1280x1024x64k mode: 1280x1024x16m mode: 1600x1200x32k mode: 1600x1200x64k edid: edidfail >From that we could guess horizontal & vertical data... -- amd driver fails to autoconfigure https://bugs.launchpad.net/bugs/140051 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121540] Re: "Where are you?" SAIGON should be named "Ho Chi Minh City"
I can hardly understand the "too long" argument when "Asia/Ho_Chi_Minh_City" is only 21 characters long but you can find other time zone specification as long as 30 characters, eg "America/North_Dakota/New_Salem"... Note also that, after tzdata source inspection, I can see multiple translations of "Saigon" into "Ho Chi Minh" which is simply totally wrong. At the minimum "Asia/Saigon" should be changed to "Asia/Ho_Chi_Minh_City", since the city name was changed to the name of the Vietnamese President after the liberation from U.S.A. people in 1975, the old name remembering to some people the old ages. But it *really* should be changed to "Asia/Hanoi" because it is the "Vietnamese's main city" from the Vietnamese government point of view! Microsoft have done this change (moving from "Saigon" to "Hanoi") since Windows XP, it's 6 years ago and I can't believe it takes so long to make the same with FOSS... Please don't give them arguments against us!! :-( ** Bug watch added: Debian Bug tracker #471305 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471305 ** Also affects: tzdata (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471305 Importance: Unknown Status: Unknown -- "Where are you?" SAIGON should be named "Ho Chi Minh City" https://bugs.launchpad.net/bugs/121540 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
Thanks for this! About which SCIM method to select, no problem. As soon as all required Vietnamese input methods are available, it's alright. I also think it's better to have no default for this for "political" reasons (classic North/South conflicts). ;-) The m17n 1.4.0 is not absolutely required, but... The 1.3.1 version has a nasty backspace bug: you have to use shift backspace, or comment two lines in the input method source file. The "free typing" (entering tone mark at the end of the word) is highly appreciated and only (correctly) available from version 1.4.0. About the m17n in Debian, there have been some wishlist bug reports for upgrade but without reaction (I didn't check recently though). I had no specific problem to package the 1.4.0. I just re-used the packaging information from Debian to do it, without much change (disabled patch for Tamil included upstream). Thanks for taking this. I have finally downloaded Hardy Alpha 6 successfully and will now be able to test the Colin correction included. -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
Wait is always acceptable if we get what we want right in time! ;-) Do you think he could do it soon enough to let it in Hardy? If not, I've attached what is needed to correct the backspace issue. ** Attachment added: "Correct Vietnamese Telex backspace issue in m17n-db 1.3.1" http://launchpadlibrarian.net/12598684/m17n-db_1.3.1_vi-telex.mim.diff -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
I've just tested Hardy Alpha6 and here are my comments about Vietnamese support: - default keyboard is now US at boot, in Xorg and Ubiquity, thanks to Colin Watson - default GTK input method is "system" which still activate VIQR by default because of the im-viqr.so im-module hint for "vi" environment Here I can see two options: - let SCIM be the default input method in GTK => it's definitely the preferred long term solution (for Vietnamese and probably others too) but it sometime requires tuning before being fully usable, especially when mixing different locales/keyboard (eg Vietnamese with AZERTY), so this solution would require more testing and would not be appropriate right before the Hardy release ; - disable the hint for Vietnamese locale in the im-viqr.so GTK im-module so GTK input will just use straight Xorg keyboard which is now US by default => it's probably the preferred solution here since it would affect only Vietnamese support and nothing else, so even in the case it would create troubles they would be only ours. ;-) ** Also affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
Answer to Sebastien Bacher: Problem summary: When choosing some Vietnamese locale like "vi_VN", GTK is activating its VIQR input method automatically (because of im-module hint) which leads to unexpected typing (for most Vietnamese people, not used to this input method) and even loss of characters in input fields (eg an 'e' at the end of a word will be loosed if you don't type a space after it). Because of this we often get complaints about typing being wrong (like password not working) which leads to bad Ubuntu experience for Vietnamese people. What we expect now: We would like to get the VIQR GTK input method module *not activated by default* for a Vietnamese locale. It is probably easy to solve by just removing the "vi" hint from the GTK "im-viqr.so" im-module. I think it's the last step to solve this "Bad default choices for Vietnamese" now. Don't hesitate to ask more or contact me directly as needed. TIA, J.C. -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
[More Hardy Alpha6 Vietnamese support tests] It seems it's not exactly what I supposed... I see a strange GTK behavior here! When running a gnome-terminal, the default GTK input method is "system" and VIQR is *not* activated. When running ubiquity, the default GTK input method is also "system" but the VIQR input method *is* activated. You can see the difference between input results in the attached screenshot. So here I'm puzzled... I have no clue why the behavior is different between ubiquity or gnome-terminal, both being GTK compliant applications AFAIK... The good news is that GTK doesn't seem to "eat" characters anymore: when I type a final 'e' and then press Enter I still get the 'e' in the input. But still the VIQR input method being running by default is an unwanted feature. Let's give another example: people typing a password containing "e^" will get it entered as "e^" in console (or any other "not-through-GTK" input) but as "ê" in GTK, leading to password problems confusion. ** Attachment added: "Hardy Alpha6 Vietnamese support - strange behavior in GTK" http://launchpadlibrarian.net/12605795/HardyAlpha6Vietnamese.png -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
Thanks Ming Hua for you summary which is absolutely exact. Your patch seems quite appropriate too, at least for the previous known GTK+ behavior. Can somebody generate a .deb from this? Else I'll try through my PPA, but I'm not sure to have time for this today... -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
We could organize intensive testing for Vietnamese, but I'm afraid we won't be able to test every single language provided by m17n-db... :-/ About the language-support-input-vi metapackage, I do confirm that adding scim-m17n is enough and does work from Hardy Alpha 6 (I've just tested it). It was not enough up to and including Gutsy because libm17n-0 didn't depend on m17n-db which is the case now. -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103328] Re: Correction in m17n vi-telex.mim
I do confirm the correction asked for line 234. There is only one instance of (insert "aff") in this file which really should be corrected to (insert "af"). You can find a second confirmation of this here: http://en.wikipedia.org/wiki/Telex_(IME) " To write a tone marking key as a normal character, one has to press it twice: "herr" becomes "her". " I do confirm the correction asked for line 367 and 368, except that semicolon (;) should be doubled. There already is a fix proposal by Arne Goetje, see here: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/191451/comments/31 ** Changed in: m17n-db (Ubuntu) Status: New => Confirmed -- Correction in m17n vi-telex.mim https://bugs.launchpad.net/bugs/103328 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
not really a scim problem, and a fixed has been done for m17n-db to get a minimal working environment ** Changed in: m17n-db (Ubuntu) Sourcepackagename: scim => m17n-db Status: Confirmed => Fix Committed -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 186174] Re: Please update to 1.5
Version 1.4.0 or later is also required for free typing in Vietnamese which is what people are used to here in Vietnam. And about the Debian update: https://bugs.launchpad.net/ubuntu/+source /m17n-db/+bug/191451/comments/22 ** Changed in: m17n-db (Ubuntu) Status: Invalid => New -- Please update to 1.5 https://bugs.launchpad.net/bugs/186174 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
(not sure about what is the exact meaning of "Fix Committed" in term of bug management...) ** Changed in: m17n-db (Ubuntu) Status: Fix Committed => In Progress -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 186174] Re: Please update to 1.5
** Bug watch added: Debian Bug tracker #434043 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434043 ** Also affects: m17n-db (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434043 Importance: Unknown Status: Unknown -- Please update to 1.5 https://bugs.launchpad.net/bugs/186174 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121540] Re: "Where are you?" SAIGON should be named "Ho Chi Minh City"
FYI... Following indication from Clint Adams (see Debian's bug link at top of this page) I'm discussing this at the source: http://thread.gmane.org/gmane.comp.time.tz/2122 As Martin Pitt already said, people from tzdata have good arguments to keep going with current rules, which define time zone names using the "most populous" cities. Hopefully they already agreed to change "Saigon" to "Ho_Chi_Minh", but there's not enough space to append "_City" to the name since the POSIX limit is 14 characters for each path component. So as the last resort option, I'm trying to let "Hanoi" be a "link" to "Ho_Chi_Minh" so one can choose either one. Not sure if they'll agree on that since it requires more management on their side, especially if "everybody" start to ask to add link for the Capitol City... -- "Where are you?" SAIGON should be named "Ho Chi Minh City" https://bugs.launchpad.net/bugs/121540 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121540] Re: "Where are you?" SAIGON should be named "Ho Chi Minh City"
FYI... I've post a closing answer to this thread. Summary here: 1) no more ask for switch to Hanoi in tzdata ; 2) no more ask for Hanoi link in tzdata ; 3) confirmed the necessity to switch from "Saigon" to "Ho_Chi_Minh". It seems that 3) is being considered by tzdata maintainers, so we'll probably close this bug soon. As for 1) and 2) I've understood tzdata is not the right place to do this kind of change so I'll suggest another way: propose multiple city names for time zones at the user interface level, as we can see in some other systems. Or may be simply don't change anything and explain people what is the time zone naming simple and only rule: the most populous city, and not the capitol as we usually guess it should be... Anyway, I also understand that this change is not Ubuntu specific and so I'll eventually continue this work at the source in the Debian bug report (linked at top of this page). Thanks to everybody having participated in this, especially Martin Pitt for the first step with upstream. -- "Where are you?" SAIGON should be named "Ho Chi Minh City" https://bugs.launchpad.net/bugs/121540 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
Answer to Sebstien Bacher: Sorry for current delay in my answers: I'm currently busy working longer than planed in Hồ Chí Minh City and have no time to do the requested test... Could somebody else test it please? But I'm not sure every Vietnamese people subscribed to this bug and interested in testing are able to rebuild a package including the patch proposed. Could somebody build such a package for them please? Answer to Vũ Đỗ Quỳnh: Please check bug 103328: you should not need to follow our procedure anymore since it has been integrated already. But it has been done one day after the beta release so the correction is probably not available in the beta. More on all this when I come back next week, sorry... -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
Forgot to answer on one point to Sebastien Bacher: This change is about disabling Vietnamese typing by default in GTK+, independently of the distribution, so is suitable for upstream, IMHO. But, we ask for this to be included in Hardy to help us promote Ubuntu deployment using a LTS with already good Vietnamese support and directly from the original Ubuntu, not the derivative some people started to do for Vietnam (myself, but others too). -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121540] Re: "Where are you?" SAIGON should be named "Ho Chi Minh City"
I have remastered the Hardy beta LiveCD after having updated this package and I do confirm we can now see "Ho Chi Minh" as the default timezone choice for Vietnam in Ubiquity. So this bug can now be closed. Many thanks! -- "Where are you?" SAIGON should be named "Ho Chi Minh City" https://bugs.launchpad.net/bugs/121540 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103328] Re: Correction in m17n vi-telex.mim
I have remastered the Hardy beta LiveCD after having installed the scim- m17n package to test m17n-db bugs corrections and I do confirm that Telex is now working appropriately (no more backspace or "aff" bugs) ! So this bug can now be closed. Many thanks! -- Correction in m17n vi-telex.mim https://bugs.launchpad.net/bugs/103328 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
I have remastered the Hardy beta LiveCD after having updated the gtk+2.0 package and I do confirm that VIQR is not anymore activated by default for Vietnamese locale! I have also installed the scim-m17n package to test m17n-db bugs corrections and I do confirm that Telex is now working appropriately (no more backspace or "aff" bugs) ! So this bug can now be closed. Many thanks! -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191451] Re: Bad default choices for Vietnamese installation
About SCIM (and everything else), look at my first comment on February 26, 2008, detailing all requirements. -- Bad default choices for Vietnamese installation https://bugs.launchpad.net/bugs/191451 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251709] Re: rdesktop works bad with several keyboard layouts
It appears _there actually is_ some wrong/bad consequences when activating capslock, especially when going in/out the rdesktop window. It then sometimes makes the capslock modifier apparently stuck (permanently active) in the GNOME environment which alter a lot of keyboard and mouse actions. It's all suppositions (for now) because I didn't experienced that myself (it was some colleagues reporting it). So I will investigate more (since we badly need it at work) before posting a debdiff. -- rdesktop works bad with several keyboard layouts https://bugs.launchpad.net/bugs/251709 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 416000] Re: loosing %Title info => cups-pdf save as "_stdin_"
Does my proposed solution (moving away pstopdf.convs) works in your case? BTW, how are you converting your PPT into PDF? Doesn't OpenOffice have a direct PDF rendering function (totally independent from CUPS) which could be used for that? -- loosing %Title info => cups-pdf save as "_stdin_" https://bugs.launchpad.net/bugs/416000 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 433495] Re: [Karmic] Gajim fails to work with indicator applet
It has been fixed upstream already, see the bug URL I've just linked. Could anybody ensure this fix will be integrated for the Karmic final release? BTW, since this bug was because of an API change in the python-indicate package, developers ask for a way to get a module version number (from inside Python, of course). ** Bug watch added: Gajim Trac #5271 http://trac.gajim.org/ticket/5271 ** Also affects: gajim via http://trac.gajim.org/ticket/5271 Importance: Unknown Status: Unknown -- [Karmic] Gajim fails to work with indicator applet https://bugs.launchpad.net/bugs/433495 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 451930] Re: telepathy-salut assert failure: telepathy-salut: glib-watch.c:205: timeout_free: Assertion `!t->dead' failed.
*** This bug is a duplicate of bug 441694 *** https://bugs.launchpad.net/bugs/441694 Apport retracing service a écrit : > *** This bug is a duplicate of bug 441694 *** > https://bugs.launchpad.net/bugs/441694 > > This particular crash has already been reported and is a duplicate of bug > #441694, so is being marked as such. Please look at the other bug report to > see if there is any missing information that you can provide, or to see if > there is a workaround for the bug. Additionally, any further discussion > regarding the bug should occur in the other report. Please continue to > report any other bugs you may find. > Ok, it's the usual way, but there is something unusual here... This is what I get when going on https://bugs.launchpad.net/bugs/441694 : Not allowed here Sorry, you don't have permission to access this page. You are logged in as Jean Christophe André. Could it be possible you forgot to switch that other bug to public access? Or at least give my account access to it? -- Jean Christophe "プログフ" ANDRÉ — ✧ — Responsable technique régional Bureau Asie-Pacifique (BAP)— ✧ — http://www.asie-pacifique.auf.org/ Agence universitaire de la Francophonie (AuF) — ✧ — http://www.auf.org/ Adresse postale : AUF, 21 Lê Thánh Tông, T.T. Hoàn Kiếm, Hà Nội, Việt Nam Tél. : +84 4 9331108 ✦ Fax : +84 4 8247383 ✦ Cellul. : +84 91 3248747 ⎧ Note personnelle: merci d'éviter de m'envoyer des fichiers PowerPoint ⎫ ⎩ ou Word, cf http://www.gnu.org/philosophy/no-word-attachments.fr.html ⎭ -- telepathy-salut assert failure: telepathy-salut: glib-watch.c:205: timeout_free: Assertion `!t->dead' failed. https://bugs.launchpad.net/bugs/451930 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409813] Re: hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned)
But Karmic is bringing OOo 3.1.1... shouldn't this package be available at the same version as OOo? -- hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned) https://bugs.launchpad.net/bugs/409813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409813] Re: hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned)
Anyway, having hunspell-vi (and others hunspell-*) conflicting with any (unversioned) Thunderbird is really blocking hard against getting Vietnamese language support in Ubuntu (since we can't spellcheck it in OpenOffice, Firefox or Thunderbird without this package)... So, please find a way (and Arne's way seems quite good to me, wouldn't it apply as easily to 3.0.1 as well?), I'm willing to help as much as I can to get this make it into Karmic! TIA (reminder: we just need to change unversioned Conflicts: to versioned one, against Thunderbird (<< 2.0.0.1+0dfsg-0)) -- hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned) https://bugs.launchpad.net/bugs/409813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 433495] Re: [Karmic] Gajim fails to work with indicator applet
@pavolzetor This traceback is _not_ related to the indicator applet support problem. It's about a wrong number of columns in an SQL instruction while writing in the log database. I suppose that may be because of a log database structure change and a problem with database migration (or no migration at all). You should open an other bug about this one (please first check if there is already one about SQL error or log database). -- [Karmic] Gajim fails to work with indicator applet https://bugs.launchpad.net/bugs/433495 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234981] Re: rdesktop shift / caps lock problem with keymap fr (and others?)
** This bug has been marked a duplicate of bug 251709 rdesktop works bad with several keyboard layouts ** This bug is no longer a duplicate of bug 251709 rdesktop works bad with several keyboard layouts -- rdesktop shift / caps lock problem with keymap fr (and others?) https://bugs.launchpad.net/bugs/234981 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 254968] Re: CAPS LOCK doesn't work in rdesktop 1.6
*** This bug is a duplicate of bug 251709 *** https://bugs.launchpad.net/bugs/251709 @Daniel, yes it's a workaround, but at least it lets CapsLock being usable again! The CapsLock synchronization between inside and outside is another matter, which is not as important as just being able to switch it in the first place. Note: this problem is still present in Jaunty and Karmic RC. -- CAPS LOCK doesn't work in rdesktop 1.6 https://bugs.launchpad.net/bugs/254968 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251709] Re: rdesktop works bad with several keyboard layouts
This problem is still present in Jaunty and Karmic RC (whatever US or French keyboard). I'm going to try Michael's patch above. -- rdesktop works bad with several keyboard layouts https://bugs.launchpad.net/bugs/251709 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251709] Re: rdesktop works bad with several keyboard layouts
Ok. After some wide investigations (checking raw keyboard scan codes with "showkey", checking Xorg key codes with "xev", checking GNOME keyboard selection, checking/removing SCIM/iBus keyboard alteration in the way, checking console keyboard choice in "/etc/default/console-setup") and after trying to tune rdesktop keyboard files, some friend and I found that the problem in our case can be separated in two parts: - rdesktop's capslock problem, easily solved using the solution given in comment #29 - xorg's numeric keypad decimal separator problem, easily solved with the following Xmodmap entry: keycode 91 = KP_Delete KP_Decimal KP_Delete KP_Decimal KP_Delete KP_Decimal I can't understand why this solution to the capslock problem has not been integrated since Intrepid... There is only people telling it works, nobody complaining about regression after that, so what?!? About the numeric keypad decimal problem, in our case it's specific to the French keyboard (no problem with the US keyboard) which defines it this way: keycode 91 = KP_Delete period KP_Delete period comma U202F comma U202F KP_Delete period The French keyboard I'm talking about is this one (from "/etc/default/console-setup") : XKBMODEL="pc105" XKBLAYOUT="fr" XKBVARIANT="oss" XKBOPTIONS="" -- rdesktop works bad with several keyboard layouts https://bugs.launchpad.net/bugs/251709 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251709] Re: rdesktop works bad with several keyboard layouts
Thanks for the directions. Starting to learn how to use debdiff... -- rdesktop works bad with several keyboard layouts https://bugs.launchpad.net/bugs/251709 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409813] Re: hunspell-hu conflicts with thunderbird (unversioned)
Same problem with hunspell-vi... hunspell-fr and hunspell-en-us have correct version'd conflict dependencies on Thunderbird < 2.0.0.1 but not a few others like those we need here... -- hunspell-hu conflicts with thunderbird (unversioned) https://bugs.launchpad.net/bugs/409813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409813] Re: hunspell-hu conflicts with thunderbird (unversioned)
Arne, I have assigned this bug to you since you were assigned to the bug #227711 which is exactly the same. ** Changed in: openoffice.org-dictionaries (Ubuntu) Assignee: (unassigned) => Arne Goetje (arnegoetje) -- hunspell-hu conflicts with thunderbird (unversioned) https://bugs.launchpad.net/bugs/409813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409813] Re: hunspell-hu & hunspell-vi conflict with thunderbird (unversioned)
** Summary changed: - hunspell-hu conflicts with thunderbird (unversioned) + hunspell-hu & hunspell-vi conflict with thunderbird (unversioned) -- hunspell-hu & hunspell-vi conflict with thunderbird (unversioned) https://bugs.launchpad.net/bugs/409813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409813] Re: hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned)
** Summary changed: - hunspell-hu & hunspell-vi conflict with thunderbird (unversioned) + hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned) -- hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned) https://bugs.launchpad.net/bugs/409813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409813] Re: hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned)
I've just tested the use of the current hunspell-vi package (forcing its installation) in Jaunty and it works perfectly with Thunderbird (and Firefox too). -- hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned) https://bugs.launchpad.net/bugs/409813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409813] Re: hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned)
Same test in Hardy (forced hunspell-vi installation) and it works perfectly with Thunderbird too. -- hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned) https://bugs.launchpad.net/bugs/409813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409813] Re: hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned)
Ahem... The previous comment was meant to be about Karmic, not Hardy... :-P I didn't test in Hardy. It works in Jaunty and Karmic (beta + every updates as of now). -- hunspell-hu, hunspell-vi and probably others hunspell-* conflict with thunderbird (unversioned) https://bugs.launchpad.net/bugs/409813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 42147] Re: "PDF Printer" does no not show up in "existing printers" (Dapper)
Because it wants to put the resulting PDF files in the home directory! It looks totaly wrong to me, but that's the way it works right now. -- "PDF Printer" does no not show up in "existing printers" (Dapper) https://launchpad.net/bugs/42147 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***
On my side, the error only shows once per session, yes, but… my request also never works as expected, ever. I just want to use the unity-scope-calculator as usual — “Dashing” for calc:1+2 — but it doesn't work, neither the first time nor the next ones. Is this scope obsolete? Or is it supposed to still work? If the whole scope-runner-dbus.py thing is affected, it means this problem is affecting all Python scopes, that is: $ ls -l /usr/share/unity-scopes/*/*_daemon.py -rw-r--r-- 1 root root 7028 mar 28 2014 /usr/share/unity-scopes/calculator/unity_calculator_daemon.py -rw-r--r-- 1 root root 10731 jui 23 2013 /usr/share/unity-scopes/chromiumbookmarks/unity_chromiumbookmarks_daemon.py -rw-r--r-- 1 root root 10087 jui 23 2013 /usr/share/unity-scopes/colourlovers/unity_colourlovers_daemon.py -rw-r--r-- 1 root root 9772 mar 28 2014 /usr/share/unity-scopes/devhelp/unity_devhelp_daemon.py -rwxr-xr-x 1 root root 25607 mar 18 2014 /usr/share/unity-scopes/facebook/unity_facebook_daemon.py -rw-r--r-- 1 root root 8922 aoû 9 2013 /usr/share/unity-scopes/firefoxbookmarks/unity_firefoxbookmarks_daemon.py -rwxr-xr-x 1 root root 26075 mar 18 2014 /usr/share/unity-scopes/flickr/unity_flickr_daemon.py -rwxr-xr-x 1 root root 13883 nov 25 11:34 /usr/share/unity-scopes/gdrive/unity_gdrive_daemon.py -rwxr-xr-x 1 root root 6939 mar 24 2014 /usr/share/unity-scopes/manpages/unity_manpages_daemon.py -rw-r--r-- 1 root root 8485 jui 23 2013 /usr/share/unity-scopes/openclipart/unity_openclipart_daemon.py -rwxr-xr-x 1 root root 21877 mar 18 2014 /usr/share/unity-scopes/picasa/unity_picasa_daemon.py -rwxr-xr-x 1 root root 24576 mar 18 2014 /usr/share/unity-scopes/shotwell/unity_shotwell_daemon.py -rw-r--r-- 1 root root 8213 mar 28 2014 /usr/share/unity-scopes/texdoc/unity_texdoc_daemon.py -rw-r--r-- 1 root root 8574 jui 23 2013 /usr/share/unity-scopes/tomboy/unity_tomboy_daemon.py -rw-r--r-- 1 root root 8993 jui 23 2013 /usr/share/unity-scopes/virtualbox/unity_virtualbox_daemon.py -rw-r--r-- 1 root root 9967 jui 23 2013 /usr/share/unity-scopes/yelp/unity_yelp_daemon.py -rw-r--r-- 1 root root 11082 jui 23 2013 /usr/share/unity-scopes/zotero/unity_zotero_daemon.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538471 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1538471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***
I forgot to mention: I rely on on the Python scopes infrastructure to work as expected to endorse the deployment of this Xenial LTS over 400 computers in the NGO I'm working for… Since I love Ubuntu and advocate for it at work, if you need any more tests, it will be my pleasure to volunteer! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538471 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1538471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
FYI, after a kernel upgrade the NVIDIA driver was unusable again. This time was because of the DKMS mechanism which, for whatever reason I didn't investigate yet (could it be because of the apt-pinning??), didn't success to build and install the nvidia_304.ko module for the new kernel. If that happens to you, the solution is to run these commands: dpkg-reconfigure nvidia-304 service lightdm restart (no need to reboot) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 411358]
Hi, Thanks mainly to Jonathan and jhorak work, I've come to find an easy solution to manage this problem without patching/recompiling anything. We just need to intercept the gconf_client_get_string call using LD_PRELOAD to make it answer nicely on a search containing a '+' symbol. You will find an example how to do it at http://git.auf.org/?p=auf- poste-client.git;a=tree;f=lucid/auf-thunderbird-hack This example is very specific to Ubuntu “Lucid Lynx” 10.04 LTS, because it is our current concern for now. But it's only about 20 lines of code so it should be easy to adapt to any other context. Thanks to everyone for their comments here, which allowed me to manage this problem quite fast, in about half a day! Greetings, J.C. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/411358 Title: Thunderbird2 gconf gmt problem 'Bad key or directory name' because of plus symbol (+) To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/411358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
In my case I have a GeForce 6150SE so I really need this 304.131 and can't higher version like 340.xx. For people needing to downgrade, this is one (among others) correct way to do so with Ubuntu 16.04: - first create a file named /etc/apt/preferences.d/local-nvidia-quirks with the following content: Explanation: block this specifique update because of OpenGL problem with 304.132 Package: nvidia-304 Pin: version 304.132-0ubuntu0.16.04.2 Pin-Priority: -10 Explanation: block this specifique update because of OpenGL problem with 304.132 Package: nvidia-opencl-icd-304 Pin: version 304.132-0ubuntu0.16.04.2 Pin-Priority: -10 - then reinstall the working old packages (they are still available in the repository): sudo apt install nvidia-304=304.131-0ubuntu3 nvidia-opencl- icd-304=304.131-0ubuntu3 - finally, reboot your computer (because it also affects the initrd boot image) The previous way only blocks the currently known not working version, without blocking future updates. If you want a way to stay at the known working version without further updates, here is the content you should use for your /etc/apt/preferences.d/local-nvidia-quirks: Explanation: do not use any other version than this one, ever (priority 1001 will ensure that) Package: nvidia-304 Pin: version 304.131-0ubuntu3 Pin-Priority: 1001 Explanation: do not use any other version than this one, ever (priority 1001 will ensure that) Package: nvidia-opencl-icd-304 Pin: version 304.131-0ubuntu3 Pin-Priority: 1001 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
Sorry for the typos and long-lines… Can't find a way to edit back my posts… :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***
Not sure if this helps but it appears this problem only occurs on a 64-bit system. I did a Xenial 32-bit installation recently and the Python scopes (I tested calc: and manpages:) worked properly. On a Xenial 64-bit installation, even with the very last updates (especially the recent libunity-core), it still crashes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538471 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1538471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
FYI, downgrade “solved” the problem for me too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
A debdiff between the packages shows the difference is mainly a version upgrade from 304.131 to 304.132. And it seems a lot of people are experiencing problems with version 304.132, cf https://devtalk.nvidia.com/search/more/sitecommentsearch/304.132/ A specific thread retained my attention: https://devtalk.nvidia.com/default/topic/968892/linux/geforce-7300le- with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request- badvalue-quot-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
** Bug watch added: Debian Bug tracker #840342 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840342 ** Also affects: nvidia-graphics-drivers-legacy-304xx (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840342 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
Since this problem greatly affects usability (no graphic login anymore), may be it's worth (in the users' point of view) creating a “fake version” security-upgrade like "304.132-0ubuntu0.16.04.2+really304.131" to fill the gap while waiting for Nvidia to provide a fix for 304.132, IMHO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639180] Re: no login possible after update to nvidia 304.132
Well… Switching to another window manager doesn't solve the “any 3D/GLX app would crash” issue… In my case I would have preferred to use the nouveau driver from the beginning, except that for ancient cards like the 6150SE it makes the whole system freeze after only a few minutes… Finally, I was so p*ssed off about this bug and the fact that I have to tune this or that after some security update, that I looked back into this nouveau driver bug for 2 days and finally found a way to use it without patching/installing anything or totally disabling all graphic accelerations. (options nouveau config="PMPEG=0" => works for me/my card) So now that I have returned to The open and happy world and am not concerned with this bug anymore. Goodluck everybody else! :-P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***
After having installed 2 identical VM (PXE + preseed), with the only difference being the architecture (32-bit vs 64-bit), I can now confirm that the Python scopes are working on a 32-bit install and crashing on a 64-bit install, with exactly the same requests made on both sides (calc:1+1, man:calc). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538471 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1538471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***
I confirm the Python scopes are now, after having applied the pygobject update, working on a Xenial 64-bit system and still working (= no regression) on a 32-bit one. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538471 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1538471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447345] Re: Support the unprivileged namespace sandbox
Same here with Evince not being able to lauch the browser when you clic on a link inside a PDF: apparmor="DENIED" operation="capable" profile="/usr/bin/evince//sanitized_helper" pid=16137 comm="chromium- browse" capability=21 capname="sys_admin" ** Also affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447345 Title: Support the unprivileged namespace sandbox To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1447345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455791] Re: v4l2loopback-dkms 0.8.0-1: v4l2loopback kernel module failed to build
According to the Debian bug #786779, upgrading to v42loopback 0.9.0 should solve this issue as it compile properly with newer Linux kernels (including 4.0). ** Bug watch added: Debian Bug tracker #786779 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786779 ** Also affects: v4l2loopback (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786779 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455791 Title: v4l2loopback-dkms 0.8.0-1: v4l2loopback kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1455791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455791] Re: v4l2loopback-dkms 0.8.0-1: v4l2loopback kernel module failed to build
FYI, debuild'ing the last Debian package on Trusty solved the problem for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455791 Title: v4l2loopback-dkms 0.8.0-1: v4l2loopback kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1455791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317602] Re: package linux-image-3.13.0-24-generic 3.13.0-24.46 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Trying a 14.04 netboot today still fails the same way. I had to do this to allow the installation to continue: - switch to the 2nd console (alt+f2) - press enter to get a command prompt - type these commands: chroot /target rm /initrd.img* dpkg --configure -a # it runs the linux-image-extra-3.13.0-24-generic configuration exit # the chroot exit # the shell - switch back to the 1st console (alt+f1) - continue the installation by re-running the last step (software installation) This allows the installation to continue, but this problem definitely forbids fully automated/unattended installation… :-( IMHO, it seems two kernels are trying to make the same link to /initrd.img and the second one fails to do it because it already exists, making its configuration (and the installation) to stop. The second kernel (3.13.0-66) is a security update coming from trusty- updates (and trusty-security). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317602 Title: package linux-image-3.13.0-24-generic 3.13.0-24.46 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317602] Re: package linux-image-3.13.0-24-generic 3.13.0-24.46 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Changing my netboot preseed configuration from "d-i pkgsel/upgrade select full-upgrade" to "d-i pkgsel/upgrade select none" was enough to get around this problem. Hopefully the installation process still apply the security updates. It seems to do it later in time so it's probably why it doesn't fall into this very specific initrd.img symlink race condition case anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317602 Title: package linux-image-3.13.0-24-generic 3.13.0-24.46 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547431] Re: Does not allow appstream files
For those who wonder (because of the lack of informative comments for standard _users_...) the fix has been released in upstream version 0.8.8. Ref. : https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p =apt-cacher-ng/apt-cacher- ng.git;a=commitdiff;h=c54b88bb28781b13a35c7bbc227066c7c141af9c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547431 Title: Does not allow appstream files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1547431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909139] Re: preseed_fetch no longer works with relative URL
Same problem in Trusty. ** Also affects: preseed (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678694 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909139 Title: preseed_fetch no longer works with relative URL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/909139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998759] Re: hud-service frequently tries to accesses non existing files causing high disk/network activity
I confirm on my side that the gsetting suggestion from Ted Gould (comment #8) is working for a user with his homedir over NFS. I have now put it in my default Ubuntu deployment strategy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998759 Title: hud-service frequently tries to accesses non existing files causing high disk/network activity To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/998759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 643289] Re: idmapd does not starts to work after system reboot
Hi guys! First thanks for your analysis I'm in the process to let deploy more than 400 computers using the current LTS with NFSv4 (and autofs here too) and I'm stuck at randomly facing exactly the same problem of idmapd failing to start, here because of the late rpc_pipefs start: Feb 28 22:20:42 test kernel: [6.305583] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). Feb 28 22:20:43 test rpc.statd[888]: Version 1.1.6 Starting Feb 28 22:20:43 test rpc.statd[888]: Flags: Feb 28 22:20:43 test rpc.idmapd[901]: main: open(/var/lib/nfs/rpc_pipefs/nfs): No such file or directory Feb 28 22:20:43 test init: idmapd main process (901) terminated with status 1 Feb 28 22:20:43 test init: idmapd main process ended, respawning ... (more of them) Feb 28 22:20:43 test init: idmapd main process (954) terminated with status 1 Feb 28 22:20:43 test init: idmapd respawning too fast, stopped So what's next? Is there any package ready for testing yet? Cheers, J.C. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/643289 Title: idmapd does not starts to work after system reboot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 643289] Re: idmapd does not starts to work after system reboot
Thanks Alexander! I've investigated your patches and find them very interesting, clearly based on the same model of portmap/portmap-wait. Still, I was looking for the less intrusive possible modification in the time being (while this bug is being investigated thoughtfully, I hope, by Canonical and/or the community) so I just added this line at the end of idmapd's pre-start script: if ! mountpoint -q /var/lib/nfs/rpc_pipefs ; then do_modprobe sunrpc ; mount -t rpc_pipefs rpc_pipefs /var/lib/nfs/rpc_pipefs || true ; fi I know this is not the correct way to do it, but it's enough in my case to ensure idmapd will always start/restart/stop correctly, without needing to touch any other file than /etc/init/idmapd.conf. I think your way is a really good one and I hope it will soon be officially integrated through a standard LTS update. Cheers, J.C. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/643289 Title: idmapd does not starts to work after system reboot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 44170] Re: Wake on LAN: No safe way to keep interface up
FYI, on my side I ensure the interface stays "awaken" (and not up, it can not stay "up", in the Unix meaning of this term, once the system has shut down) by putting these two lines in /etc/default/halt : NETDOWN=no # to not shutdown the interfaces ethtool -s eth0 wol g # to activate the wake-on-lan facility Best regards, J.C. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/44170 Title: Wake on LAN: No safe way to keep interface up -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
