Debian apparently has a separate repository for debug packages. I found and
installed nemo-dbgsym and nemo-fileroller-dbgsym, and re-ran gdb.
(terminal output for gdb without dbgsym is shown in comment #6, above)
No crash.
Ran without gdb.
Crash.
I will attach the no-crash terminal output
** Attachment added: "nemo_gdb_with_dbgsym.txt"
https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1804978/+attachment/5304903/+files/nemo_gdb_with_dbgsym.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As of version 4.2.3-2 from https://deb.debian.org/debian testing/main amd64
Packages
bug is still present.
(bring` up external drive in second tab, eject: nemo window disappears)
scott@ASUS-PRIME-B350M-A-CSM:~$ uname -a
Linux ASUS-PRIME-B350M-A-CSM 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1
As of version 4.0.6-1 from https://deb.debian.org/debian testing/main amd64
Packages
bug is still present.
(bring` up external drive in second tab, eject: nemo window disappears)
scott@ASUS-PRIME-B350M-A-CSM:~$ uname -a
Linux ASUS-PRIME-B350M-A-CSM 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1
Well, this was a LONG time ago, and I must have figured out how to get around
the bug, or the bug was fixed, but...
It seems to me that reporting not being able to get Wi-Fi to work, when it had
worked perfectly well in all [L]Ubuntu versions I had used previous to 16.04
(with no fiddling at
As of Nemo 3.8.5, bug still present.
scott@ASUS-PRIME-B350M-A-CSM:~$ uname -a
Linux ASUS-PRIME-B350M-A-CSM 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1
(2019-01-17) x86_64 GNU/Linux
scott@ASUS-PRIME-B350M-A-CSM:~$ lsb_release -dsc
Debian GNU/Linux buster/sid
buster
scott@ASUS-PRIME-B350M-A-CSM:~$ echo
After I had tested the crash from the terminal, I went back and finished the
install.
This I also invoked from the terminal.
In case the terminal output from a successful install would be useful to
you, I will now attach it here also.
The output appears to be identical prior to where the
Public bug reported:
I have tested this a couple of times, and will attach a text file of
terminal output.
I was installing the beta of Lubuntu 19.04 (03/26), and manually editing
partitions.
I had edited a partition, and either hit "Enter" from the partition name
field, or clicked on "OK"
As of the Beta release (03/26) of Lubuntu 19.04, the same thing occurs.
calamares 3.2.4-0ubuntu1
calamares-settings-lubuntu 1:19.04.3
calamares-settings-ubuntu-common1:19.04.3
partitionmanager3.3.1-5
--
You received this bug notification because you are a member of
As of the Beta release (03/26) of Lubuntu 19.04, the same thing occurs.
calamares 3.2.4-0ubuntu1
calamares-settings-lubuntu 1:19.04.3
calamares-settings-ubuntu-common1:19.04.3
partitionmanager3.3.1-5
--
You received this bug notification because you are a member of
Public bug reported:
I just did a Catfish search, and it found the two files for which I was looking
(one a copy of the other, in a different location).
I opened the context menu, to see what it contained.
I saw "Show in File Manager"
Since I do not use the default File Manager for Lubuntu
I take it that you found the problem?
Boy - that was fast!
I am curious what it was...
Also,
If it has been fixed, please let me know where and when I can access the
fixed version for "artful", so I can help verify that it now works.
--
You received this bug notification because you are a
** Attachment added: "Stitching log file"
https://bugs.launchpad.net/ubuntu/+source/hugin/+bug/1815854/+attachment/5239910/+files/TKDC9713-28_4_Cyl.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK. I have done the SSR recording of the process, and will attach it,
and the .log file (to which I added the terminal output), and the
stitching log and the .pto file.
The logs are from a run later than the one in the video, but it looked
and achieved exactly the same thing (I had somehow
** Attachment added: ".pto file of same run as hugin.log, and the stitching
.log file"
https://bugs.launchpad.net/ubuntu/+source/hugin/+bug/1815854/+attachment/5239911/+files/TKDC9713-28_4_Cyl.pto
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "Hugin .log file, with terminal output appended"
https://bugs.launchpad.net/ubuntu/+source/hugin/+bug/1815854/+attachment/5239909/+files/Hugin.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No. I was able to reproduce it several times.
When I get a minute, I will Simple Screen Recorder a video showing the
process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815854
Title:
Hugin (et
Here is the .pto file requested.
** Attachment added: "TKDC9713-28-2_Cyl.pto"
https://bugs.launchpad.net/ubuntu/+source/hugin/+bug/1815854/+attachment/5239392/+files/TKDC9713-28-2_Cyl.pto
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The attached screenshot shows what the desktop with the empty window and empty
Error box looks like, after going away to a different desktop (to file this
bug) and then returning to it.
Part of the window gets erased, but not redrawn with anything, and hence
remains blank, and the rest doesn't
Public bug reported:
I just tried to do another long (14 picture) panorama (also with a
tripod).
This one had a wide brightness range, which was eventually going to cause a
problem, but I told it to go ahead and align it anyway.
In two different runs-through, I got two slightly different
** Attachment added: "Screenshot showing enlarged lower bound of crop box
during stitch."
https://bugs.launchpad.net/ubuntu/+source/hugin/+bug/1815854/+attachment/5238511/+files/Hugin_Squeeze_Bug_2.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I have a long horizontal panorama (16 photos), that I took with a
tripod.
I opened the images, and told Hugin to align them
I used the Move/Drag tab to slightly rotate the image to be more
horizontal.
I used the Crop tab to approximately match the top/bottom/right/left
Oops! Sorry!
I think I actually did check this, but somehow never reported...
In any event, I have just tried it again. NO persistence, on new
computer.
Same result: I actually did a screenshot (which looked just as the previous did)
but of course, without persistence, I could not save it on
"LXDE will now use the titlebar layout by default."
Well, time marches on, and Lubuntu now has LXQt.
Should I assume that the comment also applies to LXQt as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>>> Surprise! <<<
(...sorry...)
I just booted up the live-USB for another purpose (prepping a new SSD to
be used in a new computer, once I have them put it together) and ran the
installer (only as far as the problem window), and it still almost
doesn't show the buttons.
I will attach
Here is the monitor settings window.
** Attachment added: "MonitorSettings.jpg"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1801441/+attachment/5220766/+files/MonitorSettings.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
I can fairly reliably cause Nemo to crash.
I have to say "fairly", as after multiple crashes, nemo now does something
different.
(More on that later)
To induce the crash, I would mount a USB stick with files on it, and open it in
a second tab.
I then clicked on "Eject",
I was able to boot without persistence (I had been afraid that I would
have to re-"burn" the USB drive without persistence, in order to test
this, but found the 3rd GRUB menu option did the trick).
Lo and behold, the "Trust this executable" was checked.
I have NO IDEA how it could have become
/etc/apt/sources.list :
--
deb cdrom:[Lubuntu 18.10 _Cosmic Cuttlefish_ - Release amd64 (20181017.2)]/
cosmic main multiverse restricted universe
deb http://archive.ubuntu.com/ubuntu/ cosmic main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/
I have booted from the install USB drive again.
The icon still exhibits the same behaviour (see screenshot).
regarding libfm-qt5 / casper :
lubuntu@lubuntu:~$ apt-cache policy libfm-qt5
libfm-qt5:
Installed: 0.13.1-5ubuntu7
Candidate:
I don't know if it was a YouTube video, or a website photo, but I later
noticed that a British user's install showed UnitedKingdom, also as one
word...
Perhaps, for some reason, the required text cannot contain white-
space...
--
You received this bug notification because you are a member of
scott@scott-Asus-M2N68-AM-PLUS:~$ sha256sum
/data/scott/Downloads/lubuntu-18.10-desktop-amd64.iso
99408e73e5ff11727be6987d9b2f8ee3b6a3b672c9da540a63c8b462a0cf63c4
/data/scott/Downloads/lubuntu-18.10-desktop-amd64.iso
I always do a md5sum on my .iso downloads, before burning to USB.
Is this
Here is the second of the two screen images.
Note that more time has passed and more notifications have displayed in
the panel.
Seeing this, and that at first nothing seems to happen at all, a first-
time user might be getting worried that maybe something is wrong.
I have a dual-core 3.1 Mhz.
Public bug reported:
First, when logging in from the boot screen, there is no indication that the
password entered was accepted.
The image remains on the screen what seems a long time.
So long, that eventually, the boot screen image ends up sharing the
screen with the panel as it is displayed,
Calamares is apparently NOT present ("dpkg-query: no packages found
matching calamares") on the installed release version of Lubuntu 18.10
(as I had suspected), so I am reporting the 5 separate issues from the
live session. Fortunately, ubuntu-bug seems to work from a live
session...
--
You
Public bug reported:
I don't use my Windows partition, except once in a while, when I need files
from it, so I do
not boot from it. When I saw "boot" checked, amongst various other flags, I
unchecked it
(I probably didn't need to - I don't know what all those flags do, anyway...)
On the
Public bug reported:
After manually selecting partitions for installation, the overview summary
window is so tall that only the top of the buttons "Back", "Install", and
"Cancel" are visible.
I had to click on the window's Maximize button to see the whole button.
(I think I remember a later
Public bug reported:
During the install, when the "System Language" and "...Locale" are displayed,
"UnitedStates" contains no space between "United" and "States".
This is after one selects the language and locale... I don't remember if it is
also true just as one is entering the information
Public bug reported:
Double-clicking on the "Install Lubuntu 18.10" icon on the desktop in the
live-session results in
the Window "Execute File" appearing, and it asks what we want to do with
"...what seems to be a desktop entry". The options "Open", "Execute", and
"Cancel" appear (with
Public bug reported:
Upon booting with a USB live system of the release version of Lubuntu 18.10,
the system menu contains two entries that appear to be able to install the new
version.
One is labelled "Install Lubuntu 18.10" and the other is labelled "Install
System".
I don't imagine that we
>In particular, #2 makes me question what image you're using. Sounds
like an old one.
I just today downloaded the released Lubuntu 18.10, placed it on a USB
thumb drive, and booted from it. There on the desktop was the install
icon, which when double-clicked upon, yielded the stated window...
I
Public bug reported:
In doing testing for other bugs related to this package, I have noted
that this file manager defaults to displaying files/directories in
reverse order (Z->A, 9->1, etc.)
I don't know if this is a bug, or a design decision, but it seems
counter-intuitive to me...
I just
I have now installed the release version of Lubuntu Cosmic 18.10.
I have not tested the multitude of file-associations that I did before,
as I was testing a different bug, but I will note in passing that when
I tried to display a .png file by double-clicking on it, it brought up Firefox,
not
Public bug reported:
{If each of these should be reported separately, let me know. It seems
a bit of a waste, though...}
1. Both "Install Lubuntu 18.10" and
"Install System"
appear in the System menu of the Live session.
2. Double-clicking on the "Install Lubuntu 18.10" icon on
Having now installed the released version of Cosmic, the same problem
exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773608
Title:
Custom partition mount point not kept with "OK"; kept with
Here are the terminal commands that I saw in your screenshot,
plus output from inxi, which is similar to what produced your system output.
I had to modify the ls command for /data, as the recursive output would
have reached the nearest star and back...
[By the way, I was surprised to find the
OK.
I have now installed the released 18.10 version of Lubuntu, and have
exactly the same problem as before...
1. Install Lubuntu 18.10
2. Reboot
3. Edit /home/scott/.config/user-dirs.dirs to point the standard xdg
directories to
directories in my /data/scott directory
4. Log out/Log in
5.
I am currently out of town (and before then was busy trying to find a new used
car to replace one damaged in an accident) or I would have installed the beta
version of L 18.10 to test if the problem has since gone away. I probably will
not be able to test it before the final version is
*** This bug is a duplicate of bug 1607481 ***
https://bugs.launchpad.net/bugs/1607481
"Remember, this bug report is a duplicate of bug #1607481."
Well, actually, since this bug was filed two months before #1607481,
and the terminal output (or relevant portion thereof) was given in the
Just out of curiosity, just where is bash "turned on" (presumably at boot or
(more likely) login)?
What program or script enables it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773607
Title:
This has not happened in a long time. Might as well close it.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349208
Title:
New version of firefox crashes upon opening
To manage
This has not happened in a while, so go ahead and close the bug.
If it starts up again, I'll start a new bug report...
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639015
Title:
I don't believe that I have noticed this for a while, so I guess it can be
closed.
If it recurs, I will re-file with a new bug.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593916
I have been using Firefox less often lately, but I have been able to use all FF
versions
after #40 or perhaps earlier.
I am not sure, but some issue(s) may have been memory-related.
After I started using the add-on UBlockOrigen, FF started using quite a bit
less memory.
[Hmmm... That's
I have been using Firefox less often lately, but I don't think that this is
happening anymore.
I have only 4 windows, and all seem to have context menus working properly.
I guess you can close this, and I'll file a new one, if it recurs...
Thank you.
--
You received this bug notification
I have been using Firefox less often lately, but I don't think that this is
happening anymore.
I guess you can close this, and I'll file a new one, if it recurs...
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Lubuntu Cosmic - 18.10 daily for 2018-07-12
Upon logging in, there are two notifications displayed.
Each begins with "lxqt-panel"
1) "Show Desktop: Global shortcut
'Control+Alt+D' cannot be
registered"
2) "Volume Control: The following
shortcuts can not be
I have kept tabs on the .manifest files of the daily .iso , and I noted recently
that both PCManFM-qt and libfm-qt5 have now gone to 0.13.x versions.
Having now installed the 07/12 daily of Cosmic (18.10) in my test partition,
I can confirm that the bug is still present.
[Same procedure: install
As of the 2018-07-12 .iso,
(newer calamares 3.2.1-1)
I can confirm that I was not presented with the two options stated.
[In case calamares-settings-lubuntu is involved,
the original version was 2, and the current = 7. ]
--
You received this bug notification because you are a member of Ubuntu
As of the 2018-07-12 .iso,
( newer calamares 3.2.1-1 and
the same partitionmanager 3.3.1-2 )
the situation is the same.
[In case calamares-settings-lubuntu is involved,
the original version was 2, and the current = 7. ]
--
You received this bug notification because you are a member of
As of the 2018-07-12 .iso,
( newer calamares 3.2.1-1 and
the same partitionmanager 3.3.1-2 )
the situation is the same.
[In case calamares-settings-lubuntu is involved,
the original version was 2, and the current = 7. ]
--
You received this bug notification because you
.
-
-
- "Format" partiton edit option appears to keep reverting to "Keep" Edit
- Bug #1773610 reported by Scott Cowles Jacobs a moment ago
-
- Thank you for spending your time helping to make Ubuntu better with this bug
report. Reporting a bug is the first step in the bug fixin
Public bug reported:
Lubuntu 18.10 Cosmic
I am not absolutely sure about this (I may have missed this during install),
but I do not recall being presented with either of the following install
options, that I have seen on all previous installs:
1: do you want to update packages to their latest
, but left the actual package(s), I might well not have
known the difference...)
See screenshot.
"Format" partiton edit option appears to keep reverting to "Keep" Edit
Bug #1773610 reported by Scott Cowles Jacobs a moment ago
Thank you for spending your time helping t
Public bug reported:
Lubuntu 18.10 Cosmic
In doing a manual install, I always format the '/' root partition, but
leave all others alone.
Thus for all others, I kept the partition edit option at "Keep".
After changing the partition for '/' to "Format", I noticed that there was no
display
Public bug reported:
Lubuntu 18.10 Cosmic
In doing a manual install, I found out that if for a particular
partiton, one erases "(no mount point)" and enters a custom mount point,
that if one clicks on "OK" to finish editing the partition info, nothing
changes on screen, the mount point column
Public bug reported:
I have installed the 05/25 daily of Cosmic, and when I went to run qterminal
I found that:
There is no prompt;
There is no cursor key for history or line editing
(one only gets output like: "$ ls ^[[D^[[C^[[A^[[B" )
If there is an error, one gets something like:
"$ auvcg
Public bug reported:
Lubuntu 18.10 Cosmic
I have a second hard drive whose contents I have been looking through lately.
This is designated sda (plus the full description, of course).
My main hard drive is designated sdb.
On the page where one selects the type of install, one is given the
choice
Having now installed the 05/25 daily of Cosmic (18.10) in my test partition,
I can point out several odd file associations:
Text files (.txt .h .cpp ...) default to LibreOffice Writer, not
FeatherPad.
.pdf and .md (which appears to be a type of text file) default to E-book Viewer,
not qpdfview
Having now installed the 05/25 daily of Cosmic (18.10) in my test partition,
I can confirm that the bug is still present.
$ uname -a
lsb_release -dsc
echo $DESKTOP_SESSION
Linux scott-Asus-M2N68-AM-Plus 4.15.0-22-generic #24-Ubuntu SMP Wed May 16
12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Here is the promised screenshot (which looks much like the last one, as
nothing has changed).
Just as with LN 18.04, L 18.10's PCManFM-qt reads my user-dirs.dirs file
correctly when
it handles the desktop, but not when the user clicks on the App's Desktop
button in the left pane.
** Attachment
I am using LibreOffice-Writer 1:6.0.3-0ubuntu1 on Lubuntu Next 18.04, and found
when opening a previously-created document, that the pages did not line up.
Searching for LO-W bugs that referenced line-spacing, eventually led me to the
original reporter's bug, and then to the debian bug report
I have now booted into my old Lubuntu Next 17.10 install, to see what
PCManFM-qt was doing there.
It reports the correct Desktop location: "/data/scott/Desktop"
No problem at all.
To summarize:
In BOTH Lubuntu Next 17.10 and 18.04 (the final dailies of each),
PCManFM-qt finds/uses
>Maybe you should try following what I did in a clean system
>(try a virtual machine)?
I did.
I did a complete fresh install in one of my partitions.
"Desktop" did its default "/home/scott/Desktop" initially.
Then I swapped out the default user-dirs.dirs with mine (see above),
logged out, logged
** Attachment added: "Permissions window (PCManFM) for /data/scott/Desktop"
https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1768961/+attachment/5142017/+files/PCManFM_Permissions.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "Permissions window (Nemo) for /data/scott/Desktop"
https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1768961/+attachment/5142016/+files/Nemo_Permissions.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I will attach two screengrab'd files that show Nemo's and PCManFM's
Properties->Permissions for my /data/scott/Desktop directory.
See if you see any issue...
To my inexperienced eye, nothing seems wrong - the owner IS scott, and the
owner has read/write/execute permissions for the directory
>Reporter, is this still present on 17.10?
I believe it was.
I now have Lubuntu Next 18.04
(as soon as I have time, I'll install a daily of Cosmic and see what
if anything has altered between 18.04 and "18.10")
and Synaptic still reports "The list of installed files is only available for
Well, today was interesting...!
I brought up LO-W from the context menu of a document that I wished to
edit.
The day before, I had to do a hard shutdown (nouveau video-crashed) with
several LO-W windows open, so now LO_W put up the window where it shows
documents that need to be recovered.
When
@Walter Lapchynski (wxl)
Thank you for your advice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769420
Title:
Odd lxqt-config-file-associations for .jpg and .pdf
To manage notifications about
I am not sure where someone got the impression I had somehow installed
Lubuntu, and then installed LXQt packages on top of it ("Taking the LXDE
version of Lubuntu and installing LXQt metapackages on it will result in
a different experience. Unfortunately, that's not something the Lubuntu
team does
Well, even though there will be no "Lubuntu Next" ongoing, as you point
out, the ongoing Lubuntu will be fully LXQt.
Unless you plan to use completely different [LX]Qt apps in Lubuntu than were
used in Lubuntu Next, or completely re-write them, then it must be assumed that
the same apps will be
Public bug reported:
I recently installed Lubuntu Next 18.04, which includes LibreOffice 6.
At some point, I noticed that LibreOffice Writer (unlike all my other
programs) does not appear in the panel's Taskbar (where all apps loaded
in that workspace/desktop should be).
All other apps with
OK.
I have now re-purposed one of my previous distro-partitions, and
did a minimal install of Lubuntu Next, as I did before.
Upon booting into the new install, the odd file-associations are already
there.
Any file that is pure text (.txt .cpp .h ... ) defaults to LibreOffice Writer
instead of
OK.
I have now re-purposed one of my previous distro-partitions, and
did a minimal install of Lubuntu Next, as I did before.
Upon booting into the new install, Desktop is what you would expect:
/home/scott/Desktop. Fine.
Upon updating software (updating packages that changed since the April
I don't know - if you don't try it, you won't know.
The code may behave differently if it finds the string "$HOME",
than if it does not.
I have downloaded the source for libfm-qt-0.12.0 and libqt5core5a,
and have found what may be relevant code, but since I am not C++ literate
(I did C some
Lubuntu Next 18.04
Screengrab 1.97-2
Same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733461
Title:
QLubuntu - Default File Format blanks and always comes up .png
To manage
>How did you end up running Ubuntu 18.04?
Lubuntu-Next, actually - from:
http://cdimage.ubuntu.com/lubuntu-next/daily-live/pending/ -->
bionic-desktop-amd64.iso
Installed onto USB with mkusb package.
>Did you upgrade from a previous version of Ubuntu or did you install fresh?
I always install
Maybe it is just me, but to cut 'n' paste one complete line
("deb http://ppa.launchpad.net/mkusb/ppa/ubuntu bionic main")
seems easier ("a bit more user friendly")
than to need to cut the line up into three pieces, and paste them
individually into the three fields.
And I think it was even easier:
My point, I guess, was that even though my xdg user-dirs.dirs directory for
Desktop was:
/data/scott/Desktop
(an absolute path - no reference to $HOME)
pcmanfm-qt and a number of other programs (just was using qpdfview today and
had the same problem) apparently insisted upon adding /home/scott
Public bug reported:
It used to be easy to add a PPA to the Other Software tab in Synaptic,
Click on "Add", a window comes up, cut/n/paste the APT line from the
website's page that holds the PPA info, and click on "Add Source".
Done. (possibly also fix a key problem...)
Now, when one clicks on
** Attachment added: "Add PPA - new method"
https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1769514/+attachment/5135070/+files/Synaptic_addPPA_new.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Walter Lapchynski (wxl)
The incorrect Desktop reference in the left panel seems to be a
combination of the original and the other-partition directory.
It seems to want to use $HOME as part of the reference, even though
$HOME was not part of the actual directory path in userdirs.dirs.
Have you
I now have Lubuntu Next 18.04, and also have Nemo version 3.6.5-1, and
still have the same issue.
While I do not have the theme Radiance to test, I do have Ambiance (not
my default theme, which is Lubuntu Arc), but unlike "Dominique Meeùs
(dominiquem) ", selecting this theme does not alter the
Public bug reported:
I have Lubuntu Next 18.04
I do not know if the Lubuntu team modifies the file associations to match the
release,
or if the file associations are an LXQt default and are left intact until the
user
installs the Distro and modifies them.
I don't even know if the associations
I just noticed that ScreenGrab, in its Browse for default save directory,
does exactly the same thing:
Desktop under "Places" comes up as directory buttons (each of the following is
its own button):
/ home scott " data scott Desktop"
Note that there is a directory button containing only
This is $HOME/.config/user-dirs.dirs.
(I'm a little fuzzy on the details, but I believe that xdg looks for
user-dirs.dirs in $HOME/.config, and if it does not find it, creates it from
the default file in /etc/xdg
No, I guess not - I just had a look in /etc/xdg and found only
user-dirs.defaults
Public bug reported:
I have my personal data in a separate partition, and when I do a new install of
a distro
(Originally Ubuntu, then Lubuntu for a long time, now Lubuntu Next) always
change xdg's user-dirs.dirs to point at directories in my partition:
"
#XDG_DESKTOP_DIR="$HOME/Desktop"
Public bug reported:
I have my personal data in a separate partition, and when I do a new install of
a distro
(Originally Ubuntu, then Lubuntu for a long time, now Lubuntu Next) always
change xdg's user-dirs.dirs to point at directories in my partition:
"
#XDG_DESKTOP_DIR="$HOME/Desktop"
I am using Lubuntu Next 17.10 from last October.
I had problems with gdebi-kde (some sort of missing module), and installed
gdebi,
which also has a problem (if I don't invoke from terminal, cannot install, as
no password window ever appears), but at least I can get around it.
If one did not
1 - 100 of 328 matches
Mail list logo
