Public bug reported:
On a lubuntu next install I tried to install offline following this
testcase on an hp laptop that had previously worked with lubuntu and
secure boot.
ubiquity:
Installed: 17.10.2
Candidate: 17.10.2
Version table:
*** 17.10.2 500
500
s/1 --
> ----
> nmcli-nm:
>RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
> WIFI WWAN-HW WWAN
>running 1.2.2connected started none enabled enabled
> enabled enabled enabled
>
> To manag
Public bug reported:
To reproduce on an alternate install complete the install with ethernet
plugged in and boot into the new install and log into to the lubuntu
desktop and move over to the nm-applet and notice it says that your
ethernet device is not managed and showing connectoin information
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1612978
Title:
packgekit crash soon after install bcmwl-kernel-source
Public bug reported:
To reproduce run xeyes then run ubuntu-bug -w and close the popup telling you
to click on a window. Then click on xeyes. I get an error message from apport
saying xprop failed to determine the process id of the window.
apport:
Installed: 2.20.1-0ubuntu2.1
Candidate:
Public bug reported:
To reproduce run xeyes then run ubuntu-bug -w and close the popup telling you
to click on a window. Then click on xeyes. I get an error message from apport
saying xprop failed to determine the process id of the window.
apport:
Installed: 2.20.1-0ubuntu2.1
Candidate:
I see the same thing in the file but this is a quite simple fix with a
text editor that is easily accomplished if you can say write your own
udev rules.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1517625
Title:
Typo in hooks/biosdevname
Status in initramfs-tools package in Ubuntu:
Public bug reported:
To reproduce launch usb creator and then and opne a terminal and run
ubuntu-bug usb-creator-gtk . I get an error message saying that usb-
creator-gtk is not an offical package in wily.
I have usb-creator-gtk usb-creator-gtk:
Installed: 0.2.67ubuntu0.1
Candidate:
Public bug reported:
Install apparmor-docs and sudo gunzip techzip.pdf.gz to unzip the docs
then open in a pdf viewer.
On page 12 the apparmor walkthrough does not lead to a an apparmor
walktrhough but just developer.novel.com
http://developer.novell.com/wiki/index.php/Apparmor
Then in
I think it is marginally useful I learned a few things but could use a
major overhaul.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1495308
Title:
apparmor-docs has
Public bug reported:
To reproduce in a terminal or shell run man apparmor. In the section
Ubunut policy load assumes upstart as in 14.10 and earlier.
To copy the section from the man page it is
UBUNTU POLICY LOAD
Ubuntu systems use upstart(8) instead of a traditional SysV init system.
Public bug reported:
To reproduce on vivid install python3-autopilot and run autopilot3 list
--suites to try and list suites and it requires a suite name to list the
suite. The problem is for this command to do anything before I run this
command I need to know what the suite is called to list the
Public bug reported:
To do install a lubuntu installation in a kvm vm with qxl graphics. Then
lightdm will not start after restarting the installation. Lightdm will
not start.
lightdm:
Installed: 1.15.0-0ubuntu1
Candidate: 1.15.0-0ubuntu1
Version table:
Description:Ubuntu Wily Werewolf
Public bug reported:
Install the latest wily daily iso install install to the and and right
click on ibus in lxpanel then click about and it links to a dead
code.google.com/p/ibus when the homepage has moved to gihub.
ibus:
Installed: 1.5.9-1ubuntu3
Candidate: 1.5.9-1ubuntu3
Version table:
Public bug reported:
To reproduce install lubuntu 415 i386 on a t6500 core 2 duo cpu. I know I am
installing 32 bit on 64 but it will show like in with both a braodcom 4322
which I have not yet installed the prorpietary driver and this intel cpu. Open
additional drivers from the menu in lxde.
I am able to work around
this via the workaround in bug 1424362
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1442898
Title:
software-properties-gtk can't
Public bug reported:
To reproduce boot the April 5th dialy amd64 live iso of lubuntu and and
select try lubuntu without installing. Plymoth will show up and youi ar
egreeted with a screen of random shapes. The underlying system still
seems to work for user input for the keyboard as control alt t
I had trouble trying to apport collect from a tty so I saved a file from
the machine and reported it on my desktop.
** Attachment added: saved file from broken machine
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1440577/+attachment/4366898/+files/xorg.crash
--
You received this bug
** Also affects: lubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1432843
Title:
Lubuntu failed to boot
Public bug reported:
boot March 6th daily ubuntu mate installation went fine restarted got
to grub started up and did not load any further switched to tty and no
gui or splash screen came up. I switched to tty 1 and was able to login.
lightdm:
Installed: 1.13.1-0ubuntu2
Candidate:
I get the same behavior of not having this error message in a plain lxde
session but still get the same behavior on up to date vivid build.
To do this I ran sudo apt-get install lxde in vivid and then switched
user to the guest session and then tried launched a guest session and
did not get the
apport information
** Tags added: apport-collected
** Description changed:
EXPECTED RESULTS:
Log into guest session with no error messages.
ACTUAL RESULTS:
Upon log in to guest session, an error no session for pid pid for
lxsession is printed.
STEPS TO REPRODUCE:
1. Using
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1273524/+attachment/4254765/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: LightdmUsersConfig.txt
https://bugs.launchpad.net/bugs/1273524/+attachment/4254767/+files/LightdmUsersConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1273524/+attachment/4254766/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
apport information
** Description changed:
EXPECTED RESULTS:
Log into guest session with no error messages.
ACTUAL RESULTS:
Upon log in to guest session, an error no session for pid pid for
lxsession is printed.
STEPS TO REPRODUCE:
1. Using Lubuntu in trusty, utopic, or vivid
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1273524/+attachment/4254768/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Attachment added: run.log
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1273524/+attachment/4254074/+files/run.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
I can confirm that in lubuntu with
libgtk-3-0:
Installed: 3.12.2-0ubuntu15.1
Candidate: 3.12.2-0ubuntu15.1
Version table:
*** 3.12.2-0ubuntu15.1 0
500 http://us.archive.ubuntu.com/ubuntu/ utopic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
3.12.2-0ubuntu15 0
Also can you state what icon theme you are using. To find this out go to
the menu select prefrences and customize look and feel. If it says
lubuntu which is the default icon theme for lubuntu then lxde icon theme
is not the the right package.
If it says nuovext2.0 then lxde-icon-theme will be the
a fresh i386 vm in virtualbox using 20140929 -lubuntu-desktopi386
boots with lightdm booting. I am using plymouth 0.9.0.0-ubuntu6.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
I can confirm lightdm 1.11.9 works on real hardware of an nvidia gt 5200
I am still able to reproduce the bug with in virtualbox with 1.11.9.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Also happens in Lubuntu with the desktop iso haven't tried the alternate
yet.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into
34 matches
Mail list logo
