[Bug 262781] Re: Intel driver gives incorrect screen size, DPI
** Attachment added: "Output of lspci -vvnn" http://launchpadlibrarian.net/21034157/lspci.out -- Intel driver gives incorrect screen size, DPI https://bugs.launchpad.net/bugs/262781 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 262781] [NEW] Intel driver gives incorrect screen size, DPI
Public bug reported: System: Dell Inspiron 6000, Ubuntu 8.04 Graphics successfully autodetected and set up, using "intel" xorg driver and i915 kernel module. However, the screen size is incorrectly set and results in a crazy DPI. In gdm, this results in characters in the user-chooser and password field about half the height of the screen. Once gnome is started the xfont DPI appears to be used instead and most things appear normal (although some programs like totem which I suspect use the screen dimensions to set proper video aspect ratios result in badly stretched video). Adding a -dpi 112 option to the line "command=/usr/bin/X -br -audit 0" is a fix for the incorrect size in GDM, or setting the size or DPI correctly using xrandr. Setting the -dpi 112 option results in the screen size in xdpyinfo being correctly calculated. lspci reports: 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03) xdpyinfo reports: screen #0: dimensions:1280x800 pixels (289x21 millimeters) resolution:112x968 dots per inch ddcprobe reports: screensize: 33 21 (ddcprobe gets the correct screen size). Adding the option DisplaySize 330 210 in the "Monitor" section of /etc/X11/xorg.conf has no effect - the intel driver apparently overrides any value given there. The incorrect assignment is perhaps because of (Xorg.0.log line 409-412) (II) intel(0): EDID vendor "LPL", prod id 0 (II) intel(0): EDID quirk: Detailed timings give horizontal size in cm. (II) intel(0): EDID quirk: Detailed timings give sizes in cm. (II) intel(0): DDCModeFromDetailedTiming: 1280x800 Warning: We only handle seperate sync. Since the screen size does use the value in cm it gets from ddcprobe in mm, perhaps this quirk is either unnecessary for this model or being incorrectly applied somehow. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- Intel driver gives incorrect screen size, DPI https://bugs.launchpad.net/bugs/262781 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 262781] Re: Intel driver gives incorrect screen size, DPI
Attached Xorg.0.log for booting up without -dpi 112 setting in gdm.conf. Note at line 453 the displaysize parameter is read from xorg.conf and DPI set accordingly, followed by at line 680 the intel driver overriding this setting with an incorrect value. ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/17161838/Xorg.0.log -- Intel driver gives incorrect screen size, DPI https://bugs.launchpad.net/bugs/262781 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 1871580] [NEW] Session killed instead of suspended on screen lock
Public bug reported: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871580] Re: Session killed instead of suspended on screen lock
There appear to neither be any relevant crash files (there are a couple which predate upgrading this system to focal), nor are there any reports on errors.u.c for this whoopsie-id. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871580] Re: Session killed instead of suspended on screen lock
Session lock invoked manually (~11:00:00), lock screen displays, click mouse to get unlock. Screen freezes for ~10 seconds, then blanks briefly and shows login screen. Looks like gnome-shell crashing at about 11:00:26 - interesting lines: Apr 08 11:00:26 kallisti gnome-shell[23758]: clutter_actor_insert_child_at_index: assertion 'child->priv->parent == NULL' failed Apr 08 11:00:28 kallisti kernel: gnome-shell[23758]: segfault at 0 ip 7fce7c55445a sp 7fffada2b230 error 4 in libst-1.0.so[7fce7c532000+4b000] Apr 08 11:00:28 kallisti kernel: Code: 4d 8b 8c 24 28 01 00 00 48 98 eb 0c 0f 1f 40 00 48 83 e8 01 85 c0 78 52 4d 8b 04 c1 b9 16 00 00 00 48 89 ef 49 8b 10 48 8b 12 <48> 8b 32 f3 a6 0f 97 c2 80 da 00 84 d2 75 d7 4d 8b 40 08 49 83 78 ** Attachment added: "journal during session lock" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+attachment/5349407/+files/journal-gnome-crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871580] Re: Session killed instead of suspended on screen lock
Lots of repetitions of: ``` ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: called for pid 7223, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: debug: session gdbus call: (true,) ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: apport: report /var/crash/_usr_bin_gnome-shell.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS ERROR: apport (pid 7377) Wed Apr 8 12:22:45 2020: called for pid 7303, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 7377) Wed Apr 8 12:22:45 2020: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 7377) Wed Apr 8 12:22:45 2020: debug: session gdbus call: (true,) ERROR: apport (pid 7377) Wed Apr 8 12:22:45 2020: apport: report /var/crash/_usr_bin_gnome-shell.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS ``` I guess a anti-disk filling feature is proving counterproductive here? It's also possible that I manually disabled bits of whoopsie/apport in the past. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871580] Re: Session killed instead of suspended on screen lock
Deleting the old _usr_bin_gnome-shell.1000.crash and collecting a fresh one. However, a quick bit of experimentation appears to show that this crash only occurs with extensions enabled - after globally disabling extensions it appears to no longer occur. I haven't bisected extensions individually, but I'm guessing `gnome-shell-pomodoro` might be a good candidate since most of the others are javascript only. Still not ideal that extensions can kill the shell. ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+attachment/5349454/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871580] Re: Session killed instead of suspended on screen lock
Uploaded in #1871580. Looking through gnome-shell issues, #1868440 looks like it might also be the same thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()
In my case it did appear to be gTile related also. Just manually disabling the extension on the gnome extensions panel was also sufficient to trigger a crash (presumably triggering the same path as when the screen lock was activated). Presumably other extensions using libst can have the same effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868440 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615574] [NEW] yakkety upgrade - 256MB boot partition too small to upgrade when using EFI
Public bug reported: This is related to #1465050. ubuntu-release-upgrader-core: 1:16.04.16 What I expected to happen: Attempting xenial -> yakkety upgrade, using a previously installed system with the default partitioning scheme, would succeed. What happened: With a 256MB /boot [1] partition on a system using EFI (having the normal two kernels [2] with initrd, vmlinuz and vmlinuz.efi.signed), `do-release-upgrade -d` exits warning insufficient space in /boot [3]. Manually working around this is fine, but I suspect this isn't that uncommon a configuration and release-upgrader might need logic to remove the backup kernel to free sufficient space? [1]: /dev/sda2 237M 121M 104M 54% /boot /dev/sda1 511M 3.6M 508M 1% /boot/efi (this was the install default for xenial beta-1, I think) [2]: 1.2M abi-4.4.0-31-generic 180K memtest86+.bin 1.2M abi-4.4.0-34-generic 182K memtest86+.elf 187K config-4.4.0-31-generic 182K memtest86+_multiboot.bin 187K config-4.4.0-34-generic 3.8M System.map-4.4.0-31-generic 4.0K efi/ 3.8M System.map-4.4.0-34-generic 1.0K grub/6.8M vmlinuz-4.4.0-31-generic 37M initrd.img-4.4.0-31-generic 6.8M vmlinuz-4.4.0-31-generic.efi.signed 37M initrd.img-4.4.0-34-generic 6.8M vmlinuz-4.4.0-34-generic 12K lost+found/ 6.8M vmlinuz-4.4.0-34-generic.efi.signed [3]: The upgrade has aborted. The upgrade needs a total of 118 M free space on disk '/boot'. Please free at least an additional 9,134 k of disk space on '/boot'. Empty your trash and remove temporary packages of former installations using 'sudo apt-get clean'. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (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/1615574 Title: yakkety upgrade - 256MB boot partition too small to upgrade when using EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1615574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471423] Re: GnuTLS Support in Task
This is fixed in wily and debian unstable/testing (taskwarrior 2.4.x), and I think the updated package should at least install on vivid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471423 Title: GnuTLS Support in Task To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/task/+bug/1471423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262151] [NEW] mdadm generates incorrect config if array name contains whitespace
Public bug reported: System: Acer S5-391 Contains two flash drives configured as (Intel) fakeraid. mdadm correctly detects that this array exists, and shows (apparently) correct metadata for both the overall array and the individual disks. However, the name of the raid array contains spaces, and the /etc/mdadm/mdadm.conf generated (presumably by postinst scripts) does not quote or escape the spaces, resulting in an invalid config file. I assume it uses the output of something like `mdadm --examine --scan`, which yields ARRAY metadata=imsm UUID= ARRAY /dev/md/Aspire S5-391 container= member=0 UUID= Subsequently attempting to assemble the array then gives an error that the second ARRAY line is invalid (treating /dev/md/Aspire and S5-391 as separate arguments). This can be corrected manually by adding quotation marks around "/dev/md/Aspire S5-391" in /etc/mdadm/mdadm.conf, after which the array works correctly, but a check should probably be added for this syntax. I'm not sure if this can be fixed just in the debian/ubuntu packaging or needs to be sent upstream. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Tags: saucy ** Tags added: saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262151 Title: mdadm generates incorrect config if array name contains whitespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1262151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262161] [NEW] dmraid failure when array name contains spaces
Public bug reported: (see #1262151 concerning the same issue with mdadm) Ubuntu: saucy dmraid: 1.0.0.rc16-4.2ubuntu1 System: Acer S5-391 Contains two flash drives configured as (Intel) fakeraid. dmraid detects this array exists, and attempts to assemble it, but the resulting block device name contains an escaped space that makes them effectively unusable. The raid array contains a GPT-formatted disk, and boots with UEFI. dmraid -s *** Group superset isw_foobar --> Subset name : isw_foobar_Aspire S5-391 ... dmraid -ay produces devices named like /dev/mapper/isw_foobar_Aspire\x20S5-391 /dev/mapper/isw_foobar_Aspire\x20S5-391p[1-6] These block devices correctly map to the correct disk blocks (eg, mkfs.ext4 /dev/mapper/isw_foobar_Aspire\\x20S5-391p4 successfully creates a new filesystem), but anything that attempts to pass the names through appears to either fail to interpret the escapes or incorrectly splits the device into two arguments. `gparted` started without argument refuses to read the device (/dev/mapper/isw_foobar_Aspire does not exist) `gparted /dev/mapper/isw_foobar_Aspire\\x20S5-391` correct shows the partitions on the disk, but attempts to launch further tools (eg, create an ext4 filesystem in an existing partition), fails with non-existent device errors `ubiquity` shows the partitions (providing `dmraid -ay` was run first), but similarly fails to actually create a filesystem or write anything into it I was eventually able to install this system using `mdadm` to mount the disks and `debootstrap` to install the base system (since ubiquity will not work with md devices), but the experience was not at all fun. Consequently the extra information/logs I can provide is probably a bit limited as I'd rather not start messing around with the RAID again if I can possibly help it. ** Affects: dmraid (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/1262161 Title: dmraid failure when array name contains spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1262161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262161] Re: dmraid failure when array name contains spaces
It appears to be the same as that upstream report, yes. The RAID name has been set by the manufacturer in this case, and to dual-boot without re-installing everything it was necessary to use it. Is it correct behaviour for `dmraid` to escape the space to `\x20` in this case though, given it is a valid character in a file name? (Assuming there aren't different rules for block device names I don't know about). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262161 Title: dmraid failure when array name contains spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1262161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413963] [NEW] network manager cannot configure pptp VPN
Public bug reported: Release: vivid (fresh install) Packages: network-manager 0.9.8.8-0ubuntu34 network-manager-pptp 0.9.8.2-1ubuntu2 network-manager-pptp-gnome 0.9.8.2-1ubuntu2 After installing network-manager-pptp-gnome, it is not possible to add a PPTP VPN from the networkmanager GUI. What I expected to happen: Network -> Add Network Connection -> VPN -> Select PPTP and configure with GUI What happened: Network -> Add Network Connection -> VPN pptp is not listed as a possible VPN type. Cannot graphically configure VPN. Possible cause: Copying an existing VPN configuration to /etc/NetworkManager/system- connections results in a VPN which does work. The option to add a new one is possibly because of a missing file: /etc/NetworkManager/VPN/nm-pptp-service.name includes: [GNOME] properties=/usr/lib/NetworkManager/libnm-pptp-properties which does not exist after installing the above packages. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager-pptp (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager-pptp (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-control-center (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413963 Title: network manager cannot configure pptp VPN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1413963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1275760] [NEW] low graphics mode due to possible race condition on precise
Public bug reported: Precise 12.04.4 x86_64, kernel 3.2.0-58-generic. lspci reports: 01:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev a1) dpkg -l 'nvidia*' | grep '^ii' reports: ii nvidia-304 304.116-0ubuntu0.0.1 ii nvidia-319-updates 331.20-0ubuntu0.0.1 ii nvidia-331-updates 331.20-0ubuntu0.0.1 ii nvidia-common 1:0.2.44.2 ii nvidia-current 304.116-0ubuntu0.0.1 ii nvidia-settings331.20-0ubuntu0.0.1 ii nvidia-settings-304331.20-0ubuntu0.0.1 ii nvidia-settings-319-updates331.20-0ubuntu0.0.1 ii xorg 1:7.6+12ubuntu2 Since installation, this system has periodically fallen to the "running in low graphics mode" prompt on boot. This can always be resolved by logging into a TTY and restarting LightDM: sudo service lightdm restart. Recently (sorry I can't say precisely - probably the last month or so) the frequency of this event has increased to ~90% of boots. Sample Xorg.0.log attached, but the key lines appear to be [ 3.364] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the [ 3.364] (EE) NVIDIA(0): system's kernel log for additional error messages and [ 3.364] (EE) NVIDIA(0): consult the NVIDIA README for details. [ 3.364] (EE) NVIDIA(0): *** Aborting *** While `dmesg | grep nvidia` shows [2.737764] nvidia: module license 'NVIDIA' taints kernel. [3.658332] nvidia :01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [3.658338] nvidia :01:00.0: setting latency timer to 64 >From the timestamps, it looks like Xorg attempts to load the nvidia drivers 300ms before the kernel has actually loaded/initialised them, and hence fails. This certainly looks like a race condition. By the time I log into a TTY, lsmod shows the `nvidia` module to be loaded and restarting lightdm succeeds. Is there any way for either Xorg to check and if necessary wait for kernel module loading, or the low graphics dialog at least include a better option for dealing with this situation? ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/bugs/1275760/+attachment/3967555/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1275760 Title: low graphics mode due to possible race condition on precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1275760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285611] [NEW] python-networkx and python3-networkx conflict
Public bug reported:
Ubuntu: trusty 14.04
The python2 and python3 packages for the networkx library should
(presumably) be co-installable, but currently contain a common set of
files that cause whichever is installed second to fail.
python-networkx: 1.8.1-0ubuntu3
python3-networkx: 1.8.1-0ubuntu3
$ sudo apt-get install python{,3}-networkx
[ ... ]
dpkg: error processing archive
/var/cache/apt/archives/python3-networkx_1.8.1-0ubuntu3_all.deb (--unpack):
trying to overwrite
'/usr/share/doc/python-networkx/examples/basic/read_write.py', which is also in
package python-networkx 1.8.1-0ubuntu3
While the library is installed in /usr/lib/pythonX.Y/dist-packages in
each case, both attempt to install (I think identical)
documentation/examples to /usr/share/doc/python-networkx, causing the
collision.
I assume either a python 2/3 independent documentation package is
needed, or the python3 package needs to change the directory into which
it installs documentation. There seem to be a number of other python3-
prefixed directories in /usr/share/doc, so this wouldn't be
unprecedented.
This bug was not present in Saucy (python-networkx 1.7-2,
python3-networkx 1.7-2), in which the python3 version contains no
documentation.
** Affects: python-networkx (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/1285611
Title:
python-networkx and python3-networkx conflict
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-networkx/+bug/1285611/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 751605] Re: maximizing windows in a dualscreen setup goes awry
I also use vertically-stacked dual monitors, however I do not see the odd maximisation behaviour. I suspect it is significant that the two screens have the same width, but different heights (1280x800, 1280x1024). However, I do see the issue with maximised windows in the secondary screen disappearing under the title bar. This appears to be broadly similar to #707346 (the same issue, but in gnome). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/751605 Title: maximizing windows in a dualscreen setup goes awry To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/751605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737706] [NEW] Firefox plugin overwrites root window
Public bug reported: Binary package hint: firefox ubuntu 10.10, i386 xorg: 7.5+6ubuntu3 nvidia driver: 260.19.06-0ubuntu1 firefox 3.6.15+build1+nobinonly-0ubuntu0.10.10.1 metacity 2.30.2-0ubuntu1 After running flash content in the browser, the last frame shown remains in some part of the graphics buffer, and bleeds through into black pixels of any window moved on top of it. (ie, a semi-black background image shows the last flash frame only in the black area, and a terminal moved over the area shows the last frame everywhere except the white of the characters). I had originally assumed this was getting drawn onto the X root window, but the effect is not stored in screencaptures with either gimp or xvidcap. Killing firefox/plugin-container does not make the effect go away. Restarting metacity does remove it. I don't know if this is a bug in the flash plugin or plugin container (presumably related to hardware acceleration/DRI), or somewhere else in the X stack. Does anyone have suggestions for more useful diagnostics? ** Affects: firefox (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/737706 Title: Firefox plugin overwrites root window -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 522478] Re: Failed to mount "iPod".
A workaround, at least for the second-generation iPod Nano, as of ubuntu
10.10 is to insert the following into /lib/udev/rules.d/90-libgpod.rules
ENV{ID_VENDOR}=="*Apple*", ENV{ID_MODEL}=="*iPod*",
ENV{ID_FS_LABEL}=="*iPod*", ENV{UDISKS_PRESENTATION_NOPOLICY}="1"
This prevents any attempted mounting or handling of the the first
(system) partition on the iPod, after which the second mounts
successfully and is visible from, eg Rhythmbox.
Only tested once and might interact badly with other iPod partition
arrtangements - presumably this is something that should be done
properly in the /lib/udev/ipod-set-info binary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/522478
Title:
Failed to mount "iPod".
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 707346] [NEW] Window/toolbar overlap in vertically stacked monitor configuration
Public bug reported: Binary package hint: gnome-panel Binary package hint may be wrong, possible other candidates metacity, nvidia-current. When using a vertically stacked monitor layout (1280x1024 on top of 1280x800), with the primary monitor set to the upper screen. The GNOME upper and lower toolbars (fixed size, not set to auto-hide) are displayed on the primary (upper) screen. Windows in this screen when maximised set their upper bound as the bottom of the upper toolbar, but set their lower bound as the bottom of the top screen (underneath the bottom toolbar). Expected behaviour: either the bottom toolbar should appear on the second (lower) screen, or windows maximised on the upper screen should maximise only in between the two toolbars. Actual behaviour: windows maximise to include the space under the bottom toolbar, meaning that the active line of a terminal is hidden unless the terminal is explicitly resized. Other information: ubuntu: 10.10 w/m: metacity 1:2.30.2-0ubuntu1 gnome-panel: 1:2.30.2-1ubuntu3 The multiple screens are being run using the nvidia binary driver, version 260.19.06-0ubuntu1. This may be significant given the way it handles X screens when multiple monitors are connected. ** Affects: gnome-panel (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/707346 Title: Window/toolbar overlap in vertically stacked monitor configuration -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644644] Re: Frequent PA crashes during playback - pa_stream_cork() failed: Connection terminated and pa_stream_writable_size(): Connection failed
I note an interesting variation of this bug which I don't think anyone
else has reported (ubuntu 10.10).
I am unable to play video at any time with totem (resulting in the
pa_stream_cork() failed messageboxes as other have described).
However, using either rhythmbox (which I would naively assume is using
all the same backend elements as totem), playback succeeds, but only if
a network connection is available. No error messages are reported if no
network connection is available, but the sounds frequently pauses and
comes out in mixed-up order.
I see the same behaviour with mplayer (works providing a network
connection is available, otherwise sound pauses and shuffles as with
rhythmbox). No errors are shown except for a warning that my system is
too slow to play the video (not the case). Mplayer can be made to work
normally without a network connection by killing pulse and using -ao
{alsa, oss}.
I looked in my pulseaudio configuration and could not obviously find
anything that should be network dependent (network sinks, etc) - the
configuration should be as-shipped, anyway.
I'm not sure if this is sufficiently different to count as a separate
bug. I will see if the PPA above solves any of these issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/644644
Title:
Frequent PA crashes during playback - pa_stream_cork() failed:
Connection terminated and pa_stream_writable_size(): Connection failed
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 631735] Re: Wireless is disabled on boot
The same bug affects me (regression on upgrade from lucid to maverick), with the same driver (bcmwl-kernel-source). I note for the reporter (assuming the problem is actually identical) that right-clicking on the wireless taskbar logo and ticking "Enable Wireless" successfully brings the device back up, and a short while afterwards a wireless connection is successfully made (and stays up). system: Lenovo Ideapad S12N lspci reports: 07:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) lsmod reports: wl 1959533 0 lshw reports: *-network description: Wireless interface product: BCM4312 802.11b/g LP-PHY vendor: Broadcom Corporation physical id: 0 bus info: p...@:07:00.0 logical name: eth2 version: 01 serial: 00:26:82:32:35:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=wl0 driverversion=5.60.48.36 ip=192.168.1.5 latency=0 multicast=yes wireless=IEEE 802.11bg resources: irq:19 memory:c220-c2203fff On boot, lshw reports the same, except this entry starts " *-network DISABLED". On boot, lsmod reports that wl is already loaded as above. -- Wireless is disabled on boot https://bugs.launchpad.net/bugs/631735 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 631735] Re: Wireless is disabled on boot
Followup I'm not sure whether this is a bug with the driver (bcmwl-kernel-source) or networkmanager (network-manager-gnome). Looking at the state of some things in the /sys hierarchy before and after checking "enable wireless" in network manager. I'm not sure if these are helpful or irrelevant, but it probably doesn't hurt... /sys/bus/pci/devices/:07:00.0/enable "1" (before and after) /sys/bus/pci/devices/:07:00.0/power/control "on" (before and after) /sys/bus/pci/devices/:07:00.0/net/eth2/carrier "invalid node" -> "0" /sys/bus/pci/devices/:07:00.0/net/eth2/dormant "invalid node" -> "0" /sys/bus/pci/devices/:07:00.0/net/eth2/flags "0x1002" -> "0x1003" /sys/bus/pci/devices/:07:00.0/net/eth2/link_mode "0" -> "1" /sys/bus/pci/devices/:07:00.0/net/eth2/operstate "down" -> "up" /sys/bus/pci/devices/:07:00.0/net/eth2/power/control "auto" (before and after) -- Wireless is disabled on boot https://bugs.launchpad.net/bugs/631735 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
