I *DID* try it. I set Desktop to /blah (note, there's no $HOME in there)
and it did not fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768961
Title:
xdg user-dirs not being read/stored
I finally could get back to my laptop, and I have tried Kau-Heng's
patched kernel 4.15.0-22 . I confirm that the webcam now works as
expected. Thanks a lot Kay-Heng and Mario.
I will apply now for a SRU for all supported Ubuntu versions.
--
You received this bug notification because you are a
Thank you for your response Joseph
I can not install an upstream kernel, because I use proprietary modules
(Virtual Box, Nvidea), and I did not find any extra packages for the
version, and as it is a production machine I will not risk it.
Let's wait for the normal kernel update via distro
Actually I manually applied the fix, which allowed it to actually pass
along far enough to actually try to unpack the squashfs and that's when
it failed and suggested to install squashfs-tools. Reverting the fix,
installing the package, and starting over and everything worked just
fine.
**
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769781
Title:
calamares crashes trying to open squashfs in Lubuntu Cosmic
To manage
Note in the upstream bug this is fixed upstream already, but only in
master. A release of 3.2.0 should be forthcoming next week with this
included. Getting that into Debian should resolve everything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
To reproduce in Lubuntu Cosmic run the calamares installer and pick any
install options/method.
I expected the installer to not crash but instead it crashed shortly
after creating the partition with the following error:
Boost.Python error in job "unpackfs".
** Description changed:
- To reproduce in Lubuntu next run the calamares installer and install to
- the entire disk.
+ To reproduce in Lubuntu Cosmic run the calamares installer and pick any
+ install options/method.
+
+ I expected the installer to not crash but instead it crashed shortly
+
Public bug reported:
calamares has no apport per-package hook, which means that when an error
is reported, little information is collected. ubiquity provides all
sorts of great info that can help diagnose issues. At minimum, the
Calamares.log in $HOME/.cache/Calamares/Calamares would be a good
Judging by the attached log, the partition is created successfully but
it fails when trying to "unsquash filesystem."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769781
Title:
calamares crashes
** Summary changed:
- calamres crashes with an error message when installing lubuntu-next
+ calamares crashes trying to open squashfs in Lubuntu Cosmic
** Attachment added: "$HOME/.cache/Calamares/Calamares/Calamares.log"
** Changed in: calamares (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769781
Title:
calamres crashes with an error message when installing
** Changed in: calamares (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769781
Title:
calamres crashes with an error message when installing
>From what I'm understanding here, the OP, Rob, resolved his issue, which
centered around Ubuntu Desktop, so for all intents and purposes, this
bug should be considered invalid, given those particular requirements.
The other affected party, Nils, seems to be dealing with Lubuntu. I
cannot
Public bug reported:
I recently upgraded ubuntu budgie 17.10 to 18.04, when suspending the OS
when returning does not reconnect with the network.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic
I just set Desktop to /blah and everything works fine in pcmanfm-qt and
calibre, for example. That said, I cannot reproduce your issue.
Something must have changed about your system that is causing these
issues, but I have no idea what they are.
--
You received this bug notification because you
I have the same problem. Does also not work with the nautilus version
from flathub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767817
Title:
Full text search does not work
To manage
If you install a package, it will install additional dependencies.
Unless you remove those dependencies, you can run into issues. Assuming
you're following suggested packages, pcmanfm-qt would have installed
lxqt-session which may have lead to the problem at hand.
--
You received this bug
The system won't clobber over your config files on update/upgrade, at
least not the ones in your home. It will ask you if it notices that
things have changed on systemwide stuff.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: pcmanfm-qt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769313
Title:
Installed lxqt dependencies try to override Gnome at next start up
Since at least Trusty, lxpanel-indicator-applet-plugin (which does not
appear to be provided upstream), suggests indicator-messages-gtk2, which
is not available. It also suggests indicator-application-gtk2 which has
a hard requirement for gtk2 while indicator-application is gtk3. It
seems that the
** Summary changed:
- lxpanel-indicator-applet-plugin recommends non existent package
+ lxpanel-indicator-applet-plugin suggests deprecated package
** Changed in: lxpanel (Ubuntu)
Status: New => Triaged
** Changed in: lxpanel (Ubuntu)
Importance: Undecided => Medium
--
You received
Nope, but it should be irrelevant. If what you're saying is consistent,
it should end up looking in $HOME/Desktop/$HOME/Desktop/foobar, no?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768961
Try as I've might, I am not able to duplicate this. Can you provide some
clear instructions on how to do so?
** Changed in: lxqt-config (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Project changed: lubuntu-tweaks => lubuntu-default-settings (Ubuntu)
** Changed in: lubuntu-default-settings (Ubuntu)
Importance: Undecided => Low
** Changed in: lubuntu-default-settings (Ubuntu)
Status: New => Triaged
** Summary changed:
- Ship with screen shot application
+
This is not a bug, but a change in functionality. In fact, it requires
the same information but in a bit more user friendly way. You said you
would do e.g. "deb http://ppa.launchpad.net/mkusb/ppa/ubuntu bionic
main" and now you would fill that out as:
Type: Binary (deb)
URI:
I changed $HOME/.config/user-dirs.dirs so that
XDG_DESKTOP_DIR="$HOME/Desktop/foobar" and everything seems to behave
fine, so I can't replicate your experience, which makes it hard to fix.
Could you start with a fresh system (maybe a virtual machine) and come
up with some clear steps?
Barring
Lubuntu Next was never officially released, even though we had
beta/alpha versions. Additionally, the idea of having both a LXDE and
LXQt image is something we will not be continuing for the Cosmic cycle.
Instead, we will be switching over to LXQt entirely. It will most
certainly have apport in
The file is ~/.config/openbox/lxqt-rc.xml. Since it's in your home
folder (~), you don't need to sudo anything. I'm not sure what file
you're looking at but it's most certainly not the right one based on
what you're explaining or unless you broke something. That said, there's
no reason why nano
That can't be the end as that's not even a complete and valid config
file. Openbox would complain at you when you tried to run it. My guess
is that you're not arrowing down enough. Nano should say "Read 744
lines" in its status when you open it. That doesn't look like 744 lines.
:)
The sections
Actually `eject` is a standard part of the install and doesn't even
require the device name. Obviously if there's more than one device and
you want to open one over the other, it needs to be specific, but
there's always a default device. That said, the solution is fairly easy:
1. Open up
Is this $HOME/.config/user-dirs.dirs that you're editing or /etc/xdg
/user-dirs.dirs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768961
Title:
xdg user-dirs not being read/stored correctly for
For that matter, what is $HOME for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768961
Title:
xdg user-dirs not being read/stored correctly for desktop icon in left
panel
To manage
The question I was trying to ask was what specific command you use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768294
Title:
"eject" key doesn't open optical drive tray in Openbox
To manage
Actually, yeah, that 204 I got from some wiki page. It seems the
possible keycodes are:
$ xmodmap -pke | grep Eject
keycode 169 = XF86Eject NoSymbol XF86Eject
keycode 170 = XF86Eject XF86Eject XF86Eject XF86Eject
keycode 174 = XF86AudioStop XF86Eject XF86AudioStop XF86Eject
The fact that 174 is
** Changed in: lubuntu-default-settings (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768294
Title:
"eject" key doesn't open optical drive tray in
More comments coming from DELL:
"Yesterday, a new Dell internal document was created which contained a
temporary work around to downgrade the camera firmware to 1.0 ( the file
RomainDurritcague shared ). This internal document is about to be deleted as
this fix wasn't meant to be shared yet.
A solution has been proposed by Dell France:
http://dl.free.fr/uYeYUDXjo
Untar the archive and then go inside the folder, and you should be able
to execute: sudo ./rts_uvc -v 0x0bda -p 0x58f4 --download
170606_6BF129N2_58F4_v7605.rfw
It should say a huge "PASS" and after rebooting the camera
** Changed in: lubuntu-artwork (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: lubuntu-artwork (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unfortunately, that makes it quite difficult to fix, since we don't know
what caused the problem. Sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768325
Title:
lxpanel crashed with SIGSEGV in
So give me the exact steps to reproduce it. If it's reproducible, you
should be able to do it again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768325
Title:
lxpanel crashed with SIGSEGV in
1. Open up the terminal
2. Type xev
3. Hit enter
4. Press the eject key
5. Close the window that was opened by xev
6. Copy and paste the last "KeyRelease event" from the terminal here
You should have something like (except this is for a different key):
KeyRelease event, serial 40, synthetic
Yeah #5 is not really a bug. It would be "nice" to have a better look,
but it's not necessarily a problem. I don't off hand know of a good
solution.
As far as the first bug is concerned, I've removed the cruft, but I'm
not clear how to reproduce this. If you could enumerate the steps to do
so,
** Description changed:
- 1. As historically the desktop icon installer hasn't worked very well, I
+ As historically the desktop icon installer hasn't worked very well, I
tried to use the "calamares" option to install Lu Next 18.04 . . .
choosing "manual" and working my way through the
Regardless of how it works elsewhere, in Openbox it depends on the name
of the key and optionally the keycode. It may be different and perhaps
more flexible in other window managers. That said, I still need the
above information to get this implemented in Lubuntu.
--
You received this bug
In order to fix this, we need clear steps to reproduce this. If you can
provide us with a detailed list of what you did to produce the crash,
that will help significantly.
** Changed in: lxpanel (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Actually, I just discovered that the installer's Qt front end pretty
much has Kubuntu hard coded into it and will require a fairly extensive
addition of code to build flexibility into it.
Meanwhile, there has been some discussion about changing installers for
Lubuntu Next. We shall see…
**
Once we officially release it, we'll make sure that gets fixed ;)
** Changed in: lubuntu-next
Status: New => Invalid
** Also affects: lubuntu-default-settings (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lubuntu-default-settings (Ubuntu)
Status: New =>
BTW I removed the extra comments from the bug. If that is indeed
reproducible, please file a separate report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768293
Title:
Installer for Lubuntu Next
As far as I know, there's no binding in the Openbox configuration for an
eject key either upstream or within lubuntu-default-settings, nor has
there ever been. Assuming that the keybinding is standardized, we can
make it a wishlist item for lubuntu-default-settings, though.
As long as hitting the
As I said, this at least in my case was caused because I was using mutt
before the sidebar was coded into the main version (I was using
something called "patched" mutt). This file is not needed any more and
can be removed manually and the bug is gone.
It you think this is a bug please open a bug
I cannot replicate this in Bionic, at least if I understand the steps to
reproduce correctly. If this is still valid in Bionic, please re-write
the description with clear steps to reproduce. Ideally, this should be
something that could be recreated from a fresh install. Thanks!
** Changed in:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
>From what I understand from the above comment, individual bug reports
should be filed for each application that this is applicable to rather
than blaming the icon theme itself. If this is still relevant, please
file new bugs,
** Changed in: elementary-icon-theme (Ubuntu)
Status: New =>
Marking as invalid for the update-manager project as it was fixed in the
Ubuntu package and I expect is long outdated regardless.
** Changed in: update-manager
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same problem happened to Ubuntu 16.04.5. I have to specify "vers=1.0" to
mount a NAS drive successfully. The help said the default version is
1.0, so I spent a lot of time to check other options. Anyone please
update the help text.
--
You received this bug notification because you are a member
Same problem happened to Ubuntu 16.04.5. I have to specify "vers=1.0" to
mount a old NAS drive successfully. The help said the default version is
1.0, so I spent a lot of time to check other options. Anyone please
update the help text.
--
You received this bug notification because you are a
Public bug reported:
see report
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
Date: Thu Apr 26
@jay-z The reason is quite simply that there are drivers for this webcam
available for Windows but not for Linux.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated Webcam
@asgard2, open please another bug report with your system information.
Try also to disable all add-ons and see if you see the crash, just in
case it is not caused by an add-on. I was affected by this bug but I
haven't seen this crash for months. This bug report is expired and
nobody will pay
Confirmed on today's image. As if the bug wasn't strange enough, it's
even more strange that it just disappeared. This is not the kind of
thing that makes me sleep well at night. In any case, I'm inclined to
call this incomplete until it pops up again unless there is suggestion
otherwise.
--
You
See this forum:
https://www.dell.com/community/Linux-General/Dell-xps-13-9370-Webcam-
support/td-p/6032049
Dell is downgrading the firmware by plainly substituting the whole
screen with another screen that has the integrated webcam with firmware
1.00.
--
You received this bug notification
As I say in message #5, I tried 4.17rc1 and the webcam was still not
working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4)
I found an application that detects the camera, vokoscreen. But neither
cheese nor skype can detect it. So I will close this as invalid and
investigate somewhere else.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a
I tried also the 4.13 kernel, and the webcam is not working there either
(not detected by applications, detected by the system). This is strange
because this webcam was working for me in Ubuntu 17.10.
The microphone of the webcam is working normally.
--
You received this bug notification
I tried the 4.17rc1 mainline kernel and same thing, webcam detected by
the system but not by applications.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765058
Title:
Regression: 046d:08da
Public bug reported:
The 046d:08da Logitech, Inc. QuickCam Messanger webcam that was being
detected fine in Ubuntu 17.10 is not being detected in bionic by
applications. It is detected fine by the system, but Cheese for instance
reports "No device detected", and I've tried with other applications
** Tags added: kernel-bug-exists-upstream-4.17rc1
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765058
Title:
Regression: 046d:08da Logitech, Inc. QuickCam
I tried this last one, and webcam still not detected. But now syslog
seems to show the 1.00 firmware. This is the output of "dmesg | grep
uvcvideo":
dmesg | grep uvcvideo
[2.148721] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:58f4)
[2.149311] uvcvideo: UVC non compliance -
Thanks Key-Heng, I tried your kernel but in my system there is no
change. The webcam is still using the 1.50 firmware and is not detected
by the system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Kai-Heng Feng (kaihengfeng):
>Is the webcam firmware upgradable under Linux? I can't reproduce the issue on
>the XPS 9370 at my hand >because it's with older firmware.
As far as I can tell the only way to upgrade the firmware is to
completely change the screen, at least this is what Dell is
I've tried with a 4.17rc1 kernel recompiled with the patch mentioned in
#2 but no change, the webcam does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated Webcam
Dear Stefano, I think the problem is there is no appropriate driver in
the Linux kernel for the 1.50 firmware, and the installed webcam has
that firmware.
I'm trying now to recompile the 4.17.rc1 kernel with the patch I mention
in #2. I will try this patched kernel and see if the webcam works.
** Summary changed:
- Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in
DELL XPS 13 9370
+ Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in
DELL XPS 13 9370 with firmware 1.50
** Description changed:
The webcam is detected by the system, but
I tried the following upstream kernel:
Linux XPS-13-9370 4.17.0-041700rc1-generic #201804152230 SMP Mon Apr 16
02:33:40 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
and the bug is reproducible.
** Tags added: kernel-bug-exists-upstream-4.17.rc1
--
You received this bug notification because you are
Another piece of information. This webcam is working with the 1.0
firmware, but not with the 1.5 firmware that the Dell XPS 13 9370 ships
right now. Some affected user have reported the issue and they have
changed the screen for them with a webcam with the 1.0 firmware, and the
webcam started
Public bug reported:
The webcam is detected by the system, but no applications detect it.
sudo lsusb -v: (relevant part)
Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.01
It seems that there is a patch being worked out:
https://www.mail-archive.com/linux-media@vger.kernel.org/msg127992.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated
*** This bug is a duplicate of bug 1759920 ***
https://bugs.launchpad.net/bugs/1759920
Same Problem with ubuntu 17.10 an Kernel 4.13.0-37, can only boot with
kernel 4.13.0-36-generic. Using Gnome + Radeon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Before I submitted this, I had run the following command, per the web
page mentioned above.
sudo apt-get install libnl-3-200=3.2.21-1 libnl-route-3-200=3.2.21-1
libnl-genl-3-200=3.2.21-1
After submitting this, I ran the following commands:
sudo apt-get update
sudo apt-get install
Public bug reported:
I did an upgrade with "sudo apt-get dist-upgrade", and it removed
network-manager and network-manager-gnome. I could not connect to my LAN afer
that. I was able to find instructions for downgrading the libnl packages at
That's good news!
I have tested both kernels in multiple C5/M5 instances (more than 80)
with SSSD and AppArmor enabled in N.Virginia, and I could not face one
single failure. It seems that this new kernel version fixed the issue.
It would be good to get more feedbacks and push this kernel
This is caused by the following file:
/etc/Muttrc.d/sidebar.rc
It looks like a remaining from when I used a patched version of mutt, to
have a sidebar. The sidebar has been now been added as a feature of
normal mutt, so probably this is not needed. I have moved this file out
of that directory,
This is not a bug with Lubuntu. Lubuntu does not ship this, for one
thing. Also, it is a bug with how numlockx functions. Please file a bug
against numlockx.
** Changed in: lubuntu-meta (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
What error? If this is not the same problem as the bug description, file
a new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752733
Title:
xiterm+thai is installed and set to
@kamalmostafa - I have installed the suggested linux-
image-4.4.0-117-generic_4.4.0-117.141_amd64.deb and launched multiple M5
and C5 (more than 40) instances across multiple availability zones in N.
Virginia and unfortunately the issue still happening with this kernel.
--
You received this bug
Public bug reported:
I have Mutt configured to use the sidebar. When I start mutt, the
following error is reported:
Press any key to continue...ar.rc, line 4: ifdef: unknown command
Error in /usr/lib/mutt/source-muttrc.d|, line 5: source: errors in
/etc/Muttrc.d/sidebar.rc
Error in /etc/Muttrc,
Adam, I'm curious about your Python statement. This only fails when
running Ubiquity directly from GRUB. Loading the live system and then
running Ubiquity works fine. Also, Ubiquity fails to fail for any other
flavours.
Things start going south in syslog here:
Mar 7 21:40:40 lubuntu
*** This bug is a duplicate of bug 1752733 ***
https://bugs.launchpad.net/bugs/1752733
** This bug has been marked a duplicate of bug 1752733
xiterm+thai is installed and set to x-terminal-emulator
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928
Public bug reported:
I don't know, the error was raised without using the scanner .
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature:
Yes, this is present in 17.10.
** Tags added: artful
** Changed in: appmenu-qt (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-session (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
+ READ ME FIRST
+ =
+ This is a cosmetic issue. The warning message is just that— a warning. Though
the message comes up, there is no problem with the install/upgrade happening
like normal. That said, feel free to ignore it. It will get fixed, but it's
** Description changed:
- On a clean install of Lubuntu Desktop 18.04, the default x-terminal-
- emulator is set to txiterm, which comes from the package xiterm+thai.
- With this terminal it's not possible to use characters with accents like
- í or Á.
+ STEPS TO REPRODUCE
+ ==
+
** Changed in: lubuntu-meta (Ubuntu)
Status: New => Triaged
** Summary changed:
- Default terminal emulator is set to txiterm, which causes problems with
certain characters
+ xiterm+thai is installed and set to x-terminal-emulator
--
You received this bug notification because you are a
I've checked and everything seems OK, at least for Catalan. Thanks
@seb128 and @gunnarhj.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749673
Title:
Fcitx translation to Catalan not imported
To
Thanks @Sebastien and @Gunnar. As for @Sebastien's question, the place
where I don't see any of my Transifex translations is:
https://translations.launchpad.net/ubuntu/bionic/+source/fcitx/+pots/fcitx/ca/+translate?show=untranslated
Same thing for other packages like "systemd", which I
Also includes other properties like "Scale". Changing between "Join
Display" and "External Only" switches the scale to 100%.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749670
Title:
Display
Public bug reported:
Fcitx is translated into Catalan in Transifex. But these translations
are not imported into Launchpad. Is there anything special that has to
be done for the import to happen?
** Affects: fcitx (Ubuntu)
Importance: Undecided
Status: New
--
You received this
I am running Lubuntu 16.04.3 on a Acer Aspire One AOA150/ZG5.
I had the same problem described by Henk Leusink, after an update to
4.13.0-26 generic.
Now I deleted 4.13.0-26 and my system is working fine with the previous
kernel 4.10.0-42 generic.
Thank you
--
You received this bug
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743111
Title:
crash after update linux-image-4.13.0-26-generic
To manage
801 - 900 of 4969 matches
Mail list logo
